Resolve a developer profile to exactly one project blueprint and return its CI-tested setup recipe.
Quick Install
Automated & IDE SetupCopy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.
One-click editor setup isn’t available for this listing yet — we don’t have a confirmed install command, and we’d rather show nothing than point your editor at the wrong package or host. Follow the project’s own setup instructions, linked above.
Manual Client & Custom JSON ConfigExpand JSON ▾
No confirmed setup config for this listing yet. We only publish a config block when the install details come from the project itself — its README, its docs, or a verified owner. We haven’t found those for Forgeprint, and we’d rather show nothing than a guess you’d paste into your client. Follow the project’s own setup instructions for the current steps.
Documentation Overview
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:
On Windows PowerShell, quote the separator:
claude mcp add forgeprint "--" npx -y forgeprint-mcp.Any MCP client can connect; the site has the command or configuration for each of the nine registered agents, and the catalog with its current counts. 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.
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.
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:
Both are verified against the real tools before each release, and
forgeprint validate fails on a skill that would not install — see
ADR 0006.
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 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.
What works today
To work on the catalog itself:
| 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 <slug> | Check a setup recipe: numbering, verification, pinning, safety |
pnpm forgeprint similarity <slug> | 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.
Layout
Roadmap
Related MCP Servers
Reviews
No reviews yet — be the first to share how this listing worked for you.
Frequently Asked Questions about Forgeprint
AllMCPs Directory Badge
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
Badge Style:
Live Dynamic SVG Preview
Markdown (GitHub README)
[](https://allmcps.com/mcp/forgeprint)HTML Embed
<a href="https://allmcps.com/mcp/forgeprint"><img src="https://allmcps.com/api/badge/forgeprint?style=directory" alt="Forgeprint on AllMCPs" /></a>