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.4147 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.1MIT
- AlicenseAqualityAmaintenanceMCP servers for KiCad schematic, PCB, symbol, footprint, and project automation, enabling AI-assisted electronic design via tools for read/write, analysis, and exports.109426 PyPI16GPL 3.0
TDQS
Scored across 15 tools
Most tools have clearly distinct roles (local analysis vs. DFM audit vs. impedance calc vs. job/payment lifecycle), but calligraphy_route_pcb is explicitly declared an alias of calligraphy_compile_board, creating a genuine duplicate entry an agent could misselect. There is also soft overlap between calligraphy_preflight_audit and analyze_kicad_pcb (both ingest the same file modes and inspect readiness), and between calligraphy_lookup_b2b_invoice and calligraphy_get_job_status.
All names are snake_case with a verb-first construction (analyze_, calculate_, audit_, calligraphy_compile_board, calligraphy_get_job_status), and the calligraphy_ prefix cleanly marks the hosted service namespace versus local tools. Minor deviations: calligraphy_preflight_audit is noun-noun rather than verb_noun, and the 'pcb' token floats inconsistently (analyze_kicad_pcb vs audit_pcb_dfm_rules vs calligraphy_route_pcb).
15 tools sits at the top of the comfortable range and each maps to a real step: local analysis, impedance/DFM checks, compile, status, payment (Stripe/Coinbase/stablecoin), download, invoice, purge, whitelist. The only clearly unearned slot is the redundant calligraphy_route_pcb alias, making it slightly bloated for the underlying workflow.
The surface covers a full lifecycle: input parsing (KiCad, Specctra), local physics/DFM analysis, compile/route, job status polling, three payment paths (Stripe checkout URL, Coinbase/x402, stablecoin tx verification), artifact download, invoicing, and vault destruction. Only marginal gaps exist (no job cancellation/refund or multi-job listing), which agents can work around via job_id status calls.