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 — on claude.ai, in Claude Desktop, or in Claude Code (the CLI).
There are two ways to authenticate:
- Sign in with Zenode — Claude opens a browser window, you log in to your Zenode account and approve access. No key to copy or store. Available in Claude only, for now.
- API key — paste a Zenode API key into Claude's config. Works in every client, including Cursor and VS Code.
Sign in with Zenode
You need a Zenode account — sign up at zenode.ai if you don't have one. Usage is charged to that account's balance, the same one the REST API uses.
claude.ai and Claude Desktop
Claude Desktop shares its connectors with claude.ai, so you only add Zenode once.
- Open Settings → Connectors and click Add custom connector.
- Name it Zenode and set the URL to
https://api.zenode.ai/mcp. Leave the advanced settings (OAuth client ID and secret) empty, then click Add. - Click Connect next to Zenode. A browser window opens with the Zenode authorization screen — if you aren't logged in to Zenode yet, you're asked to log in first.
- Check that the screen names Claude as the app, review the permissions, and click Approve.
You're sent back to Claude and Zenode shows as connected. In a chat, open the Search and tools menu to turn its tools on or off.
On Team and Enterprise plans, an owner adds the connector once under Organization settings → Connectors; each member then clicks Connect and signs in with their own Zenode account.
Claude Code (CLI)
Add the server without a header:
1claude mcp add --transport http zenode https://api.zenode.ai/mcpThen, inside a Claude Code session, run /mcp, select zenode, and choose Authenticate. Your
browser opens the same Zenode authorization screen; approve it and Claude Code reports the server as
connected. It keeps you signed in and refreshes access on its own.
What Claude can access
The authorization screen lists what you're granting. Claude gets only these permissions, and only for your account:
| Permission | Lets Claude |
|---|---|
| Search parts | Search the catalog, resolve part numbers, browse manufacturers and categories |
| Read part details | Pull full part records — specs, pricing, availability, datasheets |
| Ask documents | Ask questions of datasheets and get cited answers |
| AI research | Run AI discovery and research tools |
| Read lists | Read your approved-parts lists |
| Read usage | Check your balance and usage |
| Stay signed in | Refresh access without asking you to log in again |
Disconnect
Disconnect Zenode under Settings → Connectors in Claude, or run claude mcp remove zenode in
Claude Code. Connecting again takes you back through the authorization screen.
Use an API key
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:
1claude mcp add --transport http zenode https://api.zenode.ai/mcp/ \2 --header "Authorization: Bearer <YOUR API KEY HERE>"Confirm it connected:
1claude mcp listor run /mcp inside a Claude Code session — you should see zenode listed as connected.
Claude Desktop
With an API key, Claude Desktop reaches the server through mcp-remote. Open
Settings → Developer → Edit Config and add a zenode entry:
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.