Connect Sume to Zapier MCP Client: Run Tool vs Read-Only Tool

To connect Sume to Zapier, add a connection to the MCP Client app, enter https://mcp.sume.com/mcp as the server URL, choose Streamable HTTP as the transport, and authenticate with either OAuth or a bearer token (a Sume API key). Zapier then exposes Sume's tools as a Run Tool action and a Run Read-Only Tool search. This is the direction where Zapier calls out to Sume, not the other way around.

Zapier describes MCP Client as a beta feature that is still in active development, so the field names below may change. Check the Zapier page in the sources before you build on it.

What do you enter in the connection form?

Per Zapier's help page, you open the Apps page, choose Add connection, search for MCP Client, and fill in a server URL, a transport method (Streamable HTTP or SSE), whether the server requires OAuth, and an optional bearer token.

Sume's hosted endpoint is a streamable HTTP server, so pick Streamable HTTP. For auth, Sume accepts OAuth access tokens or API keys, and one cannot stand in for the other.

Which Zapier step should call which Sume tool?

Zapier lists triggers (New Tool, New Tool Result), a search (Run Read-Only Tool) and an action (Run Tool). Use the read-only search for Sume's free reads: jobs_status, jobs_get, jobs_result, balance_get, and catalog_list. Use Run Tool for paid creates such as generate_image or generate_video.

Every write or paid Sume tool needs an idempotency_key, which is a dedup key and not human approval. Give each Zap run a stable value, for example the trigger record id plus a step label, so a Zapier retry does not submit a second render.

What limits apply on each side?

Keep the first Zap read-only: run mcp_health, then tools_list, then one jobs_status. Add a paid step only after those pass.

• Zapier says MCP Client supports tool calls only, not resources or prompts. Sume's hosted MCP is tools-only, so nothing is lost.
• Zapier cannot connect to Zapier's own MCP servers with this app. That does not affect Sume.
• An OAuth session with only mcp:read hides write and paid tools; they return insufficient_scope if called. Use a key, or turn Write on at consent, for generation.
• A jobs_wait call holds at most 55 seconds on remote MCP, so a long video needs several wait steps or a delay-and-poll loop.

What does a safe first Zap look like?

Start with a Zap that has a single Run Read-Only Tool step calling mcp_health. Zapier's help page says that if a connection fails right after setup, you should verify permissions, review the server documentation to confirm the fields, and reconnect the account. For Sume, the usual causes are a wrong URL, the SSE transport chosen instead of Streamable HTTP, or a key pasted with stray whitespace.

Next, add a second step that calls tools_list and read the result: an OAuth read-only connection returns fewer tools than a key connection, and that difference tells you which credential Zapier is actually using. Only then add a Run Tool step for generate_image with dry_run set to true. The dry run returns a cost and queue preview without submitting a job, so you can look at the estimate in the Zap history before any wallet spend.

When you remove dry_run, keep the same idempotency_key shape and consider setting max_spend_usd so a mistaken prompt cannot exceed your cap. Sume enforces that cap only when you send it.