Continue MCP server: add Sume in .continue/mcpServers

To add an MCP server to Continue, create a .continue/mcpServers folder at the top level of your workspace, put a YAML block file in it with name, version, and schema, and list the server under mcpServers. For Sume's hosted MCP server, set type: streamable-http and url: https://mcp.sume.com/mcp, and send a Sume API key in an Authorization header through requestOptions. Continue uses MCP tools only in agent mode.

Continue's side comes from its MCP deep dive, config.yaml reference, and secrets guide; Sume's side comes from MCP quickstart, MCP OAuth and API keys, and MCP tools and gates, all read on 2026-09-28. Sume has no official Continue connector: Continue connects to Sume's remote MCP server like any other, and Sume's basics page says hosted MCP still works but is not part of the primary path today. VS Code's own mcp.json is a different format, covered in VS Code remote MCP server.

How do I add Sume to Continue?

Save this as .continue/mcpServers/sume.yaml. A standalone block file needs the name, version, and schema metadata; the server itself is one entry in the mcpServers list:

• ${{ secrets.SUME_API_KEY }} is Continue's mustache notation for secrets. For a local config, Continue resolves it from a .env file at your project root or in .continue/.env, then from ~/.continue/.env.
• Keep those .env files out of version control, and rotate the key if it ever appears in logs or chat history. Where to store API keys covers the options.
• For every workspace, add the same mcpServers entry to your user-level ~/.continue/config.yaml instead.

name: Sume MCP
version: 0.0.1
schema: v1
mcpServers:
  - name: Sume
    type: streamable-http
    url: https://mcp.sume.com/mcp
    requestOptions:
      headers:
        Authorization: Bearer ${{ secrets.SUME_API_KEY }}

Why streamable-http, and why requestOptions?

Continue's type takes sse, stdio, or streamable-http. Sume's quickstart points remote clients at a streamable HTTP MCP server, and in current code Sume answers a GET on its MCP URL with 405, so don't pick sse.

Continue's reference gives sse and streamable-http servers an optional requestOptions in the same format as a model's requestOptions, which is where headers lives. Continue's examples page shows some remote servers with an apiKey field instead, but doesn't say which header that sends. Sume expects Authorization: Bearer or x-api-key, so set the header yourself.

Can I reuse a JSON MCP config from Cursor or Claude?

Continue picks up JSON MCP config files from Claude Desktop, Cursor, or Cline when you copy them into .continue/mcpServers/, for example as mcp.json. Sume's own Cursor example, though, is a bare url that relies on an OAuth sign-in in Cursor, and Continue's MCP pages show keys passed as secrets rather than an OAuth sign-in. Use the YAML block with a key. MCP JSON config file explains the JSON shape other clients share.

What should I know before the agent calls Sume?

• MCP works only in agent mode, and agent mode needs a model with the tool_use capability, which Continue detects automatically for most models.
• An API-key session sees Sume's full hosted tool set, paid tools included, and spend resolves to the key's workspace.
• Paid tools need an idempotency_key; dry_run=true previews cost without submitting; max_spend_usd caps a call only when it is sent.
• One Sume jobs_wait call holds for up to 55 seconds, or 50 when timeout_seconds is omitted. On wait_slice_expired, the agent should call jobs_wait again with the same ids and never resubmit the paid create; MCP tool call timeouts on long-running video jobs covers the pattern.
• Hosted MCP can't read files from your laptop.