Which transport do I choose in Cline?
Streamable HTTP, which Cline recommends for remote servers. SSE (Legacy) is for older servers.
I prefer editing the JSON. What goes in it?
Press Edit Configuration under Customize → MCP and add { "mcpServers": { "research": { "type": "streamableHttp", "url": "https://research.brontir.com/api/mcp" } } }. Keep the type: without it Cline falls back to the legacy SSE transport.
Cline added the server but can’t connect. What is the usual cause?
The transport. With type missing from the JSON, or spelled differently (streamable-http, http), Cline falls back to legacy SSE, which doesn’t work with this server. Set "type": "streamableHttp" exactly and save the file.
The server is connected, but Cline says MCP isn’t set up. Why?
A task that was open while you signed in can keep going without the new tools. Start a new task, or reload the window, and Cline sees them.
Do I need an API key?
No. Once the server is added, an Authenticate button shows under its error: press it, sign in with your Google account and press Approve.
How do I sign in again, or set the server up from the Cline CLI?
In the extension, press Authenticate under the server’s error again. In the CLI, cline mcp add research https://research.brontir.com/api/mcp --transport http adds the server, and cline mcp opens a menu whose Authorize OAuth runs the browser sign-in, or reruns it.
Where does Cline keep its MCP settings?
In ~/.cline/data/settings/cline_mcp_settings.json, which the extension and the Cline CLI share. Edit Configuration under Customize → MCP opens it.
Can Cline call the tools without asking every time?
Yes. Turn on Use MCP servers in Cline’s auto-approve options: since version 4.1.15 that one switch approves every MCP tool, and the per-tool autoApprove list no longer applies. The research tools only read public data, so approving all of them changes nothing on your machine.