# Forgeprint
**Category:** 💻 Developer Tools
**Repository:** https://github.com/forgeprint/forgeprint
**Views:** 0
**Installs:** 0
**Upvotes:** 0
**Directory Page:** https://allmcps.com/mcp/forgeprint
## Description
Resolve a developer profile to exactly one project blueprint and return its CI-tested setup recipe.
## Claude Desktop Quick Installation
Heuristic fallback — verify the package name and runner against the repository README before running it. Uses `npx` (confidence: low):
```json
"mcpServers": {
"forgeprint": {
"command": "npx",
"args": ["-y","forgeprint"]
}
}
```
## Documentation & README
# Forgeprint
**Others say "here are 200 skills, go find yours." Forgeprint says "tell me who
you are and what you're building — here is your package."**
Forgeprint is a community-grown blueprint catalog and MCP server that lets a
coding agent bootstrap a new project with the right context in one shot: the
`AGENTS.md`, the skills, the MCP and plugin configuration, and a deterministic
setup recipe the agent can execute.
> **Status: pre-release.** A catalog of blueprints, experts, crews and
> integrations, working tooling, and an MCP server with all ten tools, published
> and connectable today. With Claude Code:
>
> ```bash
> claude mcp add forgeprint -- npx -y forgeprint-mcp
> ```
>
> On Windows PowerShell, quote the separator:
> `claude mcp add forgeprint "--" npx -y forgeprint-mcp`.
>
> Any MCP client can connect; [the site](https://forgeprint.github.io/forgeprint)
> has the command or configuration for each of the nine registered agents, and
> the catalog with its current counts. [Roadmap](#roadmap) has the rest.
---
## The problem
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.
---
## What makes it different
### 1. A resolver, not a catalog to browse
You do not search Forgeprint. You describe yourself and your goal, and it
returns **exactly one** blueprint.
```
You: I know C#. I want to build a multi-tenant SaaS API.
Agent: [resolve] → Forgeprint returns questions: which database, which auth,
self-hosted or cloud?
You: Postgres, JWT, cloud.
Agent: [resolve] → one blueprint, why it was chosen, what is missing on this
machine, and the setup plan.
```
When the profile is incomplete, the resolver does not guess: it returns the
questions your agent should ask you. When two candidates are genuinely close,
it returns both as a question and lets you pick — never as a list to sift
through. When nothing fits, it says so, names the closest blueprint, explains
why it does not fit, and offers to file a request. It never invents a match.
Scoring is weighted: a language you already know beats everything else.
### 2. A setup recipe, not a description
`setup.md` is a script, not prose. Every step is numbered, is a single command
or a single file operation, and ends with a verification command. Versions are
pinned. Option branches are explicit. The agent executes it; Forgeprint itself
installs nothing and runs nothing on your machine.
### 3. A quality gate, not a junk drawer
Every pull request passes schema validation, a setup test that actually runs
the recipe in a clean container, and a duplicate report against the closest
existing blueprint. Two blueprints may not claim the same stack, project type
and requirements — a better one **replaces** the old one instead of sitting
next to it.
There is no inheritance and there are no variants. Variation is expressed as
`options`, capped at three fields with three values each, so the whole matrix
stays testable. See [ADR 0001](https://github.com/forgeprint/forgeprint/blob/HEAD/docs/decisions/0001-no-variants.md).
### 4. Standards-compatible, not another format
Forgeprint follows the existing specs — `AGENTS.md`, `SKILL.md`,
`marketplace.json` — so its output drops into the tools you already use, and
skills remain installable through the usual channels:
```bash
npx skills add forgeprint/forgeprint # skills.sh CLI
gh skill install forgeprint/forgeprint blueprint-author
```
Both are verified against the real tools before each release, and
`forgeprint validate` fails on a skill that would not install — see
[ADR 0006](https://github.com/forgeprint/forgeprint/blob/HEAD/docs/decisions/0006-skill-distribution.md).
---
## How it compares
Forgeprint is not trying to replace most of these. It sits in the gap between
them.
| Project | What it does | How Forgeprint differs |
| -------------------------------- | --------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- |
| `microsoft/skills` | 170+ Azure/Foundry skills, an AGENTS.md template, ready MCP configs | A catalog you browse; no matching, and Azure-shaped |
| `github/awesome-copilot` | Community instructions, prompts and skills for Copilot | A rule collection; no setup recipe, no resolver |
| `github/spec-kit` | Spec-driven development: spec → plan → tasks | A process tool. Forgeprint delivers the context package and the recipe — complementary, not competing |
| `agent-rules-mcp` | An MCP that fetches rule files from any GitHub repo | Fetches files; no selection, no schema, no setup, no quality gate |
| `codeops-mcp` | Universal coding rules, generates project.md from an existing project | The opposite direction: it analyses projects that exist. Forgeprint bootstraps ones that do not |
| `awesome-cursorrules` | A Cursor `.mdc` rule collection | One tool, one file type; no setup, no MCP |
| `skills.sh`, `gh skills install` | Skill distribution standard and CLI | Distribution infrastructure that Forgeprint builds **on top of**, not a competitor |
---
## How it works
You point your agent at the MCP server and talk normally.
[docs/mcp.md](https://github.com/forgeprint/forgeprint/blob/HEAD/docs/mcp.md) has the connection details and a worked exchange.
| Tool | What you get |
| -------------------- | -------------------------------------------------------------------------------------------------- |
| `resolve` | Either the questions to ask you, or one blueprint with its rationale, missing tools and setup plan |
| `search_blueprints` | Matching blueprints with scores, when you want to look yourself |
| `get_blueprint` | The manifest and every file, with option branches already resolved |
| `compare_blueprints` | A pros-and-cons table for 2–4 candidates, built from their `overview.md` files |
| `validate_blueprint` | Schema errors and a similarity report, for contributors |
| `request_blueprint` | A GitHub issue payload when nothing matches |
Forgeprint replies in English. Your agent presents it in your language: the
tools take a `locale` hint and hand it back, so nothing in the catalog has to
be translated. See [ADR 0004](https://github.com/forgeprint/forgeprint/blob/HEAD/docs/decisions/0004-english-only-catalog.md).
---
## What works today
```bash
npx forgeprint validate # in a checkout of any Forgeprint catalog
npx -y forgeprint-mcp # the MCP server, over stdio
```
To work on the catalog itself:
```bash
git clone https://github.com/forgeprint/forgeprint.git
cd forgeprint
pnpm install
pnpm run build
pnpm forgeprint validate
```
| Command | What it does |
| ----------------------------------- | -------------------------------------------------------------- |
| `pnpm forgeprint validate` | Schema, taxonomy, required files, and the catalog-wide rules |
| `pnpm forgeprint build-index` | Regenerate `docs/index.json` |
| `pnpm forgeprint build-schema` | Regenerate `schema/manifest.schema.json` |
| `pnpm forgeprint build-codeowners` | Regenerate `.github/CODEOWNERS` from the manifests |
| `pnpm forgeprint lint-setup ` | Check a setup recipe: numbering, verification, pinning, safety |
| `pnpm forgeprint similarity ` | Duplicate report against every other blueprint |
**Every pipeline step is a command you can run locally.** Hosted CI is a
convenience, never a dependency: the workflows call these same commands, the
generated index is committed to the repository, and GitHub Pages serves it
straight from the branch. When Actions is unavailable, nothing stops.
See [ADR 0002](https://github.com/forgeprint/forgeprint/blob/HEAD/docs/decisions/0002-actions-optional.md).
---
## Layout
```
blueprints// one folder per blueprint — the unit of contribution
skills/ blueprint-author and blueprint-review
schema/ manifest schema and the controlled taxonomy
packages/cli/ forgeprint validate / build-* / similarity / lint-setup
packages/mcp-server/ the MCP server (npx forgeprint-mcp)
packages/site/ the static GitHub Pages site, generated into docs/
docs/ index.json, the ADRs, and the published site
```
---
## Roadmap
- [x] **Phase 0 — Skeleton.** Workspace, schema, taxonomy, validation and
generators, licensing, contribution and governance rules.
- [x] **Phase 1 — First content.** Three `official` blueprints, the
`blueprint-author` and `blueprint-review` skills, the similarity report
and the setup lint.
- [x] **Phase 2 — MCP.** The six tools, the option resolver, and the server
over stdio, published as `forgeprint-mcp`.
- [x] **Phase 3 — Publishing.** The site is generated from the catalog and
served at , and the workflows
run: `validate` on every push and pull request, `setup-test` on the
recipes. `forgeprint validate` checks the skill format the distribution
tools read, so `npx skills add` and `gh skills install` agree with it
([ADR 0006](https://github.com/forgeprint/forgeprint/blob/HEAD/docs/decisions/0006-skill-distribution.md)).
- [ ] **Phase 4 — Community.** Contributor visibility has shipped: every
blueprint page names and links its maintainer, and the open blueprint
requests are listed live. What is left waits on people rather than on
work — the orphan, staleness and co-maintainer rules are written in
[GOVERNANCE.md](https://github.com/forgeprint/forgeprint/blob/HEAD/GOVERNANCE.md) and will be automated when there is a
second maintainer to automate them for, and community translations open
when somebody wants to write one.
A "times resolved" counter is **not** planned. It would mean the server
learning something about the people who use it, and
[PRIVACY.md](https://github.com/forgeprint/forgeprint/blob/HEAD/PRIVACY.md) says it collects nothing. If it is ever
revisited it will be anonymous and opt-in, and that file says so.
---
## Contributing
Read [CONTRIBUTING.md](https://github.com/forgeprint/forgeprint/blob/HEAD/CONTRIBUTING.md) first — especially the part about
checking whether the blueprint you want to write already exists. The fastest
merge is usually a pull request against a blueprint that is already there.
Two skills carry the procedure, for you or for your agent:
[`blueprint-author`](https://github.com/forgeprint/forgeprint/blob/HEAD/skills/blueprint-author/SKILL.md) turns a working project
into a blueprint that passes the gate, and
[`blueprint-review`](https://github.com/forgeprint/forgeprint/blob/HEAD/skills/blueprint-review/SKILL.md) is the standard it is
judged against. Install either one into your agent:
```bash
gh skill install forgeprint/forgeprint blueprint-author
npx skills add forgeprint/forgeprint --skill blueprint-author
```
Or add the marketplace, and take them as Claude Code plugins:
```
/plugin marketplace add forgeprint/forgeprint
```
Want a blueprint you cannot write yourself? File a
[blueprint request](https://github.com/forgeprint/forgeprint/issues/new?template=blueprint-request.yml).
The catalog grows by demand.
Who decides what, who reviews, and what happens when nobody answers:
[GOVERNANCE.md](https://github.com/forgeprint/forgeprint/blob/HEAD/GOVERNANCE.md).
---
## Licence
**Forgeprint is source-available, not OSI open source.** Saying otherwise would
be easier and less honest.
| What | Licence |
| ----------------------------------------- | ----------------------------------------------------------------------------------------------------- |
| `packages/**` — MCP server, CLI, site | [PolyForm Shield 1.0.0](https://github.com/forgeprint/forgeprint/blob/HEAD/LICENSE) — use, modify and contribute freely; do not ship a competing product |
| `blueprints/**`, `schema/**`, `skills/**` | [CC BY 4.0](https://github.com/forgeprint/forgeprint/blob/HEAD/blueprints/LICENSE) — copy them into your own projects, commercial or not |
| The name and logo | [TRADEMARK.md](https://github.com/forgeprint/forgeprint/blob/HEAD/TRADEMARK.md) — a published fork must rename |
| Contributions | [DCO](https://github.com/forgeprint/forgeprint/blob/HEAD/DCO) sign-off (`git commit -s`), no CLA |
Blueprint content is deliberately the freest part: a blueprint you cannot put
in your own project is worthless. The reasoning is in
[ADR 0003](https://github.com/forgeprint/forgeprint/blob/HEAD/docs/decisions/0003-licensing.md).