vibe-hardware-mcp
Related Servers
Alternatives to vibe-hardware-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceMCP server exposing KiCad PCB Editor functionality via IPC API.4159 PyPI1MIT
- AlicenseBqualityDmaintenanceMCP server that analyzes, reviews, and exports KiCad 9 designs, with live board editing via IPC and a built-in design-review engine.471MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that gives AI agents end-to-end control of KiCad 9+ for rule checks, manufacturing exports, production-readiness certification, and live PCB editor control.MIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that exposes KiCad PCB design automation tools to AI assistants and other MCP clients.-
- AlicenseNot gradedqualityDmaintenanceMCP server for KiCad 10 that enables AI assistants to inspect and control schematics and PCB layouts in real-time using the official kipy Python bindings.109 PyPI1MIT
- AlicenseAqualityAmaintenanceMCP servers for KiCad schematic, PCB, symbol, footprint, and project automation, enabling AI-assisted electronic design via tools for read/write, analysis, and exports.109349 PyPI16GPL 3.0
TDQS
Scored across 15 tools
The local analysis tools (analyze_kicad_pcb, analyze_specctra_dsn, calculate_pcb_trace_impedance, audit_pcb_dfm_rules) are cleanly distinct, but calligraphy_route_pcb is explicitly declared an alias of calligraphy_compile_board, so two tools do the same thing. The payment surface is also crowded: a Stripe URL returned by compile, calligraphy_create_coinbase_checkout, and calligraphy_verify_stablecoin_payment overlap in purpose, forcing an agent to reason about which checkout path to take. Descriptions are verbose enough to recover, but the boundaries are not self-evident.
Everything is snake_case with a verb_noun shape, which is easy to read. The deviation is the two-family split: local utilities use bare verb prefixes (analyze_, calculate_, audit_) while the commercial flow is uniformly calligraphy_-prefixed, and calligraphy_route_pcb does not match the verb used by its own alias target compile_board. Minor, but it slightly breaks the predictable pattern.
Fifteen tools is a reasonable scope for a PCB analysis plus fab-compile/payment pipeline, and each of the analysis and lifecycle tools earns its place. The one redundant slot is the route_pcb alias, which inflates the count without adding capability.
The commercial lifecycle is well covered end to end: quote, compile, job status, three payment routes, bundle download, B2B invoice, vault purge, and rate-limit escalation, plus local KiCad/Specctra analysis, impedance, and DFM checks. Gaps are minor — no explicit cancel/refund or re-issue tool, and local analysis supports only KiCad and Specctra despite upload support for Altium/Allegro/tscircuit. Agents can work around these, but they are genuine dead ends.