06 — API & Agents · 10 tools · 1,996 capabilities
Use the catalog from an agent
Every sheet here is also data. Agents connect over the Model Context Protocol at /mcp; code reads the static JSON under /api/v1. Both are public, read-only and free. Content is CC BY 4.0 — cite the url in each answer.
MCP · Streamable HTTP
Add it to any MCP client that speaks HTTP. Stateless, JSON responses, no key.
{
"mcpServers": {
"blueprint-catalog": {
"type": "http",
"url": "https://catalog.mikereams.com/mcp"
}
}
}Claude Code: claude mcp add --transport http blueprint-catalog https://catalog.mikereams.com/mcp
Try it from a terminal
curl -s https://catalog.mikereams.com/mcp \
-H 'content-type: application/json' \
-H 'accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
"params":{"name":"capability_get","arguments":{"id":"BC-740.40"}}}'Discovery: /llms.txt · /.well-known/api-catalog
// FIG. 08 · Tools
catalog_search
Full-text search across business capabilities, macro domains, value streams, products, patterns, stacks and books. Returns ids, kinds, names and canonical URLs, best match first.
query · kinds? · limit?
capability_get
One business capability with its description, aliases, scope, CSDM note, ancestors, children and crosswalk (products that realize it, value-stream stages that use it, patterns/stacks/books that build it).
id
capability_tree
Without a root: every L1 with its macro domain and industry. With a root: that capability's subtree to the requested depth.
root? · depth?
capability_crosswalk
For a capability: which product capabilities realize it, which value-stream stages use it, which patterns, stacks and books help build it — including via its descendants (the `via` field names the descendant).
id
value_stream_get
A value stream with its trigger, outcome and ordered stages; each stage lists the capabilities it relies on.
id
product_get
A vendor product with its product capabilities and the business capabilities each realizes. Coverage and maturity are the catalog's judgment, not the vendor's claim.
id
product_coverage
For one or more products: per L1 capability, how many of each product's capabilities realize something beneath it. Use it to compare products or find gaps.
product_ids
reading_path
For a capability: the design patterns, reference stacks and books that help build it (directly or via descendants), with canonical links.
capability_id
macro_list
The eight macro domains (the executive layer) with their L1 capabilities, plus the industries the catalog covers.
no arguments
export
Capabilities shaped for import into another tool. Without l1_id: the download URL of the full file. With l1_id: that L1's subtree as CSV text, parents first. Profiles: csv (generic), servicenow (import set for Business Capability), leanix, ardoq, product-map.
profile · l1_id?
// FIG. 09 · JSON API
- /api/v1/version.json
- Version, build time, license and counts
- /api/v1/capabilities.json
- Every capability, flattened
- /api/v1/tree.json
- The capability tree, nested
- /api/v1/capability/{id}.json
- One capability with ancestors, children and crosswalk
- /api/v1/macros.json · industries.json
- The executive layer and the industry vocabulary
- /api/v1/value-streams.json · value-stream/{id}.json
- Value streams and their stages
- /api/v1/products.json · product/{id}.json
- Products and their product capabilities
- /api/v1/patterns.json · stacks.json · books.json
- The library
- /api/v1/search-docs.json
- Compact documents for client-side search
- /api/v1/changes.json
- Releases and what changed in each
- /api/v1/export/index.json · export/*.csv
- Generic, ServiceNow, LeanIX and Ardoq exports, plus the product map