MCP Integration

Zenode exposes a Model Context Protocol (MCP) server that gives AI assistants direct access to part search. Instead of copy-pasting part numbers or datasheets, your assistant can query the Zenode API in real time as part of a conversation.

Endpoint

https://api.zenode.ai/mcp

Authentication uses the same Bearer token as the REST and GraphQL APIs. See the Authentication guide for how to create a key.

Available tools

The MCP server exposes exactly two tools, corresponding to the two parts search endpoints:

Tool	Description
MPN search	Search by manufacturer part number — exact, prefix, or fuzzy. Maps to `GET /v1/parts/search`.
Keyword search	Natural-language or keyword search for parts. Maps to `GET /v1/parts/agentic-search`.

Both tools return fully enriched part records: specs, offers, datasheets, categories, and manufacturer data.

Scope

The MCP server only covers part search. Operations like BOM matching and aggregations are available through the GraphQL API directly.

Setup

Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "zenode": {
      "url": "https://api.zenode.ai/mcp",
      "headers": {
        "Authorization": "Bearer zn_your_api_key"
      }
    }
  }
}

Cursor

Add to .cursor/mcp.json in your project (or your global Cursor MCP config):

{
  "mcpServers": {
    "zenode": {
      "url": "https://api.zenode.ai/mcp",
      "headers": {
        "Authorization": "Bearer zn_your_api_key"
      }
    }
  }
}

Claude Code

claude mcp add zenode --transport http https://api.zenode.ai/mcp \
  --header "Authorization: Bearer zn_your_api_key"

Usage

Once connected, your assistant can search for parts naturally:

"Find a low-power dual op-amp in a SOIC-8 package that's in stock."

"What are the specs for the STM32F405RGT6?"

"Search for 5V LDO regulators with at least 500mA output current."

Usage counts against your balance

Every MCP tool call uses your API credit balance, the same as direct REST or GraphQL requests. Monitor consumption from your Dashboard.