Skip to content
unzoi docs

Agent clients

Every client here connects to the same endpoint with the same key. The pages differ because the clients do — where the config lives, what it is called, and the specific way each one goes wrong. 

https://api.unzoi.com/mcp

Clients

Claude Code One command. The fastest client to get working, and the easiest to debug. Claude Desktop A remote connector in settings, or the stdio bridge on plans without them. ChatGPT A custom connector, with a caveat about which mode you are in. Cursor A JSON file, per project or per user. Windsurf Cascade’s MCP config, with a header block. VS Code Copilot’s agent mode, with the key prompted rather than stored. Zed A context server entry in settings.json. Cline The MCP servers panel, or its settings file directly. Continue A YAML block in the assistant config. Goose An extension, added by the CLI or the desktop app. n8n The MCP Client Tool node, on an AI Agent node.

Frameworks and SDKs

For agents you are building rather than clients you are configuring.

Claude Agent SDK Give an agent you are building the news index, in TypeScript or Python. OpenAI Agents SDK Attach the endpoint to an Agent, in Python or TypeScript. LangChain The MCP adapters, turning the six tools into LangChain tools. LlamaIndex McpToolSpec, into an agent or a workflow. Bedrock AgentCore A remote MCP target behind an AgentCore Gateway.

If your client only speaks stdio

mcp-remote bridge For any client that only speaks stdio.

Your client is not listed

It will still work. Every MCP client needs the same three things:

  1. The URL: https://api.unzoi.com/mcp
  2. The transport: Streamable HTTP — not SSE, and not stdio
  3. A header: x-api-key: nai_..., or Authorization: Bearer nai_...

A client that only offers stdio needs the bridge. One that only offers the older SSE transport cannot connect — this endpoint does not serve it, and Transport explains why.

The two mistakes almost everyone makes

  1. Not restarting the client. Most read their configuration once, at startup, and several do not quit when you close the window. If the tools do not appear, this is the first thing to rule out.
  2. Being in the wrong mode. Cursor, VS Code, Continue and Windsurf only call tools in an agent mode. In a plain chat the server is connected and never used, which looks identical to broken.