Zapier MCP on the Free plan, and Sume's own MCP endpoint
Zapier says MCP is now in its Free, Pro and Team plans. Sume's hosted MCP is a separate server at mcp.sume.com/mcp, reached with OAuth or an API key.
Yes. Zapier's help page says Tables, Interfaces and Zapier MCP are now included in its Free, Pro and Team plans, with no separate add-on. That covers Zapier's MCP server only. Sume's hosted MCP is a different server at https://mcp.sume.com/mcp, and an MCP client can be connected to both.
Zapier facts are from the Zapier help page and MCP overview; Sume facts are from MCP OAuth and API keys and the MCP quickstart, all read 2026-09-30.
What does the Zapier page say is included?
The page lists four things as included in the Free, Pro and Team plans: Zap workflows, Tables, Interfaces and MCP. It notes that legacy-plan and current-plan accounts get an email explaining the effect, and that the information was accurate at publication. The MCP overview describes Zapier MCP as connecting your MCP client to your Zapier account so an AI can act in the apps you already use. Check Zapier's own pages for limits and usage terms; the snapshot does not state them.
How is Sume's MCP endpoint different?
It exposes Sume's media tools (images, video, audio, jobs) rather than your Zapier apps. You add it as a remote HTTP server and sign in, or send an API key.
| Zapier MCP | Sume hosted MCP | |
|---|---|---|
| Connects your client to | Your Zapier account and its apps | Sume media tools and jobs |
| Endpoint | Issued by Zapier from your account | https://mcp.sume.com/mcp |
| Auth | Zapier handles OAuth and credentials | OAuth, or Authorization: Bearer <SUME_API_KEY> / x-api-key |
How do I connect Sume with an API key?
For Claude Code the quickstart's line is claude mcp add --transport http sume https://mcp.sume.com/mcp, followed by claude mcp login sume for OAuth. An API key is the other path: the client sends the key as a bearer header or x-api-key, and the session gets the full hosted tool set. The quickstart advises against pasting API keys into chat.
What changes for paid tools?
Spend is wallet and admission based, and idempotency_key is required on write and paid tools. Under OAuth the default is read-only (mcp:read); write tools appear only with mcp:write or an API key. See API key vs OAuth for MCP for how to choose.
Sources
Related posts
More in Integrations
- Zed MCP OAuth scopes: what Sume asks for (mcp:read, mcp:write)
Zed 1.18.0 fixed OAuth for MCP servers with non-default scopes. Sume has two scopes, mcp:read (required) and mcp:write (opt-in on the consent page).
- Activepieces HTTP GET with a body: poll Sume status instead
Activepieces 0.91.0 hides the body input for GET and HEAD. Polling Sume needs none: GET /v1/jobs/:id/status carries the job id in the path.
- Activepieces multipart Content-Length: what body Sume wants
Activepieces 0.91.0 sends known-length multipart with Content-Length. Sume job submits still need JSON; send media as public HTTPS URLs or a PUT upload.
- Claude Code 2.1.287: MCP server stopped connecting, what to set
Claude Code 2.1.287 added MCP URL prompts. If a server no longer connects, its changelog says to set bareElicitationCapability. Check Sume with mcp_health.
Written by Sume