Cline MCP remote server: add Sume's hosted MCP

To add Sume's hosted MCP server to Cline, put a sume entry under mcpServers in Cline's MCP settings with "type": "streamableHttp", "url": "https://mcp.sume.com/mcp", and an Authorization: Bearer header holding your Sume API key. Set type explicitly: Cline treats an entry without it as the legacy SSE transport.

Cline's side comes from its MCP and Auto Approve & YOLO Mode pages; Sume's side comes from MCP quickstart, OAuth and API keys, MCP tools and gates, and Jobs and results, all read on 2026-09-27. Sume does not publish a Cline extension; Cline connects to Sume's remote MCP server directly. Sume's basics page says hosted MCP still works but is not part of the primary path today. For VS Code's built-in MCP support, see VS Code remote MCP server.

Where do I add a remote server in Cline?

Cline keeps servers in an MCP settings file, and every way of editing it leads to the same mcpServers entries:

• IDE extension: click the MCP Servers icon in the Cline panel, open the Configure tab, and click Configure MCP Servers to open the MCP settings JSON.
• Remote Servers tab: a form with a Server Name, the full Server URL, and a Transport Type, where Streamable HTTP is recommended and SSE is legacy. Cline's page lists no header field on that form, so add Sume's header in the JSON afterwards.
• Cline CLI: edit ~/.cline/mcp.json, or run cline mcp, whose wizard prompts for the server name, the transport type, and the URL and headers of a remote server.
• cline config mcp --json lists the configured servers without the wizard.

What does the Sume entry look like?

Sume's quickstart asks for a streamable HTTP client, which is Cline's streamableHttp type. Sume's docs prefer OAuth for interactive clients and keep API-key remote MCP for existing users and automation; Cline's MCP page describes no OAuth sign-in, and its remote example sends a token in headers, which matches Sume's API-key path. Sume accepts the key as Authorization: Bearer or x-api-key, and an API-key session sees the full hosted tool set, write and paid tools included.

Replace <SUME_API_KEY> with your key. Cline's security basics say to store secrets in environment variables, but its page shows env only on local servers, so the key sits in Cline's settings file: keep that file out of any repository, and rotate the key if it ever shows up in logs or chat history.

{
  "mcpServers": {
    "sume": {
      "type": "streamableHttp",
      "url": "https://mcp.sume.com/mcp",
      "headers": { "Authorization": "Bearer <SUME_API_KEY>" },
      "disabled": false,
      "autoApprove": ["mcp_health", "tools_list", "tools_schema", "jobs_wait", "jobs_result"]
    }
  }
}

Which Sume tools should Cline run without asking?

Only the ones that read. Cline evaluates Auto Approve per tool call; its Use MCP servers setting covers MCP tools and resources, and its recommended default leaves MCP off until you have a specific reason. YOLO mode auto-approves everything, MCP tools included, and Cline calls it dangerous. Cline's security basics say to limit autoApprove to safe tools and to review tool calls before approval.

Before a paid call, have Cline preview it with dry_run=true or generation_admission_preview; max_spend_usd caps a call only when it is sent.

What if a Sume call times out?

Cline's MCP settings let you set request timeouts, and its troubleshooting table says to increase the MCP timeout when you see timeout errors. Size it for jobs_wait, which keeps one call open for up to 55 seconds, 50 by default. After 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 rest of the wait contract.

How do I check the connection?

Cline's quick start ends by checking that tools appear and testing one tool call. Ask Cline to call mcp_health, which confirms the endpoint, the auth source, and the safety posture, then tools_list for every tool the session can see. For auth errors, Cline says to re-check API keys, tokens, and required headers. Sume MCP tools list groups the tools by read, write, and paid.