copperflow
Related Servers
Alternatives to copperflow
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceMCP server enabling AI agents to collaborate in shared rooms with a document edited via compare-and-swap optimistic concurrency, plus a chat channel and change deltas.-

forge-orchestratorofficial
FlicenseNot gradedqualityAmaintenanceEnables orchestrating multiple AI coding tools (Claude Code, Codex CLI, Gemini CLI) on shared repositories with file locking, knowledge capture, task planning, and drift detection via an MCP server.166-- AlicenseAqualityDmaintenanceEnables multiple AI agents to coordinate work on the same codebase by providing real-time file locking, commit approval, and agent awareness through a lightweight WebSocket-based MCP server.917 npm11MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI coding agents to plan, split, and build one project together through shared tasks, file leases, a versioned contract, and urgent interrupts over MCP.MIT
- FlicenseNot gradedqualityAmaintenanceEnables MCP-compatible editors to run dialectical reasoning through thesis, antithesis, and synthesis, and to build verified code via a player-coach loop with independent review and session state.-
- AlicenseNot gradedqualityAmaintenanceEnables AI agents and humans to collaboratively manage kanban boards and Markdown documentation via MCP tools, with stable item keys, revision-safe editing, and full audit trails.AGPL 3.0
TDQS
Scored across 57 tools
There are clear but overlapping tool families: connect_nets, add_trace, route_track and edit_circuit wire_corners all relate to connections; copper_summary, board_summary, circuit_summary and project_status all summarize state; and export_fabrication, export_model, export_html and export_package all export. The descriptions do distinguish schematic trace from copper track and give hints, but with 57 tools an agent can easily pick a near-miss sibling.
Almost all tools use snake_case verb_noun or noun pairs (set_project, add_trace, remove_copper, export_fabrication), with only minor deviations such as noun-only bom, render and guide, plus new_circuit versus the usual create/import pattern. The naming is predictable enough that an agent can guess tool names reliably.
57 tools is far above a comfortable range, even for a complex PCB design domain. Several clusters could be consolidated (four export_* tools, three summary tools, multiple connection and module tools), so the count feels heavy and increases selection cost.
The surface covers a broad lifecycle: project intent, circuits, parts, placement, routing, copper, pours, holes, rules, simulation, checking, fabrication exports, modules and undo/redo. Minor gaps remain, such as no explicit circuit file deletion or rename, no library part removal, and no tool for locking a part despite lock-aware tools elsewhere.