Add an MCP server: RoboPartPicker (remote, robotics projects + BOMs)

Open Beginner friendly
#1,918 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
76/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
go

Research direction

Read the existing atlassian-remote, box-remote, and datadog-remote entries to find the registry manifest pattern for hosted Streamable HTTP servers. Add RoboPartPicker using the manifest, client config, and install notes described in the issue, then check it against the registry inclusion heuristics. Done when the catalog entry captures the endpoint and setup details and passes the repository's validation.

Written by the indexing model from the issue text.

Description

needs-triage

MCP Server Information

Server Name: RoboPartPicker
Repository URL: https://github.com/brainbook0/robopartpicker-mcp
Brief Description: Public, read-only MCP server over a source-linked catalogue of 2,445 open-source robotics projects and their bills of materials. Agents can search projects and components, fetch a project with its BOM summary, compare parts, and validate RPPS documents. Hosted remote server (Streamable HTTP, no authentication for public reads).

Basic Requirements

  • Open Source: Uses acceptable license (Apache-2.0, MIT, BSD-2-Clause, BSD-3-Clause or other permissive license)
  • MCP Compliant: Implements MCP API specification
  • Active Development: Recent commits and maintained
  • Documentation: Basic README and setup instructions
  • Security Contact: Method for reporting security issues

Submitter Checklist

Details

  • Type: Remote server (remotes, Streamable HTTP) — the implementation is a hosted Cloudflare Worker; the linked repository holds the registry manifest, client config and install notes (same pattern as the existing atlassian-remote / box-remote / datadog-remote entries).
  • Endpoint: https://robopartpicker.com/mcp
  • Registry name (Official MCP Registry, already published): com.robopartpicker/robopartpicker v1.0.0, status: active
  • License: MIT (LICENSE file at the linked repository root)
  • Documentation: README lists each tool and setup; https://robopartpicker.com/developers
  • Security contact: [email protected]
  • Tools (5):
    • search_projects — search open robotics projects by keyword, category or kind
    • get_project — fetch one project with source repo, license, files and BOM summary
    • search_components — search the technical component catalogue by name, category or maker
    • compare_components — compare two to four components (same category never implies verified drop-in compatibility)
    • validate_rpps — validate a Robotics Project Package Specification document

Verified live (2026-11-10): initialize → 200 with serverInfo { name: "RoboPartPicker", version: "0.7.0" }; tools/list → 5 tools; tools/call search_projects { query: "quadruped" } → real project rows. No API key required for public reads. Every BOM line carries an explicit evidence state (verified / probable / unresolved); unresolved lines are shown, not guessed.

Dominant language
Go
Stars
26
Forks
104
Avg merge
1d 4h
Merged PRs (30d)
69

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from stacklok/toolhive-catalog

All issues in stacklok/toolhive-catalog

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.