A
licenseNot graded
qualityB
maintenanceSelf-hosted MCP server that enables ChatGPT agents to perform health checks, fetch design request context, and submit agent results back to a design system backend.
1 npm
1
Apache 2.0
design-flow-mcp
by fargo161
Related Servers
Alternatives to design-flow-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceThis MCP server enables AI agents to understand and analyze electrical schematics from Cadence and Altium for comprehensive design reviews through natural conversations.557 npm43Apache 2.0
- AlicenseNot gradedqualityAmaintenanceAn MCP server for AI-assisted project development and tracking. It exposes a typed graph of design nodes (concepts, decisions, requirements, etc.) and edges to Claude Code, enabling structured management of project knowledge and report generation.3Apache 2.0
- FlicenseNot gradedqualityAmaintenanceAn MCP server that gives an AI agent read and write access to a live SysML v2 model through the vendor-neutral OMG SysML v2 REST API.2-
- 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 creating, modifying, and analyzing KiCAD schematic files using natural language.20MIT
TDQS
A3.9/5.0
Scored across 17 tools
Disambiguation4/5
Most tools target clearly distinct resources: sessions, drafts, rounds, trace, decisions, concepts, and compiled documents. The main ambiguity is among the many read-only 'get' tools, especially get_state, get_round, and get_session_brief, though their descriptions do provide enough separation for a careful agent.
Naming Consistency4/5
The overwhelming majority follow a clear verb_noun pattern such as new_project, resume_project, import_draft, lock_round, and get_trace. 'readiness' is a notable outlier since it is a noun rather than a verb-led command, and get_unresolved is slightly elliptical, but the overall convention is predictable.
Tool Count4/5
At 17 tools, the server is slightly above the ideal 3-15 range but still reasonably scoped for a workflow engine with distinct lifecycle, draft, review, and introspection concerns. A few of the read-only getters could potentially be consolidated, but none feel redundant.
Completeness4/5
The core Design Flow lifecycle is well covered: project creation/resume/session end, draft import, preview, round locking, recommendations, and multiple read-only views. Obvious gaps include the lack of any explicit discard/abort/cancel operation or project listing/deletion, but the primary workflow appears navigable without dead ends.
Maintenance
ActivitySlowing
ResponsivenessNo issues