Tavus PAL MCP connectors vs Sume hosted MCP tools and gates
Tavus MCP connectors let a PAL call third-party MCP servers. Here is what Sume's hosted MCP at mcp.sume.com exposes and the gates a paid call needs.
The Tavus changelog says MCP connectors give a PAL access to apps, or to any third-party MCP server, so it can take actions during a conversation. Sume runs a hosted MCP server at https://mcp.sume.com/mcp. Whether a given Tavus connector can register it is a question for Tavus; this post covers what the Sume side exposes and gates.
Tavus facts are from its changelog (entry dated September 18, 2026 in the group notes); Sume facts from MCP quickstart and MCP tools and gates, read 2026-10-01.
What does the Tavus changelog say a connector does?
You register a connector, attach it to a PAL, and the PAL can act on the user's behalf, such as sending an email or filing a ticket. It lists apps like Gmail, Google Calendar, Slack and Linear, or any third-party MCP server.
What can a client do on the Sume hosted server by default?
Hosted MCP defaults to read-only visibility under OAuth mcp:read. Mutating and paid tools stay hidden until the session has mcp:write or an API key. Spend is governed by wallet and admission; there is no mcp:paid scope.
Which gates apply to a paid call?
| Gate | Required? | Meaning |
|---|---|---|
idempotency_key | Required on write and paid tools | Stable key for transport and dedup, not human approval |
dry_run=true | Optional | Admission and cost preview only; the job is not submitted |
max_spend_usd | Optional | Enforced only when provided |
What should a live-agent builder set up?
Give the agent a read-only OAuth session first, use dry_run and max_spend_usd before any generation, and track job ids since renders outlive the conversation; see MCP jobs wait for long video jobs.
Sources
Related posts
More in Integrations
- Telegram Bot API 10.3 ephemeral sendVideo with a Sume clip
Bot API 10.3 adds ephemeral_message_parameters to sendVideo. Send a finished Sume artifact URL from your webhook handler; steps, retries and limits.
- VS Code 1.138 Codex and MCP tools: one Sume server entry
VS Code 1.138 lets Codex use VS Code's built-in, extension and MCP tools. Add Sume as one remote MCP server at mcp.sume.com and verify with tools_list.
- VS Code 1.140 multi-folder sessions: where to put the Sume MCP entry
VS Code 1.140 lets each chat use its own folder or worktree, and reads MCP servers from a global file or a workspace .mcp.json. Put Sume in the global one.
- VS Code remote delegation: whose Sume credit is used?
VS Code 1.140's remote delegation tools are off by default and normal approvals still apply. Sume spend follows the credential the session connects with.
Written by Sume