Warp MCP server: add Sume's hosted MCP to Warp's agent

To add an MCP server to Warp, open Settings > Agents > MCP servers, click + Add, and paste the server's configuration: a command for a CLI server that Warp launches, or a url for a Streamable HTTP or SSE server. For Sume's hosted server, the URL is https://mcp.sume.com/mcp. Start it without credentials and Warp opens a browser sign-in (OAuth); or pass a Sume API key as a Bearer token in headers.

Warp's side comes from its Model Context Protocol (MCP) and Profiles & Permissions pages; Sume's from MCP quickstart, OAuth and API keys, MCP tools and gates, and Jobs and results, all read on 2026-09-27, plus current server code where noted. Warp's page covers MCP servers for local agents in the Warp app; cloud agents have their own page. Sume has no official connector for Warp: this is a plain remote MCP connection, and Sume's basics page says hosted MCP still works but is not the primary integration path today.

How do I add Sume's MCP server in Warp?

Open the MCP servers page in any of these ways, then click + Add. Warp accepts configurations copied from most MCP clients, and a URL server takes a required url and optional headers.

• Settings > Agents > MCP servers.
• Warp Drive, under Personal > MCP Servers.
• The Command Palette: search for Open MCP Servers.

{
  "Sume": {
    "url": "https://mcp.sume.com/mcp"
  }
}

Should Warp sign in with OAuth or an API key?

OAuth keeps your Sume API key out of Warp. Warp handles the sign-in in your browser, stores the credentials on your device, and needs a new sign-in on a new machine; you can revoke them from the MCP Servers pane. On Sume's consent page, Read is locked on and Write is off by default. With Write off, paid tools such as generate_image are hidden, and a call to one returns insufficient_scope; turn Write on if Warp's agent should generate media. In current code a Sume OAuth token lasts one hour, and Sume issues no refresh token, so expect to sign in again after that.

For an API key, Warp's Custom Headers method passes a Bearer token: add "headers": { "Authorization": "Bearer <SUME_API_KEY>" } to the entry. An API-key session sees the full hosted tool set, write and paid tools included. Warp's docs say sharing a server scrubs sensitive values in its env configuration and say nothing about headers, and they warn that MCP logs may contain API keys. Don't share a server or its logs while a key is in the header, and rotate the key if it appears in logs or chat history.

Can I keep Sume's server in a config file?

Yes. Warp reads file-based servers from ~/.warp/.mcp.json, whose servers auto-spawn by default, and from .warp/.mcp.json at a project root. Project-scoped servers never auto-spawn: you toggle each one on from the MCP servers page, and again after a restart. A file-based server that requires OAuth shows an authentication modal on its first spawn, so a project file with only Sume's URL keeps secrets out of the repository. The built-in /agent-add-mcp skill can write either file for you, and Warp asks you to approve edits to MCP config files.

How do I make Warp ask before it calls Sume?

Warp's MCP permissions are per server and live in each Agent Profile. The MCP allowlist lets the Agent call a server without asking; the MCP denylist requires approval before calling a server, even one also on the allowlist; “Agent decides” acts autonomously when the Agent is confident and asks when it is uncertain. Put Sume on the denylist if every call should wait for you. Run until completion lets the Agent proceed without asking for the current task, so leave it off while Sume's paid tools are available.

Sume's gates apply either way: every paid call needs an idempotency_key, dry_run=true previews admission and cost without submitting, and max_spend_usd caps a call only when it is sent.

Will long video jobs time out, and how do I test it?

Warp's MCP page documents no tool-call timeout, and Sume keeps each wait short: jobs_wait holds one call for at most 55 seconds, 50 by default. After wait_slice_expired, the agent should call it again with the same ids and never resubmit the paid create; MCP tool call timeouts on long-running video jobs covers the pattern.

To test the setup, ask the agent to call mcp_health, which confirms the endpoint, auth source, and safety posture, then tools_list. If a call fails, the server's View Logs button on the MCP servers page shows Warp's MCP logs.