SheetsData

SheetsData MCP

Electronic component datasheets for AI agents — pinouts, specs, package info and design checks from manufacturer PDFs.

SheetsData is a hosted MCP server. Your agent finds parts across JLCPCB, Mouser and DigiKey, reads any section of a part's datasheet as text and tables, compares parts, checks a BOM, and checks your operating conditions against the datasheet's ratings. The agent never sees a PDF, and you don't have to find or paste one.

Server URL:  https://mcp.sheetsdata.com/mcp   (Streamable HTTP)
Sign-in:     MCP OAuth (browser), or an API key as "Authorization: Bearer <key>"

This repository holds the install configs, the @sheetsdata/mcp stdio proxy for clients that only start local servers, and the Claude Desktop bundle. The server itself is a hosted service.

Create a free account · Install in your client · Pricing · Docs

What it looks like

"Is the TPS54302 fine with 24 V in and 2.5 A out?"

check_design_fit("TPS54302", input_voltage=24, output_current=2.5)

overall: WARNING
  input_voltage  24 V  PASS  within the recommended range 4.5–28 V (14.3% margin)
                             datasheet row: "| V I |  | 4.5 | 28 | V |"
  unmatched: output_current

A condition the tool can't find a limit for is listed as unmatched and keeps the verdict at WARNING: a clean PASS means every condition was checked against the datasheet.

"Buck converters that take 24 V in and give at least 2 A" (free):

find_parts("buck converter", constraints=[vin_max >= 24 V, iout >= 2 A])

AP63357DV-7       32 V  3.5 A  pass@digikey   stock: DigiKey 49,457   datasheet: ready
LM2596S-5.0/NOPB  40 V  3 A    pass@digikey   stock: DigiKey 4,460    datasheet: ready
LMR33630ADDAR     36 V  3 A    pass@digikey   stock: JLCPCB 17,768    datasheet: ready

read_datasheet("TPS54302", section="pinout")
→ GND (1), SW (2), VIN (3), FB (4), EN (5), BOOT (6)

Tools

Prices are per call and the same on every plan. A call that fails is not charged. Current prices are on sheetsdata.com/pricing.

Pass manufacturer part numbers (TPS54302, STM32F446RCT6) or LCSC numbers (C2837938), not values like 100nF or reference designators like R1. A datasheet nobody has asked for yet is read on first request (poll check_extraction_status); after that it is cached for everyone.

Prompts

Built-in prompts that walk the agent through common hardware tasks:

Resources

Pricing

• Free to start. A new account gets $5 of credit, no card needed ($20 more when you add a card). Searching (search_parts, find_parts) is free.
• Trial is pay as you go from a prepaid balance: 5 new datasheets a day (datasheets already read are unlimited), 30 requests a minute.
• Pro is $39 a month minimum, with your calls counting toward it: no daily cap on new datasheets, higher rate limits and a private parts library.

Plans, limits and fees: sheetsdata.com/pricing.

Authentication

Use whichever your client supports; both bill the same organisation.

If a client asks how to register an OAuth client, choose automatic (dynamic) registration; SheetsData doesn't support client ID metadata documents yet.

Install

One-click installs (sign in on first use):

Every client below was checked against its own documentation on 2026-10-16 (linked in each section). In the snippets, replace YOUR_API_KEY with a key from sheetsdata.com/dashboard/keys.

• Claude (claude.ai and Claude Desktop)
• Claude Code
• ChatGPT
• OpenAI Codex
• Cursor
• VS Code (GitHub Copilot)
• GitHub Copilot CLI
• Gemini CLI
• Google Antigravity
• Windsurf (Devin Desktop)
• Zed
• Cline
• Roo Code
• Continue
• Goose
• Amp
• Kiro
• JetBrains (Junie and AI Assistant)
• opencode
• LM Studio
• Warp
• Any client that only starts local servers
• Your own code

Claude (claude.ai and Claude Desktop)

Custom connector (OAuth). Open Customize → Connectors, click + Add, then Add custom connector. Name it SheetsData, paste https://mcp.sheetsdata.com/mcp and click Continue. Under OAuth client, choose Register automatically: SheetsData doesn't support the default "Use Claude's published identity" option yet. Click Add, then Connect, and sign in to SheetsData in the browser tab that opens. On Team and Enterprise plans an owner adds it under Organization settings → Connectors → Add → Custom → Web. Free plans can add one custom connector.

Claude Desktop bundle. Download sheetsdata-x.y.z.mcpb from the latest release and drop it onto the Claude Desktop window. Leave the API key field blank to sign in with OAuth, or paste a key.

Use an API key instead

