Forgeprint

Name: Forgeprint
Author: forgeprint

by forgeprintversion 0.4.5i★ –iRuns on your computer

Registry nameio.github.forgeprint/forgeprint

Install

Overview

Description from the maker (original English)

Resolve a developer profile to exactly one project blueprint and return its CI-tested setup recipe.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

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

Run this in your terminal

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

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "forgeprint": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "forgeprint-mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account forgeprint, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32410 servers in this category
Published to the registry more recently than 56% of the other 32410 servers in this category
Basic checks equal to or better than 100% of the other 32410 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Forgeprint safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.4.5) reached the registry 31 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, debuff

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

debuff

by debuffjp

Let coding agents play, test and tune your 2D web game: live state, explained errors, replays, fuzz.

Runs on your computerUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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

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.

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.

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:

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.

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
`recommend_experts`	For a task, at most one crew or at most three experts, each with a reason — never a list to browse
`get_expert`	One expert: its `SKILL.md`, checklists and sourced references
`get_crew`	One crew: its members in full, and the install command for each integration it names
`get_integration`	One pinned install recipe for third-party software, with the secrets it needs and what they reach

Without an MCP client, nothing above is required:

npx -y forgeprint get ts-http-service --agent cursor --options framework=hono

That writes the files that agent reads, and the recipe with your options resolved — the same answer the tools give, because it is the same code (ADR 0013). It reads the published catalog, or a checkout when you are in one. The catalog is also published as JSON at forgeprint.github.io/forgeprint/index.json and as llms.txt.

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

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:

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.

Layout

blueprints/<slug>/     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

Phase 0 — Skeleton. Workspace, schema, taxonomy, validation and generators, licensing, contribution and governance rules.
Phase 1 — First content. Three official blueprints, the blueprint-author and blueprint-review skills, the similarity report and the setup lint.
Phase 2 — MCP. The six tools, the option resolver, and the server over stdio, published as forgeprint-mcp.
Phase 3 — Publishing. The site is generated from the catalog and served at https://forgeprint.github.io/forgeprint, 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).
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 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 serve

Only the beginning is shown; read the rest in the repo

Forgeprint

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

debuff

README from the maker

Forgeprint

The problem

What makes it different

1. A resolver, not a catalog to browse

2. A setup recipe, not a description

3. A quality gate, not a junk drawer

4. Standards-compatible, not another format

How it compares

How it works

What works today

Layout

Roadmap