The Forgeprint MCP server: it turns "I know C#, I want to build a multi-tenant SaaS API" into one blueprint and a setup recipe your agent can execute.

It returns text. It installs nothing, runs nothing on your machine, and keeps no state beyond a five-minute cache of the catalog index.

npx -y forgeprint-mcp

Claude Code:

claude mcp add forgeprint -- npx -y forgeprint-mcp

On Windows PowerShell, quote the separator: claude mcp add forgeprint "--" npx -y forgeprint-mcp.

Any client that takes an mcpServers object:

{
  "mcpServers": {
    "forgeprint": { "command": "npx", "args": ["-y", "forgeprint-mcp"] }
  }
}

Tools

Tool	What it does
`resolve`	Start here. Returns either the questions to ask the user or exactly one blueprint with its rationale
`get_blueprint`	Manifest and files for a slug, with the chosen option branches resolved out of `setup.md`
`search_blueprints`	Scored matches with reasons
`compare_blueprints`	Two to four blueprints side by side, including what each is explicitly not for
`validate_blueprint`	Schema, taxonomy, setup and duplication checks on a draft
`request_blueprint`	A GitHub issue payload when nothing fits. It does not file it

resolve asks before it guesses, asks in rounds, and only asks questions whose answers would change which blueprint wins. It never returns a list to browse, and never invents a match.

Configuration

Variable	Default	What it does
`FORGEPRINT_CATALOG`	unset	Path to a checkout. Set it and the server reads the catalog from disk, with no network at all
`FORGEPRINT_INDEX_URL`	the published index	Where the catalog index is fetched from
`FORGEPRINT_FILES_URL`	the raw repository	Where blueprint files are fetched from

Full documentation: docs/mcp.md.