Back to Browse

Robopartpicker MCP Server

Developer ToolsLow Risk10.0MCP RegistryRemote
Free

Server data from the Official MCP Registry

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

About

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

Remote endpoints: streamable-http: https://robopartpicker.com/mcp

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.

5 tools verified · Open access · No issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "com-robopartpicker-robopartpicker": {
      "url": "https://robopartpicker.com/mcp"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

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.

Reviews

No reviews yet

Be the first to review this server!