Tell an agent who you are. Get the whole project package.
Every new project starts cold. You hunt down the requirements, write the rule file by hand, wire up the MCP servers, and get the setup steps wrong twice before they work — and everyone does it again on the next project.
Forgeprint is a curated blueprint catalog and an MCP server. You describe what
you know and what you are building; it returns exactly one blueprint: the
AGENTS.md, the skills, the MCP configuration, and a setup recipe your agent
executes step by step.
claude mcp add forgeprint -- npx -y forgeprint-mcpOn Windows PowerShell, quote the separator:
claude mcp add forgeprint "--" npx -y forgeprint-mcp
forgeprint.github.io/forgeprint · the catalog · the repository
| A resolver, not a list | You do not search it. One blueprint comes back, weighted so a language you already know beats everything else. When nothing fits it says so and names the closest |
| A recipe, not a description | Every step is one command or one file, versions pinned, each ending in the check that proves it worked. CI runs the whole thing in a clean container before anything merges |
| A gate, not a junk drawer | Schema validation, a real setup run and a duplicate report on every pull request. Two blueprints may not claim the same stack, project type and requirements |
| Standards, not a new format | AGENTS.md, SKILL.md and marketplace.json as they already exist, so the output drops into the tools you already use |
Blueprints written by a tool rather than a person say so — on their page, and
in what the MCP server returns. They can never be marked official, and the
schema refuses the combination rather than trusting a reviewer to notice.
The catalog grows by demand. If nothing fits what you are building, that is the most useful thing you can tell us:
- Request a blueprint
- Contributing guide — what a blueprint has to contain, and how it is judged
- Governance — who decides what, and what happens when nobody answers
The fastest merge is usually a pull request against a blueprint that already exists.
Source-available, not OSI open source — saying otherwise would be easier and less honest. The tooling is PolyForm Shield 1.0.0; blueprint content is CC BY 4.0, deliberately the freest part, because a blueprint you cannot put in your own project is worthless.
