Add an MCP server: RoboPartPicker (remote, robotics projects + BOMs)
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
- Domain
- ai-infra-agents, tooling
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
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
- I have read the MCP Server Registry Inclusion Heuristics
- This server meets the basic requirements listed above
- I understand this will undergo automated and manual review based on Registry Management
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 existingatlassian-remote/box-remote/datadog-remoteentries). - Endpoint:
https://robopartpicker.com/mcp - Registry name (Official MCP Registry, already published):
com.robopartpicker/robopartpickerv1.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 kindget_project— fetch one project with source repo, license, files and BOM summarysearch_components— search the technical component catalogue by name, category or makercompare_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
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from stacklok/toolhive-catalog
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
stacklok/toolhive-catalog#1967 ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
stacklok/toolhive-catalog#1929 · 1 comment ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 1/5 1-3 hours Newbie friendliness 76/100
stacklok/toolhive-catalog#1914 ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
stacklok/toolhive-catalog#1909 ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
stacklok/toolhive-catalog#1908 ·
Maintainers usually reply within 1 day
All issues in stacklok/toolhive-catalog
Similar issues
-
area/networking kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
siderolabs/talos#14972 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
kubectl wait outputs cryptic "error: unrecognized condition: []" when --for is omittedPossibly taken @muskan-creates352 claimed this today. Openkind/bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
kubernetes/kubectl#1910 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
unbound-force/gaze#353 ·
Maintainers usually reply within 1 day
-
bug cross-seed ready-for-human
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day