MCP Server
What the Zenode MCP server is and how your AI agent uses it.
The Zenode MCP server connects your AI agent — Claude, Cursor, VS Code, or any client that speaks the Model Context Protocol — to Zenode's component intelligence. Once connected, your agent can search the catalog, pull full part details, and research parts and datasheets, all on its own.
You don't call anything by hand. You ask your agent a question — "find me a low-noise dual op-amp under $1 that's in stock" — and it uses the Zenode tools to answer.
What your agent can do
Find & resolve parts
Turn a messy part number into a real MPN, or find parts by description — manufacturers and categories too.
Search the catalog
Query 25M+ parts by keyword and parametric filters; get compact summaries to choose from.
Pull full part details
Specs, pricing, availability, datasheets, lifecycle, and regulatory data for any part.
AI research
Describe a need and get ranked recommendations, or ask a datasheet a question and get cited answers.
Self-documenting
You don't need to learn the tools. On connect, your agent discovers them automatically — each tool describes its own inputs and outputs, and the server ships instructions on how they fit together — so the agent picks the right one for what you asked. There's nothing to configure beyond connecting.
Free to explore, pay for depth
Searching and resolving parts is free. You pay only when you pull a full part record or run an AI tool — using the same API key and balance as the REST API.
Connect
1https://api.zenode.ai/mcp/Authenticate with your Zenode API key as a bearer token. Pick your client to get started:
Connect Claude
Claude Code or Claude Desktop.
Connect Cursor
The Cursor editor's agent.
Connect VS Code
Copilot agent mode in VS Code.
Any MCP client
The endpoint, transport, and auth for any other client.
Next
- Connect Claude — Claude Code & Desktop
- Connect Cursor — the Cursor editor
- Get an API key — authenticate your agent