RoboPartPicker

Official registry AI and agents

Source-linked robotics projects, bills of materials and components for AI agents.

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code
claude mcp add --transport http robopartpicker 'https://robopartpicker.com/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "robopartpicker": {
            "type": "http",
            "url": "https://robopartpicker.com/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. RoboPartPicker MCP server
  2. Tools
  3. Connect a client
  4. Example
  5. What the data is, honestly
  6. License

RoboPartPicker MCP server

Remote Model Context Protocol server for RoboPartPicker — a catalog of source-linked robotics projects, bills of materials and components.

  • Endpoint: https://robopartpicker.com/mcp (Streamable HTTP, no auth for public reads)
  • Registry name: com.robopartpicker/robopartpicker
  • Product repository: brainbook0/robopartpicker
  • Discovery: https://robopartpicker.com/.well-known/mcp.json
  • Server card: https://robopartpicker.com/.well-known/mcp/server-card.json
  • OpenAPI: https://robopartpicker.com/openapi.json

This repository holds the registry manifest and client configuration for the hosted server. The server itself runs on Cloudflare Workers at robopartpicker.com.

Tools

ToolWhat it does
search_projectsSearch open robotics projects by keyword, category or kind.
get_projectFetch one project with its source repo, license, files and BOM summary.
search_componentsSearch the technical component catalog by name, category or maker.
compare_componentsCompare two to four components. Same category never implies verified drop-in compatibility.
validate_rppsValidate a Robotics Project Package Specification (RPPS) document.

Connect a client

Claude Desktop / Cursor / Cline
{
  "mcpServers": {
    "robopartpicker": {
      "type": "streamable-http",
      "url": "https://robopartpicker.com/mcp"
    }
  }
}
Claude Code
claude mcp add --transport http robopartpicker https://robopartpicker.com/mcp
Verify without a client
curl -s https://robopartpicker.com/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"curl","version":"1.0"}}}'

A healthy response reports serverInfo.name = RoboPartPicker and a tools capability.

Example

Ask an agent: "Find an open 6-axis robot arm project with a bill of materials, and tell me which BOM lines are still unresolved." A search_projects call with q=rover returns entries such as:

{
  "slug": "nasa-jpl-open-source-rover",
  "name": "NASA JPL Open Source Rover",
  "license": "Apache-2.0"
}

What the data is, honestly

  • BOM lines are derived from explicit BOM files, documentation, CAD metadata and URDF/robot-description files in each upstream repository. Every line keeps its evidence state — verified, probable, unresolved, unpriced — instead of being silently dropped.
  • Prices are observed catalog data, not quotes. Supplier coverage is partial and prices drift.
  • Upstream projects keep their own licenses. This server reads and links; it does not relicense anyone's design.
  • Software projects, commercial models without manufacturer BOMs, and physical projects without an explicit BOM report distinct honest states rather than guessed parts.

License

The contents of this repository (manifest, documentation, configuration) are MIT licensed. Robotics project data returned by the API remains subject to each upstream project's own license.

Frequently asked questions

What is RoboPartPicker?

Source-linked robotics projects, bills of materials and components for AI agents.

How do I install RoboPartPicker?

It runs as a remote server. In Claude Code: claude mcp add --transport http robopartpicker 'https://robopartpicker.com/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does RoboPartPicker need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is RoboPartPicker open source?

Its code is public on GitHub, but the repository does not declare a standard license.

Who maintains RoboPartPicker?

It is published by brainbook0. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.