Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Client teams' blueprints for coding agents (token from an engagement). Free: agentblueprint.ai/mcp
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
AGENT_BLUEPRINT_API_KEYValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"agent-blueprint": {
"command": "npx",
"args": [
"-y",
"agentblueprint"
],
"env": {
"AGENT_BLUEPRINT_API_KEY": "your-value"
}
}
}
}Run this in your terminal
claude mcp add agent-blueprint --env AGENT_BLUEPRINT_API_KEY=your-value -- npx -y agentblueprintFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"agent-blueprint": {
"command": "npx",
"args": [
"-y",
"agentblueprint"
],
"env": {
"AGENT_BLUEPRINT_API_KEY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"agent-blueprint": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"agentblueprint"
],
"env": {
"AGENT_BLUEPRINT_API_KEY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account agent-blueprint, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: AGENT_BLUEPRINT_API_KEY
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.7.23) reached the registry 3 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, FlyDocs
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Spec-driven development workflow: your agent works issues, sessions and the status lifecycle.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
CLI and MCP server for Agent Blueprint. Create structured business profiles, generate pipeline artifacts, explore blueprint data, sync implementation state, and download full Agent Skills directories. Vendor-agnostic output works with ServiceNow, Salesforce, OpenClaw, or any platform.
Agent Blueprint is delivered through hands-on engagements; API tokens are issued to client teams. If your organization works with Agent Blueprint, this package connects your coding agents to your blueprint registry.
Not a client? You don't need this package. Agent Blueprint also has free tools that need no account or token:
https://agentblueprint.ai/mcp (Streamable HTTP). No sign-in, read-only, keeps nothing. Tools: list_benchmark_jobs, estimate_agent_cost, check_agent_one_page, render_agent_map. Instructions for agents are at agentblueprint.ai/agents.# Install globally
npm install -g agentblueprint
agentblueprint login
agentblueprint list
agentblueprint get blueprint
agentblueprint get business-case agentblueprint get use-case agentblueprint get implementation-plan agentblueprint get implementation-spec agentblueprint get business-profile
agentblueprint download
agentblueprint list --org agentblueprint get blueprint --org
Or run without installing via npx:
npx agentblueprint list --token <your-api-key>
npx agentblueprint get blueprint --token
The same binary auto-detects MCP mode when stdin is piped (non-interactive). No separate command needed.
Add to your Claude Code MCP config (.claude/settings.json or project settings):
{
"mcpServers": { "agent-blueprint": { "command": "npx", "args": ["-y", "agentblueprint", "serve"], "env": { "AGENT_BLUEPRINT_API_KEY": " " } } } }
You can also start the MCP server explicitly with agentblueprint serve.
API access comes with an Agent Blueprint engagement. If your organization is a client:
Not a client yet? Get in touch at agentblueprint.ai.
Current scope is intentionally narrow:
existing PAT + existing org -> create_business_profile -> generate_use_cases -> generate_blueprint or trigger_full_pipeline -> get_generation_status -> download_blueprint
This release does not handle organization creation, OAuth bootstrap, or free-form context extraction into the business profile.
Download a blueprint as a local Agent Skills directory that any coding agent can read from the filesystem. This is the recommended way to work with blueprints.
# Using the CLI (after `agentblueprint login`)
agentblueprint download agentblueprint download --dir ./my-skills
npx agentblueprint download --token --blueprint
This creates an Agent Skills directory structure:
.agent-blueprint/<blueprint-slug>/
├── SKILL.md # Overview + frontmatter (auto-discovered by agents) ├── references/ │ ├── business-context.md # Use case, pain points, transformation story │ ├── agent-specifications.md # Full agent specs with tools, guardrails, metrics │ ├── financial-case.md # ROI, cost breakdown, sensitivity, 5-year projection │ ├── implementation-roadmap.md # Epics, stories, timeline, roles, dependencies │ ├── architecture-decisions.md # Platform, pattern, integration gaps, feasibility │ └── guardrails-and-governance.md # Risks, mitigation, per-agent guardrails └── scripts/ └── validate-spec.sh # Structure completeness checker
The Agent Skills standard is supported by Claude Code, Codex, Cursor, GitHub Copilot, Windsurf, and 18+ other coding agents. SKILL.md loads automatically at activation (~100 tokens), reference files load on demand.
| Tool | Description |
|---|---|
create_business_profile | Create or upsert a structured business profile for an existing organization |
generate_use_cases | Generate normalized use cases from the current business profile and readiness assessment |
generate_blueprint | Start blueprint generation for a chosen use case and return an auditId |
trigger_full_pipeline | Start the full pipeline for an existing business profile and return a jobId |
get_generation_status | Poll either blueprint generation or full-pipeline generation status |
list_blueprints | List all blueprints (summaries) |
get_blueprint | Blueprint summary — title, agents, phases, pattern |
get_business_case | Business case summary — ROI, pilot economics, recommendation |
get_implementation_plan | Implementation plan summary — epics, timeline, story counts |
get_use_case | Use case analysis for a blueprint |
get_implementation_spec | Implementation spec metadata |
get_business_profile | Organization business profile |
download_blueprint | Download full blueprint as Agent Skills file manifest |
The generate_blueprint and trigger_full_pipeline tools are asynchronous. Use get_generation_status to poll until the run completes, then call download_blueprint with the resolved blueprintId.
The get_blueprint, get_business_case, and get_implementation_plan tools return concise summaries optimized for agent context windows. For full details (agent specs, financial projections, user stories), use download_blueprint to get the complete Agent Skills directory.
| URI | Description |
|---|---|
agentblueprint://blueprints | Blueprint list (JSON) |
agentblueprint://blueprints/{id} | Blueprint detail (Markdown) |
agentblueprint://blueprints/{id}/spec | Implementation spec (Markdown) |
Three ways to provide your API token (checked in this order):
--token flag on any commandAGENT_BLUEPRINT_API_KEY environment variableagentblueprint login (saved to ~/.config/agentblueprint/config.json)| Variable | Required | Default | Description |
|---|---|---|---|
AGENT_BLUEPRINT_API_KEY | No | — | Your API token (alternative to agentblueprint login) |
AGENT_BLUEPRINT_API_URL | No | https://app.agentblueprint.ai | API base URL |