Sume MCP tools list: hosted tools grouped by read, write, and paid

The Sume MCP tools list groups the tools of the hosted server at https://mcp.sume.com/mcp into families: meta, account and catalog, jobs, assets, generation, avatars, crawl, and media. Within each family a tool reads, writes, or submits a paid job, and write and paid tools appear only in sessions with mcp:write or an API key. tools_list returns the exact set your session can see.

This inventory comes from MCP tools and gates, read on 2026-09-26. Where the docs group tools without naming a class, the class shown is the hosted server's current behavior. Treat it as a map, not a contract, because hosted MCP is not full parity with the HTTP API. The basics page says the CLI and hosted MCP still work but are not part of the primary integration path today.

How do I get the live tool list?

Call the discovery tools before anything else. Always discover the live contract; do not assume HTTP API parity.

• tools_list lists every tool visible in the session, with safety metadata. Each entry's safety block currently carries read_only, paid_generation, and requires_idempotency_key.
• tools_schema fetches one tool contract by name.
• mcp_health reports endpoint readiness, auth source, and safety posture.
• Tool ids use underscores. The server canonicalizes . to _ on call, so dotted aliases such as tools.list still work.
• Two aliases are retired: image-generations_create became generate_image, and video-router_create became generate_video. The server currently still maps calls to the old names, but only the new names are listed.

Which Sume MCP tools read, write, or spend?

Paid tools submit billable jobs, and write and paid tools take an idempotency_key. On the generation tools, omit payload.model to route to sume/auto unless the user named a family. An OAuth session with only mcp:read sees just the Read column; the rules for each kind of sign-in are in Connect Claude Code, Cursor, or Codex to Sume.

The table leaves out script_run, listed with the meta tools: it is not read-only, so read-only sessions do not see it, and each tool it calls keeps its own gates (programmatic tool calling).

Which writes cost nothing?

A few writes, and one mode of a paid tool, are unbilled:

• crawl_site is an unbilled write. Follow it with jobs_wait, then crawl_get on the same id.
• video_frames_create is unbilled. video_inspect probe and stills are unbilled; only its optional transcript is billed.
• video_filter with check_only: true is the unbilled program check.
• For paid tools, previewing with dry_run=true or generation_admission_preview and capping with max_spend_usd are covered in Safe automation for AI agents that call paid APIs.

Which tool names are not on hosted MCP?

If a name is missing from tools_list, one of these applies:

• images_create and videos_create. Sume Image 1.0 and Video 1.0 stay REST-only, and both are retiring soon (migration guide).
• Names that are not Sume tools, such as get_workflow_instructions, models_explore, or media_import_url. Cutouts are rmbg_create, and the social URL mirror is media-imports_create.
• The legacy caption creates video-captions_create and video-caption-overlay_create. They stay callable by name for in-flight clients but are not in tools_list.
• Scheduled runs, which have no MCP tool.
• Anything catalog_list shows without a matching tool: the catalog can list HTTP capabilities that hosted MCP does not wrap.