Claude Code 2.1.285 lists WebSocket MCP servers; Sume uses HTTP

Claude Code 2.1.285 (Sep 29, 2026) now shows WebSocket MCP servers in claude mcp list, but Sume's hosted MCP is a remote HTTP server. Add it with --transport http and the URL https://mcp.sume.com/mcp; no WebSocket setup is involved.

The same changelog entry adds a claude plugin configure command and the CLAUDE_CODE_DISABLE_WEB_FETCH environment variable.

What the 2.1.285 entry lists

How Sume is added

The quickstart uses an HTTP transport and a login step that runs the OAuth flow. The consent page lives on the MCP host, not on the app site.

claude mcp add --transport http sume https://mcp.sume.com/mcp
claude mcp login sume
claude mcp list

Reading the list

After claude mcp list shows the server connected, ask Claude to call tools_list or mcp_health. mcp_health reports the auth source and the safety posture, and tools_list shows which tools your scope can see.

If the entry is present but shows a failed state, run the login again. A connected server with only read tools usually means Write was left off at consent.

Why no WebSocket for jobs either

Generation does not need a socket. Sume jobs are durable: you submit, keep the job id, and learn the outcome by polling or through a webhook. The docs state there is no SSE or WebSocket transport on the Developer API, and that GET /v1/jobs/:id/events is a pull snapshot.

On MCP, the equivalent is jobs_wait, which holds one request for at most 55 seconds and can be repeated with the same ids.

Clean-up tips

• Keep one server name, sume, so tool names and permissions stay predictable.
• Use OAuth for interactive sessions; keep API keys for automation, and never paste them into chat.
• Use CLAUDE_CODE_DISABLE_WEB_FETCH only if you want to turn off the built-in fetch tool; it does not change Sume's own crawl tools.