Does Sume hosted MCP match the HTTP API? Where parity stops

Not fully. Hosted MCP covers most generation families, but Image 1.0 and Video 1.0 are REST-only, and schedules have no MCP tool. Use the HTTP API for those.

4 min readSume
All posts

Not fully. Sume's overview says hosted MCP does not have full parity with the HTTP API. It covers account, catalog, jobs, assets, most generation families, crawl and Avatar tools. A few things need the Developer API instead: Sume Image 1.0 and Video 1.0 are REST-only, and schedules have no MCP tool, no CLI command and no create or edit endpoint.

What is where

The first rows are from the MCP overview, and the schedule row from the Scheduled page. catalog_list can show HTTP capabilities that have no MCP tool, so it is a good first look at the gap.

MCP versus HTTP API coverage (Sume docs, read 2026-10-06)
CapabilityOn hosted MCP?Where to go
generate_image and generate_video, with sume/auto routingYesHosted MCP
music_create, tts_create, stt_createYesHosted MCP
Sume Image 1.0 and Video 1.0 (images_create, videos_create)No, REST-onlyDeveloper API
Schedule runs (/v1/actions)No MCP toolDeveloper API to list and run; dashboard to create
Agent Completions (/v1/agent/completions)No MCP toolDeveloper API with a key that has the right scopes
Capabilities with no MCP toolShown by catalog_listDeveloper API

How to choose

Start with hosted MCP when an interactive agent should call Sume, because OAuth fits a client such as Cursor or Claude. Use the HTTP API for backends, scripts and the REST-only products. For Agent Completions, the docs say your own backend starts the run with an API key, which fits a server, not a chat client.

The tool you want not being in tools_list does not mean you lack permission. It may simply be a REST-only product or a read-only session. Check the scope first, then the overview.

  • Missing write tools: check the session scope.
  • Missing a whole product: check the REST-only list.
  • Missing a schedule tool: there is none; use the dashboard or ask the Agent in chat.

The tradeoff

A split surface means an agent that needs both has to hold two kinds of access, MCP for interactive work and a key for the API. That adds setup, but it keeps the unattended, billing-heavy REST products away from a chat client that a person is steering.

If you are not sure where a feature lives, ask the agent to call catalog_list and tools_list and compare the two. Anything in the first and not the second is an HTTP capability or a scope question, and the overview page tells you which. That check is free, because both are reads, and it saves a failed paid call.

Sources

Related posts

More in Developers

All Developers posts

Written by Sume