design-flow-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DESIGN_FLOW_PROJECT_ROOT | Yes | The only directory projects may occupy. Relative paths are resolved below it. Parent traversal, absolute escapes, and detectable symlink escapes are rejected. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| readinessA | Read-only. Report adapter/engine versions, root confinement, and active-project status. Changes no semantic authority. |
| new_projectB | Mutating setup operation. Create a project through the engine and start its Design Flow session. It invents no decisions and creates no decision authority. |
| resume_projectA | Mutating session operation. Validate and open an existing engine project, then resume/start its Design Flow session. It never repairs invalid persisted state. |
| get_stateA | Read-only. Return concise state compiled by Design Flow. Requires an active project and cannot alter decisions, TRACE, or persistence. |
| get_unresolvedA | Read-only. Return the engine's canonical unresolved register. Requires an active project and does not reconstruct or change authority. |
| get_roundA | Read-only. Return the active draft summary and latest committed round. Requires an active project and cannot edit either record. |
| import_draftA | Mutating working-state operation. Import exactly one structured object or allowed-root file through engine draft intake. It does not commit a decision or change semantic authority. |
| preview_roundA | Read-only simulation. This is non-authoritative and does not commit any decision. Requires an active draft and uses the engine preview path only. |
| lock_roundA | Authority-changing operation. This commits owner-approved draft state through the Design Flow semantic engine and changes authoritative project state. Requires a complete valid draft; failures preserve it. |
| compile_context_handoffA | Read-only. Compile Context Handoff content with the engine compiler. Requires an active project and cannot rewrite semantic state. |
| compile_living_documentA | Read-only. Compile the Living Application Document with the engine renderer. Requires an active project and cannot rewrite semantic state. |
| recommend_next_roundA | Read-only advisory operation. Return the engine's bounded recommendation. It is non-authoritative and never starts a round. |
| end_sessionA | Mutating session operation. End the active Design Flow session safely through the engine. It does not mark the project complete or commit a draft. |
| get_decision_ledgerB | Read-only. Return a concise engine decision-ledger view. It exposes no mutation capability. |
| get_conceptsB | Read-only. Return concise current, affected, and historical engine concepts. It exposes no mutation capability. |
| get_traceA | Read-only. Return engine-owned TRACE records. No tool can append, edit, or delete TRACE directly. |
| get_session_briefA | Read-only. Return the engine session brief and semantic session identity. It does not conflate the MCP connection with the Design Flow session. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| active_state | Current Design Flow state compiled by the engine. |
| active_unresolved | Canonical unresolved register compiled by the engine. |
| active_context_handoff | Context Handoff compiled by the engine. |
TDQS
Scored across 17 tools
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.
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.
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.
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.