Trae IDE: add Sume as a remote MCP server with Add Manually

To add Sume to Trae, open Settings, choose MCP, click Add, then Add Manually, and paste a JSON entry whose url is https://mcp.sume.com/mcp and whose headers carry Authorization: Bearer <your Sume API key>. Trae's docs list three transports for MCP servers (stdio, SSE and Streamable HTTP), and Sume's hosted endpoint is Streamable HTTP, so the HTTP entry shape is the one to use.

Trae's side comes from Add MCP servers and Model Context Protocol; Sume's side comes from the MCP quickstart and OAuth and API keys. All were read on 2026-10-06. Sume has no official Trae integration: Trae connects to the hosted server like any other remote MCP client.

What do I paste into Add Manually?

Trae's page says that after Add > Add Manually, a Configure Manually window appears, and you fill in the JSON for the server. An HTTP server entry uses url and headers. For Sume, use an API key, because Sume's docs describe the API-key session as the full hosted tool set and OAuth as the read-only-by-default path for interactive clients.

{
  "mcpServers": {
    "sume": {
      "url": "https://mcp.sume.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_SUME_API_KEY"
      }
    }
  }
}

Where does the key end up?

Trae's page says only ${workspaceFolder} is supported as a variable, so you cannot point the header at an environment variable. The key is stored in the JSON you paste. Trae also reads a project-level mcp.json from the .trae/ folder once you switch project-level MCP on in Settings > MCP. Do not put a Sume key in that file if the folder is committed. Sume's docs say that if a key appears in logs or chat history, rotate it; create keys in the API keys dashboard.

How do I check that it works?

Ask the agent to call mcp_health, then tools_list. Sume's quickstart lists them as the read-only first calls: mcp_health confirms the endpoint, the auth source and the safety posture, and tools_list lists what this session can see. Before the first paid tool, read the tool's contract with tools_schema and preview with dry_run=true; paid and write calls always need an idempotency_key.