Connect Claude Code, Cursor, or Codex to Sume with hosted MCP

Sume's hosted MCP server at mcp.sume.com/mcp lets coding agents generate images, video, audio, and avatars. Setup, OAuth scopes, and spend gates.

Sume runs a hosted Model Context Protocol (MCP) server at https://mcp.sume.com/mcp. Point Claude Code, Cursor, Codex, or any remote HTTP MCP client at it, sign in, and your coding agent can call Sume's account, catalog, job, asset, generation, and crawl tools without wrapping the HTTP API yourself.

Everything below comes from the MCP docs. MCP access is included from the Pro plan up (see Pricing).

How do I connect Claude Code?

Add the server over HTTP, then run the login flow. OAuth consent happens on the MCP host.

claude mcp add --transport http sume https://mcp.sume.com/mcp
claude mcp login sume

How do I connect Cursor?

Add a remote MCP server entry in Cursor Settings → MCP, or in your MCP config file, and complete the OAuth sign-in when Cursor prompts you.

{
  "mcpServers": {
    "sume": {
      "url": "https://mcp.sume.com/mcp"
    }
  }
}

How do I connect Codex or another MCP client?

Point a streamable HTTP MCP server entry at https://mcp.sume.com/mcp and run that client's OAuth login for the server name you configured. The client discovers Sume's protected-resource metadata from the endpoint and sends you to the consent page on mcp.sume.com.

To check the connection, ask the agent to call tools_list (every tool visible to the session) or mcp_health (endpoint, auth source, and safety posture).

What can the agent do with each kind of sign-in?

Hosted OAuth is read-only by default. Turn Write on at consent to also grant mcp:write. There is no separate paid scope: paid calls are gated by the wallet and job admission.

From OAuth and API keys and Tools and gates, 2026-09-23.
Session	What the agent can call
OAuth `mcp:read`	Read-only tools such as `jobs_list`, `assets_get`, `catalog_list`, `crawl_scrape`. Write and paid tools return `insufficient_scope`.
OAuth `mcp:read` + `mcp:write`	The full hosted tool set, including paid generation.
API key	The full hosted tool set. Same idempotency and admission rules.

Which tools generate media?

The shipped paid tools cover more than avatars. Discovery tools (tools_list, tools_schema, catalog_list) tell the client exactly what is available in the current session, so treat the list below as a map, not a contract.

Images and video: generate_image and generate_video. Omit payload.model to let Sume route to sume/auto, or pick a catalog id.
Audio: music_create, tts_create, stt_create.
Avatars: avatars_create and avatar-videos_create.
Media tools: image_upscale_create, rmbg_create, video_upscale_create, and the timeline_* tools for assembly.
Web and social reads: the crawl_* family, for example crawl_scrape and crawl_search.

How do I keep an agent from overspending?

Write and paid tools require an idempotency_key, so a retried call cannot submit the same job twice. dry_run=true previews admission and cost without submitting, and max_spend_usd caps a call when you provide it. Every paid job still passes wallet admission. The Safe automation guide covers how agents should treat these boundaries.

What is not on hosted MCP?

Hosted MCP is not full parity with the HTTP API. Sume Image 1.0 and Video 1.0 (images_create / videos_create) are REST-only; call the Developer API for those. The in-app Sume agent is also a different product surface, not an MCP server you configure in a client.