Forgeprint

Blueprint catalog + MCP server

Tell an agent who you are. Get the whole project package.

Others hand you two hundred skills and wish you luck. Forgeprint asks what you know and what you are building, then returns exactly one blueprint — the rule file, the skills, the MCP configuration, and a setup recipe your agent runs step by step.

Pre-release · 7 blueprints · 3 languages

Connect it to your agent

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

One command. It adds the MCP server to Claude Code.

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

Browse the catalog

Every new project starts cold

You hunt down the requirements, write the rule file by hand, wire up the MCP servers, pick the plugins, and get the setup steps wrong twice before they work. Hours of it — repeated by everyone, on every project, forever.

That knowledge is not hard to write down. It is just never written down in a form another agent can use.

Without Forgeprint

  • Search for a starting point, find five, compare them by hand
  • Write AGENTS.md from memory, forget half of it
  • Wire MCP servers one at a time, from their own READMEs
  • Run setup steps that were right six months ago
  • Discover the gaps only when something fails

With Forgeprint

  • Describe yourself in one sentence; the resolver asks what it still needs
  • Get one blueprint, with the reason it was chosen
  • The rule file, the skills and the MCP configuration arrive together
  • Every setup step is pinned and ends with the command that proves it worked
  • The recipe is executed in CI before it ever reaches you

How it works

You talk to your agent normally. Forgeprint answers in structured data, and your agent does the work. It installs nothing and runs nothing on your machine — every tool returns text.

  1. You describe yourself

    “I know C#, I am building a multi-tenant SaaS API.” No form to fill in, no catalogue to read.

  2. The resolver asks what is missing

    An incomplete profile does not get a guess. It gets the questions your agent should ask you.

  3. One blueprint comes back

    Never a list. With the reason it was chosen, what is missing on your machine, and the setup plan.

  4. Your agent executes the recipe

    Numbered steps, pinned versions, and a verification command after each one.

What moves between the pieces

Forgeprint returns text. It never runs anything on your machine.

What makes it different

A resolver, not a list

It returns one blueprint, weighted so a language you already know beats everything else.

A recipe, not a description

setup.md is a script. Versions pinned, each step ending in the check that proves it worked.

A gate, not a junk drawer

Schema validation, a real setup run, and a duplicate report on every pull request.

Standards, not another format

AGENTS.md, SKILL.md and marketplace.json as they already exist.

The templates

Every blueprint in the catalog right now. Each one has been reviewed against named security and architecture standards, and its setup recipe is executed in CI on every push — in every option combination.

Full catalog with search Blueprint summaries stay in English. The catalog is written once, in one language, and your agent presents it in yours.

Who it is for

People who use it

Anyone starting a project with an agent

You do not need to know what an MCP server is.

Teams who keep rewriting the same setup

A blueprint is that decision, written down once.

People learning a stack

The recipe shows the decisions, not just the commands.

People who build it

Anyone with a project that works

The most valuable blueprint comes from something real.

Reviewers and maintainers

Every blueprint has a maintainer, listed on its page.

People who just want one to exist

File a request. The catalog grows by demand.

How to use it

Two minutes, and nothing to install beyond the agent you already have.

  1. Connect the MCP server

    One command. npx fetches it; nothing is installed permanently.

  2. Tell your agent what you are building

    In your own words.

  3. Answer the questions it comes back with

    The resolver asks rather than guesses.

  4. Let it run the recipe

    Your agent executes the steps and checks each one.

What the exchange looks like

YouI know C#. I want to build a multi-tenant SaaS API.

AgentForgeprint needs three things: which database, which auth, and is tenancy one schema or one database per tenant?

YouPostgres, JWT, shared schema.

Agentdotnet-multitenant-saas-api. Chosen because you already write C#. 34 steps — shall I start?

Or take the pieces directly

The skills install through the tools you already use, with no MCP server involved. 

npx skills add forgeprint/forgeprint
gh skill install forgeprint/forgeprint blueprint-author

How to contribute

One folder is one blueprint, and that folder is the unit of contribution. Everything the pipeline does is a command you can run on your own machine — hosted CI is a convenience here, never a dependency.

Get it running

git clone https://github.com/forgeprint/forgeprint.git
cd forgeprint
pnpm install
pnpm run build
pnpm forgeprint validate

How the repository is laid out

blueprints/<slug>/
One folder per blueprint

The contribution flow

  1. Check whether it already exists

    The fastest merge is usually a pull request against a blueprint that is already there.

  2. Write it from something that works

    The blueprint-author skill turns a working project into a blueprint.

  3. Pass the gate locally

    validate, lint-setup, similarity and a real setup run.

  4. Open the pull request

    Say which blueprint is closest and why yours is not a change to it.

Questions people actually ask

Does Forgeprint run anything on my machine?

No. Every tool returns text.