Qoder IDE MCP: add Sume's hosted server from Settings

In Qoder IDE, open Settings, choose MCP, click Add under My Servers, and paste a JSON entry whose url is https://mcp.sume.com/mcp. Qoder's docs say a Streamable HTTP endpoint is configured the same way as an SSE one and is detected automatically. The catch: the Qoder page I read does not document custom request headers or OAuth, so the Sume side of authentication needs a deliberate check before you rely on it.

This post uses Qoder's MCP page and Sume's MCP docs, both read on 2026-10-11.

What do I click and paste?

Per Qoder's page: open Settings (Cmd+Shift+, on macOS or Ctrl+Shift+, on Windows), go to MCP, click Add under My Servers, and enter the server as JSON. Qoder's example uses type: "sse" with a url. Sume's endpoint is Streamable HTTP, not SSE, so keep the entry free of an sse type claim and let Qoder's auto-detection handle it, as the page describes.

The entry to start with is below. It carries no secret.

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

How does Qoder authenticate to Sume?

This is the open question. Sume's preferred path for interactive clients is OAuth: the client discovers protected-resource metadata from the MCP endpoint and sends you to the consent page on the MCP host. The alternative is an API key sent as Authorization: Bearer or x-api-key.

Qoder's page says credentials for servers that need them must be set manually and mentions environment variables, but it does not state header syntax or an OAuth flow. If Qoder offers an authorize prompt when you connect, complete it. If it does not, and the server shows no tools, then this Qoder page gives you no documented way to attach the key; ask Qoder, or use a client whose docs show headers.

What about confirmations and timeouts?

Qoder says every MCP tool call requires your confirmation before it runs, and that you can set a per-request timeout from a dropdown in the server's details. Both suit Sume well. A confirmation prompt is a cheap speed bump in front of paid generation, though Sume's own gate is separate: paid and write tools need an idempotency_key, and dry_run previews cost without submitting.

Raise the timeout if you plan to wait on jobs. Sume's job-waiting tools return in slices rather than holding one call open for a whole render, so a modest timeout is enough as long as the agent polls again.

How do I verify it?

Ask Qoder to call mcp_health and tools_list. These are read-only. If you connected with OAuth and left Write off, you will see only read tools; paid tools such as generate_image return insufficient_scope or stay hidden until mcp:write is granted.