Cherry Studio: add Sume as a remote MCP server and bind it
In Cherry Studio, add a server under Settings > MCP, enable it, check its tools, then bind it to an Agent. A server that is not started cannot be bound.
In Cherry Studio, go to Settings > MCP > MCP Servers > Add, enter Sume's URL https://mcp.sume.com/mcp as a streamable HTTP server with the authorization your key needs, enable it, check that its tools appear, and only then bind it to an Agent. Cherry Studio's docs say a server that is not started cannot be bound, and that remote services usually give an SSE or streamable HTTP address.
Cherry Studio's steps are from its MCP docs; Sume's from the MCP quickstart and OAuth and API keys, read 2026-10-06. Sume has no official Cherry Studio integration.
What is the order of steps?
The table below lists each item as documented.
| Step | Where | For Sume |
|---|---|---|
| 1. Add | Settings > MCP > MCP Servers > Add | URL https://mcp.sume.com/mcp |
| 2. Authorize | Server form | API key as Bearer or x-api-key |
| 3. Enable | Server toggle | Check the tool list that appears |
| 4. Bind | Work > Agent menu > Edit > MCP | Pick only the tools the agent needs |
Why bind to one agent only?
Cherry Studio recommends enabling servers one at a time and verifying each. With Sume it also limits blast radius: an API key sees paid tools, so bind the server to a single agent whose instructions say to preview with dry_run=true and send max_spend_usd and idempotency_key on paid calls.
First calls to try
These are the points to keep in mind.
mcp_health, to read the auth source and safety posture.tools_list, to see what this session can use.tools_schemafor one tool, before any paid create.
Sources
Related posts
More in Integrations
- Claude Code MCP_TOOL_TIMEOUT is about 28 hours; Sume waits 55 s
Claude Code lets a tool call run for about 28 hours by default, but Sume's hosted jobs_wait caps one call at 55 seconds. Why you still loop in short slices.
- Claude Code saves MCP text over 50,000 characters: size Sume reads
Claude Code writes long MCP text results to a file, and Sume caps a tool answer at 256 KiB. Read job waves in batches of 20 ids so each answer stays small.
- Cloudflare Worker: keep the image model id in KV and swap it live
A Worker that proxies POST /v1/images and reads the Sume model id from Workers KV, so replacing gpt-image-1 is a wrangler command, not a deploy.
- Cloudflare Workers cron (UTC) or a Sume schedule with a timezone?
Worker cron triggers run on UTC and take up to 15 minutes to propagate. Sume schedules take an IANA timezone and a skip-or-reject overlap rule.
Written by Sume