Blueprint MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": true
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| blueprint.scanC | Public tool that builds a file inventory, analyzes parseable code, and returns the analysis artifact for grouping. |
| blueprint.groupA | Prepare mode returns a compact packet for semantic grouping; it is not the final grouping. The LLM should treat folder names as hints, not truth, and group by responsibility, runtime role, data flow, and dependencies. Prefer glob patterns like folder/** instead of enumerating files, and use exact file paths only for entry points, exceptions, or cross-cutting files. Apply mode consumes a small LLM-authored GroupingPlan and deterministically assigns files. |
| blueprint.group.updateA | Apply LLM group decisions after a Blueprint refresh. Use this tool only for assigning unassigned files to existing groups, creating a new group for unassigned files, or deleting groups that are already empty. Do not use this tool for updated files already assigned to a real group, deleted file cleanup, editing markdown memory, or rewriting blueprint-output.json manually. Validation rules: assignments[].fileId must refer to a file whose groupId is "unassigned"; assignments[].groupId must be an existing group id; newGroups[].id must not already exist; newGroups[].fileIds must all be unassigned file ids; deleteGroups[] may only contain groups with no fileIds. The tool writes .blueprint/blueprint-output.json and creates group markdown templates for new groups. |
| blueprint.refreshA | Deterministically refresh .blueprint/blueprint-output.json from the current filesystem snapshot. The tool compares .blueprint/refresh-scan.json with a fresh full scan, writes refreshed Blueprint JSON and scan state, and returns the maintenance prompt the assistant should follow. It does not send raw git diffs to the assistant. Use blueprint.group.update afterwards only for unassigned files or empty group decisions, then update affected group Markdown docs. |
| blueprint.composeA | Compose the final frontend-ready Blueprint JSON from a grouping artifact. If the response contains assistantNextSteps with required=true and executionPolicy=must_execute_before_final_response, the assistant must execute those steps before giving the user a final answer. For hydrate-group-docs, spawn one sub-agent per target group doc when sub-agents are available; otherwise edit the target docs yourself. Do not ask the user unless the required step is impossible. |
| blueprint.task_contextB | Return a compact deterministic context slice for a natural-language task from a Blueprint output artifact. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| blueprint-create-grouping-plan | Create a compact semantic GroupingPlan JSON from a blueprint.group prepare packet. Use this before calling blueprint.group in apply mode. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct operation: compose finalizes output, group handles semantic grouping, group.update applies post-refresh decisions, refresh updates from filesystem, scan builds inventory, and task_context retrieves context. No two tools overlap in purpose.
All tools follow a consistent 'blueprint.<verb>' or 'blueprint.<verb>.<subverb>' pattern (e.g., blueprint.compose, blueprint.group.update). The naming is predictable and hierarchical.
With 6 tools covering scanning, grouping, refreshing, composing, and context retrieval, the count is well-scoped for the domain of Blueprint artifact management. Each tool earns its place.
The set covers the core lifecycle: scan, group, update groups, refresh, compose final output, and retrieve task context. A minor gap is the lack of a tool to explicitly delete or list groups, but the workflow seems complete for typical use.