RoboParts MCP MCP server

RoboParts is a vendor-neutral compatibility checking layer for open-source robot parts. It allows agents to verify mechanical, electrical, protocol, and ROS compatibility between components, generate 3D-printable adapters for incompatible parts, and access a database of humanoid and bionic robot parts.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by RoboParts

MCP endpoint (Streamable HTTP)

https://roboparts.cc/mcp

Vendor documentation

What you can do with it

Check BOM compatibility between robot components
Generate 3D printable adapter STL files
Search for compatible motors and sensors
Validate ISO 9409-1 flange standards

Tools advertised by the last live check:

search_components
get_component_detail
check_compatibility
compare_components
recommend_for_application
get_parameter_semantics
bom_compatibility_check
semantic_search
get_standard_audit
review_compatibility
lint_urdf
explain_compose_frontier
explain_evidence_cohort
explain_evidence_mdv
explain_connector_types
get_research_progress
check_co_mount
get_robot_tool_side
get_behavior_evidence
get_body_binding

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http roboparts-mcp https://roboparts.cc/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add roboparts-mcp --url https://roboparts.cc/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable roboparts-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "roboparts-mcp": {
      "url": "https://roboparts.cc/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "roboparts-mcp": {
      "type": "streamableHttp",
      "url": "https://roboparts.cc/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start roboparts-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "roboparts-mcp": {
      "type": "http",
      "url": "https://roboparts.cc/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http roboparts-mcp https://roboparts.cc/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "roboparts-mcp": {
      "url": "https://roboparts.cc/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "roboparts-mcp": {
      "serverUrl": "https://roboparts.cc/mcp"
    }
  }
}

See all 957

Do you run RoboParts MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing