VS Code mcp.json for Sume: set type http, not sse

Use "type": "http" with "url": "https://mcp.sume.com/mcp" in VS Code's mcp.json. VS Code's reference (read 2026-10-08) allows http or sse for remote servers. Sume's quickstart tells you to set a streamable HTTP MCP server to that URL, and its docs describe no SSE endpoint, so http is the type to pick.

The minimal entry

The VS Code MCP page shows servers declared under a top-level servers key with type and url. For Sume:

{
  "servers": {
    "sume": {
      "type": "http",
      "url": "https://mcp.sume.com/mcp"
    }
  }
}

Why the type matters

The two types are different wire formats. If you pick the wrong one, the client speaks a format the server does not document, so expect the connection to fail. Sume's docs list one production endpoint and say public docs and customer configs must use mcp.sume.com; the mcp.dev.sume.com host is for Sume's own development environments.

Sign in and verify

Start the server from VS Code. For OAuth, the client discovers Sume's protected-resource metadata from the endpoint and sends you to https://mcp.sume.com/oauth/authorize, which continues to the consent page. Read stays on and Write is off by default. Then ask the agent to call tools_list, and mcp_health if you want to see the auth source.

If you only see read tools, that is the default scope, not a broken setup. To get generate_image and generate_video, reconnect with Write on, or use an API key through a header (see the password-input post for how to keep the key out of the file).

What not to copy

Do not copy a sse entry from another server's README, and do not add a local stdio command for Sume; hosted MCP is the supported connector. Studio Agent is a separate product and not a connector URL.

If the server does not start

Work through the checks in this order, using only what the docs describe:

• Confirm the URL is exactly https://mcp.sume.com/mcp, with no trailing path and no dev host.
• Confirm type is http and that the entry sits under servers, the key that VS Code's page shows.
• If you configured a key, confirm you send one credential header, not two.
• Complete the sign-in when the browser opens; the consent page is on mcp.sume.com, not app.sume.com.
• Once connected, call tools_list to see what this session can reach, and tools_schema for one tool's contract.

Workspace versus user config

VS Code's reference describes where mcp.json can live; this post does not repeat it. The Sume side does not care which file holds the entry. It only sees the HTTP request and the credential, and it takes the workspace from the API key or from the account that signed in. Never put a workspace id in the config: Sume's safe-automation page says tools must not accept one from the user.