In the custom connector dialog, add the request header Authorization: Bearer YOUR_API_KEY. Or, in Claude Desktop, open Settings → Developer → Edit Config and add the stdio proxy (needs Node.js; claude_desktop_config.json only starts local servers, so it cannot hold the remote URL):

{
  "mcpServers": {
    "sheetsdata": {
      "command": "npx",
      "args": ["-y", "@sheetsdata/mcp"],
      "env": { "SHEETSDATA_API_KEY": "YOUR_API_KEY" }
    }
  }
}

Restart Claude. The proxy sends the key in a header, never on the command line.

Docs: Custom connectors using remote MCP

Claude Code

claude mcp add --transport http sheetsdata https://mcp.sheetsdata.com/mcp

Start Claude Code, run /mcp, choose sheetsdata → Authenticate and sign in (or run claude mcp login sheetsdata from your shell). Add --scope user to have SheetsData in every project.

Use an API key instead

claude mcp add --transport http sheetsdata https://mcp.sheetsdata.com/mcp \
  --header "Authorization: Bearer YOUR_API_KEY"

In a project's .mcp.json, give the entry "type": "http"; an entry without a type is treated as a local server.

Docs: Claude Code MCP

ChatGPT

On the web, open chatgpt.com/plugins, click +, then Add custom MCP server. Name it SheetsData, paste https://mcp.sheetsdata.com/mcp and choose OAuth. Accept the warning, choose Create as a plugin, install it and sign in to SheetsData. Your plan and workspace settings decide whether custom servers are available. ChatGPT cannot send an API key.

Docs: Custom MCP servers in ChatGPT

OpenAI Codex

codex mcp add sheetsdata --url https://mcp.sheetsdata.com/mcp
codex mcp login sheetsdata

The second command opens your browser to sign in. The Codex IDE extension and app read the same ~/.codex/config.toml.

Use an API key instead

Add to ~/.codex/config.toml, and set SHEETSDATA_API_KEY in your shell:

[mcp_servers.sheetsdata]
url = "https://mcp.sheetsdata.com/mcp"
bearer_token_env_var = "SHEETSDATA_API_KEY"

Docs: Codex MCP

Cursor

Click **Install in Cursor**, or add to ~/.cursor/mcp.json (every project) or .cursor/mcp.json (one project):

{
  "mcpServers": {
    "sheetsdata": {
      "url": "https://mcp.sheetsdata.com/mcp"
    }
  }
}

Cursor opens your browser to sign in when it first connects.

Use an API key instead

{
  "mcpServers": {
    "sheetsdata": {
      "url": "https://mcp.sheetsdata.com/mcp",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    }
  }
}

Docs: Cursor MCP

VS Code (GitHub Copilot)

Click **Install in VS Code**, run code --add-mcp '{"name":"sheetsdata","type":"http","url":"https://mcp.sheetsdata.com/mcp"}', or add to .vscode/mcp.json (run MCP: Open User Configuration for every workspace):

{
  "servers": {
    "sheetsdata": {
      "type": "http",
      "url": "https://mcp.sheetsdata.com/mcp"
    }
  }
}

Start the server; VS Code asks you to sign in. Use it from Copilot Chat in agent mode.

Use an API key instead

VS Code asks for the key the first time the server starts and keeps it out of the file:

{
  "inputs": [
    { "type": "promptString", "id": "sheetsdata-key", "description": "SheetsData API key", "password": true }
  ],
  "servers": {
    "sheetsdata": {
      "type": "http",
      "url": "https://mcp.sheetsdata.com/mcp",
      "headers": { "Authorization": "Bearer ${input:sheetsdata-key}" }
    }
  }
}

Docs: VS Code MCP configuration

GitHub Copilot CLI

copilot mcp add --transport http sheetsdata https://mcp.sheetsdata.com/mcp

Or run /mcp add in a session, choose HTTP and paste the URL. Copilot CLI signs in with OAuth when the server asks.

Use an API key instead

copilot mcp add --transport http sheetsdata https://mcp.sheetsdata.com/mcp \
  --header "Authorization: Bearer YOUR_API_KEY"

Docs: Adding MCP servers to Copilot CLI

Gemini CLI

gemini mcp add --transport http --scope user sheetsdata https://mcp.sheetsdata.com/mcp

Start Gemini CLI, run /mcp auth sheetsdata and sign in.

Use an API key instead

gemini mcp add --transport http --scope user \
  --header "Authorization: Bearer YOUR_API_KEY" \
  sheetsdata https://mcp.sheetsdata.com/mcp

Editing ~/.gemini/settings.json by hand? Use "httpUrl" for the address; "url" means the older SSE transport.

Docs: Gemini CLI MCP servers

Google Antigravity

