Gemini CLI httpUrl or url for Sume: streaming HTTP versus SSE

Use httpUrl. Gemini CLI's MCP docs say httpUrl is for a streaming HTTP endpoint and url is for Server-Sent Events. Sume's quickstart describes the hosted endpoint as a streamable HTTP MCP server at https://mcp.sume.com/mcp, so httpUrl is the matching key. Put the URL in the server's entry under mcpServers in your Gemini settings.

The settings that matter

The Gemini column is from its own docs page. The transport description is from the quickstart. The OAuth flow is started in the CLI with /mcp auth, and Sume's consent page lives on the MCP host.

Common mistakes

Putting the URL under url makes the client try an SSE connection to an endpoint that speaks streamable HTTP, and that mismatch is the first thing to rule out if the server will not connect. Another is pointing at the dev host, which is for Sume development only.

After connecting, ask the agent to call mcp_health and tools_list. If the tool list is short, the session is probably read-only, since OAuth mcp:read hides write and paid tools.

• Check the key name first: httpUrl, not url.
• Leave trust off while you are testing.
• Use mcp_health to confirm the auth source.

The tradeoff

The 600,000 ms default means Gemini CLI itself will not cut off a Sume wait, so the 55-second server cap is the real limit. You still loop in short slices. Setting a lower per-server timeout would make Gemini fail faster on a hung call, at the cost of cutting off slow but healthy ones.

If you need to test the connection from the command line before you configure anything, the quickstart's first calls are the same for every client: mcp_health, tools_list, tools_schema and account_me. All are reads, so none of them spend credits, and a clean answer from them means the transport key is right.