Sume MCP avatar tools: 5 read-only and the paid create set

Hosted Sume MCP lists five read tools for avatars and avatar videos and a paid group for creates and previews. What OAuth mcp:read sees and the dry_run flow.

3 min readSume
All posts

The hosted MCP endpoint at https://mcp.sume.com/mcp lists five read tools for avatars and avatar videos, and a separate group of paid tools that create avatars, videos and previews (MCP tools and gates). With OAuth mcp:read only, the tools that change data and the paid tools are hidden and return insufficient_scope if called.

The two groups

Hosted MCP avatar inventory
GroupTools in the docs
Readavatars_list, avatars_get, avatars_search, avatar-videos_list, avatar-videos_get
Paid (listed under Paid)avatars_create, avatar-videos_create, avatar-image-to-video_create, avatar-video-previews_create, _get, _regenerate, _generate_video

Gates on a paid call

Every write or paid call needs an idempotency_key. dry_run: true previews admission and cost without submitting, and max_spend_usd is enforced only when you provide it. There is no mcp:paid scope.

{
  "idempotency_key": "avatar-create-001",
  "dry_run": true,
  "max_spend_usd": 2,
  "payload": {
    "avatar_handle": "studio_presenter",
    "input": { "type": "prompt", "prompt": "A friendly studio presenter in neutral lighting" }
  }
}

Cost reference

Prices behind the paid tools match the REST routes.

Sume rates, read 2026-10-08
ActionPrice
Create an avatar$0.95 flat
Avatar video, standard$0.184 per s
Avatar video, plus$0.245 per s
Avatar video, max$0.55 per s

The safe order

Connect with OAuth, call tools_list, then tools_schema with the tool name. Run the paid tool with dry_run first, read the estimate, and only then submit with a fresh key on a session that has mcp:write or an API key.

Sources

Related posts

More in Agents

All Agents posts

Written by Sume