Open the … menu → MCP Servers → Manage MCP Servers → View raw config (~/.gemini/config/mcp_config.json, or .agents/mcp_config.json in a workspace) and add:

{
  "mcpServers": {
    "sheetsdata": {
      "serverUrl": "https://mcp.sheetsdata.com/mcp"
    }
  }
}

Antigravity needs serverUrl; it rejects url. Then open Agent settings → Customizations and click Authenticate next to sheetsdata. For an API key, add "headers": { "Authorization": "Bearer YOUR_API_KEY" } to the entry.

Docs: Antigravity MCP

Windsurf (Devin Desktop)

In the Cascade panel, open the … menu → MCPs → Open MCP config file (~/.config/devin/mcp_config.json; %APPDATA%\devin\mcp_config.json on Windows; older Windsurf versions use ~/.codeium/windsurf/mcp_config.json) and add:

{
  "mcpServers": {
    "sheetsdata": {
      "serverUrl": "https://mcp.sheetsdata.com/mcp"
    }
  }
}

You sign in to SheetsData in your browser when it connects. For an API key, add "headers": { "Authorization": "Bearer YOUR_API_KEY" } to the entry.

Docs: Cascade MCP

Zed

Add to your Zed settings.json (or Settings → AI → MCP Servers → Add Server → Add Remote Server):

{
  "context_servers": {
    "sheetsdata": {
      "url": "https://mcp.sheetsdata.com/mcp"
    }
  }
}

Zed asks you to sign in. For an API key, add "headers": { "Authorization": "Bearer YOUR_API_KEY" } to the entry.

Docs: Zed MCP

Cline

Open MCP Servers → Remote Servers, name it SheetsData, paste https://mcp.sheetsdata.com/mcp, choose Streamable HTTP and click Add Server; complete the browser sign-in when prompted. In Cline CLI, run cline mcp and choose Authorize OAuth for sheetsdata.

Use an API key instead

Open MCP Servers → Configure → Configure MCP Servers (cline_mcp_settings.json) and add the entry below. Without "type", Cline assumes SSE.

{
  "mcpServers": {
    "sheetsdata": {
      "type": "streamableHttp",
      "url": "https://mcp.sheetsdata.com/mcp",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    }
  }
}

Or from Cline CLI: cline mcp add sheetsdata https://mcp.sheetsdata.com/mcp --transport http --header "Authorization: Bearer YOUR_API_KEY" --yes

Docs: Cline MCP

Roo Code

Roo Code's docs don't describe MCP OAuth, so use an API key. Open MCP → Edit Global MCP (mcp_settings.json) or the project's .roo/mcp.json:

{
  "mcpServers": {
    "sheetsdata": {
      "type": "streamable-http",
      "url": "https://mcp.sheetsdata.com/mcp",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    }
  }
}

Docs: Using MCP in Roo Code

Continue

Continue's docs don't describe MCP OAuth, so use an API key. Save as .continue/mcpServers/sheetsdata.yaml in your workspace and add SHEETSDATA_API_KEY to your Continue secrets:

name: SheetsData
version: 0.0.1
schema: v1
mcpServers:
  - name: SheetsData
    type: streamable-http
    url: https://mcp.sheetsdata.com/mcp
    requestOptions:
      headers:
        Authorization: "Bearer ${{ secrets.SHEETSDATA_API_KEY }}"

Docs: Continue MCP

Goose

In Goose Desktop, open Extensions → Add custom extension and choose Streamable HTTP with the URL https://mcp.sheetsdata.com/mcp; in the CLI, run goose configure → Add Extension → Remote Extension (Streamable HTTP). Goose runs the OAuth sign-in when it connects. Or add to ~/.config/goose/config.yaml:

extensions:
  sheetsdata:
    name: SheetsData
    type: streamable_http
    uri: https://mcp.sheetsdata.com/mcp
    enabled: true
    timeout: 300

For an API key, add headers: { Authorization: "Bearer YOUR_API_KEY" } to the entry.

Docs: Using extensions in Goose

Amp

amp mcp add sheetsdata https://mcp.sheetsdata.com/mcp

Amp opens your browser to sign in.

Use an API key instead

Add to ~/.config/amp/settings.json (or .amp/settings.json in a project, then run amp mcp approve sheetsdata):

{
  "amp.mcpServers": {
    "sheetsdata": {
      "url": "https://mcp.sheetsdata.com/mcp",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    }
  }
}

Docs: Amp MCP

Kiro

Click **Install in Kiro**, or add to ~/.kiro/settings/mcp.json (or .kiro/settings/mcp.json in a workspace):

{
  "mcpServers": {
    "sheetsdata": {
      "url": "https://mcp.sheetsdata.com/mcp"
    }
  }
}

