loading…
Search for a command to run...
loading…
8 MCP tools for exploring and downloading AI agent blueprints. List blueprints, get summaries, download full Agent Skills directories for implementation by codi
8 MCP tools for exploring and downloading AI agent blueprints. List blueprints, get summaries, download full Agent Skills directories for implementation by coding agents. Vendor-agnostic output works with any enterprise platform. Install: npx agentblueprint.
CLI and MCP server for Agent Blueprint — 23 MCP tools for creating structured business profiles, generating pipeline artifacts, exploring blueprint data, syncing implementation state, and downloading full Agent Skills directories. Vendor-agnostic output works with ServiceNow, Salesforce, OpenClaw, or any platform.
# Install globally
npm install -g agentblueprint
# Store your API token (one-time)
agentblueprint login
# List blueprints
agentblueprint list
# Get a blueprint summary (JSON to stdout)
agentblueprint get blueprint <id>
# Get other artifacts
agentblueprint get business-case <id>
agentblueprint get use-case <id>
agentblueprint get implementation-plan <id>
agentblueprint get implementation-spec <id>
agentblueprint get business-profile
# Download as Agent Skills directory
agentblueprint download <id>
# Partner cross-org access
agentblueprint list --org <customer-org-id>
agentblueprint get blueprint <id> --org <customer-org-id>
Or run without installing via npx:
npx agentblueprint list --token <your-api-key>
npx agentblueprint get blueprint <id> --token <your-api-key>
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": ["@agentblueprint/mcp-server"],
"env": {
"AGENT_BLUEPRINT_API_KEY": "<your-api-key>"
}
}
}
}
You can also start the MCP server explicitly with agentblueprint serve.
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 <id>
agentblueprint download <id> --dir ./my-skills
# Or via npx
npx agentblueprint download --token <key> --blueprint <id>
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 <key> 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 |
Добавь это в claude_desktop_config.json и перезапусти Claude Desktop.
{
"mcpServers": {
"agent-blueprint-mcp-server": {
"command": "npx",
"args": []
}
}
}pro-tip
Поставил agent-blueprint/mcp-server? Скажи Claude: «запомни почему я установил agent-blueprint/mcp-server и что хочу попробовать» — попадёт в твой Vault.
как это работает →