Source Parts
Look up electronic parts, validate BOM lines, and run sourcing workflows from your coding agent while designing hardware.
Overview
Source Parts MCP is an MCP server for the Build phase that connects agents to electronic component sourcing, BOM management, and PCB design workflows via Source Parts.
What is this MCP server?
- Streamable HTTP remote at mcp.source.parts plus local stdio via uvx/PyPI package parts-mcp
- BOM management and electronic component search aligned with PCB design workflows
- Requires a Source Parts API key from source.parts/docs/api
- Version 0.4.0 with GitHub repository SourceParts/parts-mcp
- Server version 0.4.0
- Two deployment paths: streamable-http remote and PyPI stdio via uvx
- One required secret: Source Parts API key
Community signal: 1 GitHub stars.
What problem does it solve?
Agent-assisted hardware work stalls when part numbers, stock, and BOM lines live only in browser tabs outside the coding session.
Who is it for?
Indie hardware builders, EE hobbyists, and agent users iterating PCBs who already have a Source Parts API key.
Skip if: Pure software SaaS projects with no BOM or physical components, or teams that cannot use external parts APIs.
What do I get? / Deliverables
Your agent can query and manage component data through MCP so BOM and sourcing steps stay inside the same build conversation.
- Agent-callable tools for component lookup and BOM-oriented workflows
- Unified remote or stdio MCP transport to Source Parts
- Documented package version 0.4.0 alignment with registry schema
Recommended MCP Servers
Journey fit
Hardware and electronics solo builders wire component data into the product during active development, not during abstract idea research alone. The server exposes Source Parts APIs for BOM management and PCB-related sourcing—classic third-party integration work in the build phase.
How it compares
Parts-sourcing MCP integration, not a KiCad plugin or inventory ERP.
Common Questions / FAQ
Who is Source Parts MCP for?
Solo builders and small teams designing electronics who want agents to search parts and work with BOMs via Source Parts.
When should I use Source Parts MCP?
During Build when you are selecting components, cleaning a BOM, or aligning PCB design choices with real distributor data.
How do I add Source Parts MCP to my agent?
Add the remote URL https://mcp.source.parts/ or configure the PyPI package parts-mcp with uvx stdio and set your Source Parts API key environment variable.