Quickstart

Connect Claude

Connect Claude to Zenode's component tools in a couple of steps.

Connect Claude to the Zenode MCP server and it can search and research components for you — in Claude Code (the CLI) or Claude Desktop.

Before you start

You need a Zenode API key. Create one and see how to authenticate on the Authentication page. Treat it like a password — keep it out of shared configs and source control.

Claude Code (CLI)

Add the server with one command:

BASH

1claude mcp add --transport http zenode https://api.zenode.ai/mcp/ \
2  --header "Authorization: Bearer <YOUR API KEY HERE>"

Confirm it connected:

BASH

1claude mcp list

or run /mcp inside a Claude Code session — you should see zenode listed as connected.

Claude Desktop

Claude Desktop reaches a remote MCP server through mcp-remote. Open Settings → Developer → Edit Config and add a zenode entry:

JSON

1{
2  "mcpServers": {
3    "zenode": {
4      "command": "npx",
5      "args": [
6        "-y",
7        "mcp-remote",
8        "https://api.zenode.ai/mcp/",
9        "--header",
10        "Authorization:${ZENODE_AUTH}"
11      ],
12      "env": {
13        "ZENODE_AUTH": "Bearer <YOUR API KEY HERE>"
14      }
15    }
16  }
17}

The key goes in env (not inline in args) on purpose — it sidesteps a Claude Desktop quirk where a space inside an argument gets split. Restart Claude Desktop after saving, then check Settings → Connectors for zenode.

Try it

Ask Claude:

Use Zenode to find a low-noise dual JFET op-amp under $1 that's in stock.

Claude picks the right Zenode tools on its own — there's nothing else to configure.

Next Connect Cursor