Kiro asks you to sign in. For an API key, add "headers": { "Authorization": "Bearer YOUR_API_KEY" } to the entry.

Docs: Kiro MCP configuration

JetBrains (Junie and AI Assistant)

Junie (IDE and CLI): add to ~/.junie/mcp/mcp.json (or .junie/mcp/mcp.json in a project), then run /mcp and choose Authorize. For an API key, add "headers": { "Authorization": "Bearer YOUR_API_KEY" }.

{
  "mcpServers": {
    "sheetsdata": {
      "url": "https://mcp.sheetsdata.com/mcp"
    }
  }
}

AI Assistant: its docs describe neither OAuth nor headers for remote servers, so run the local proxy. Open Settings → Tools → AI Assistant → Model Context Protocol (MCP) → Add and paste the stdio entry below.

Docs: Junie MCP, AI Assistant MCP

opencode

Add to opencode.json:

{
  "mcp": {
    "sheetsdata": {
      "type": "remote",
      "url": "https://mcp.sheetsdata.com/mcp",
      "enabled": true
    }
  }
}

opencode signs in automatically, or run opencode mcp auth sheetsdata. For an API key, add "headers": { "Authorization": "Bearer YOUR_API_KEY" } to the entry.

Docs: opencode MCP servers

LM Studio

LM Studio's docs don't describe MCP OAuth, so use an API key. Open the Program tab → Install → Edit mcp.json:

{
  "mcpServers": {
    "sheetsdata": {
      "url": "https://mcp.sheetsdata.com/mcp",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    }
  }
}

Docs: LM Studio MCP

Warp

Open Settings → Agents → MCP servers → + Add and paste:

{
  "sheetsdata": {
    "url": "https://mcp.sheetsdata.com/mcp"
  }
}

Warp opens your browser to sign in when the server starts. For an API key, add "headers": { "Authorization": "Bearer YOUR_API_KEY" } to the entry.

Docs: Warp MCP

Any client that only starts local servers

The @sheetsdata/mcp package (Node.js 18+) proxies stdio to the hosted server. Without SHEETSDATA_API_KEY it opens your browser to sign in with OAuth and caches the token.

{
  "mcpServers": {
    "sheetsdata": {
      "command": "npx",
      "args": ["-y", "@sheetsdata/mcp"],
      "env": { "SHEETSDATA_API_KEY": "YOUR_API_KEY" }
    }
  }
}

From a shell: SHEETSDATA_API_KEY=YOUR_API_KEY npx -y @sheetsdata/mcp, or npx -y @sheetsdata/mcp --api-key YOUR_API_KEY.

Your own code

Connect with the MCP TypeScript SDK over Streamable HTTP (the SDK can also run the OAuth flow):

import { Client } from "@modelcontextprotocol/sdk/client/index.js";
import { StreamableHTTPClientTransport } from "@modelcontextprotocol/sdk/client/streamableHttp.js";

const transport = new StreamableHTTPClientTransport(new URL("https://mcp.sheetsdata.com/mcp"), {
  requestInit: { headers: { Authorization: "Bearer YOUR_API_KEY" } },
});
const client = new Client({ name: "my-agent", version: "1.0.0" });
await client.connect(transport);

const result = await client.callTool({ name: "search_parts", arguments: { query: "TPS54302" } });

Recommended workflow

1. search_parts / find_parts → candidates by part number, keyword or spec
2. get_part_details          → parameters, package, pricing, stock
3. read_datasheet            → "summary" first, then the sections you need
4. check_design_fit          → your operating conditions against the ratings
5. find_alternative          → substitutes, if needed
6. compare_parts             → finalists side by side
7. check_bom                 → lifecycle, stock and sourcing for the whole BOM

Support

• Email: support@sheetsdata.com
• Issues: github.com/octoco-ltd/sheetsdata-mcp/issues
• Docs: sheetsdata.com/help

Disclaimer

Data is extracted from publicly available manufacturer datasheets by automated tools, including AI. It may contain errors, omissions or inaccuracies.

SheetsData and Octoco Ltd provide this data on an "as is" basis and make no warranties, express or implied, regarding its accuracy, completeness or fitness for any particular purpose. Always verify critical specifications against the official manufacturer datasheet before making design, purchasing or manufacturing decisions.

By using this service, you acknowledge that:

• Extracted data may differ from the original manufacturer datasheet
• SheetsData is not a substitute for reviewing official documentation
• Octoco Ltd is not liable for any damages, losses, or design failures arising from the use of this data
• Features, APIs and pricing may change

For terms of use, see sheetsdata.com/terms.

License

MIT (this repository: install configs, the npm proxy and the Claude Desktop bundle). The hosted service is covered by the terms of use.