Any MCP client

Any client that speaks the Model Context Protocol can connect to Zenode. The Claude, Cursor, and VS Code guides are shortcuts to the same endpoint below.

Connection details

Get a key and see how to authenticate on the Authentication page. The MCP server shares one account, key, and balance with the REST API.

Configure your client

Most clients take a remote server as a url plus a headers map. The shape varies by client (some use mcpServers, some servers), but the values are the same:

1{
2  "zenode": {
3    "url": "https://api.zenode.ai/mcp/",
4    "headers": {
5      "Authorization": "Bearer <YOUR API KEY HERE>"
6    }
7  }
8}

Clients that only launch local (stdio) servers can reach the remote endpoint through the mcp-remote bridge:

1npx -y mcp-remote https://api.zenode.ai/mcp/ --header "Authorization: Bearer <YOUR API KEY HERE>"

After connecting

There's nothing else to configure. On connect, the client lists the tools — each one describes its own inputs and outputs, and the server ships instructions on how they fit together — so the agent picks the right tool for the task on its own.

Next

• MCP overview — what your agent can do
• Get an API key — authenticate your agent