Forgeprint

Name: Forgeprint
Author: forgeprint

作者：forgeprint版本 0.4.5i★ –i在你的电脑上运行

注册名称io.github.forgeprint/forgeprint

安装

概览

作者提供的说明（英文原文）

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

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 其他

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
注册中心没有列出需要填写的密钥。

你需要

npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

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

在终端中运行这条命令

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

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

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

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

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

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 forgeprint 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“其他”中的其他服务器比较i

星标数多于此分类中其他 32568 个服务器的 0%
发布到注册中心的时间比此分类中其他 32568 个服务器的 56% 更新
基础检查结果等于或优于此分类中其他 32568 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Forgeprint 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.4.5）于32天前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, FlyDocs

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者：formulahendry

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

在你的电脑上运行★ 440MIT14个月前更新

安装

Remote Desktop Commander

作者：desktop-commander

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

在云端运行★ 211昨天更新

安装

FlyDocs

作者：flydocs.ai

Spec-driven development workflow: your agent works issues, sessions and the status lifecycle.

在你的电脑上运行今天更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

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

只显示了开头部分；其余内容请在仓库中阅读

Forgeprint

概览

PopNx MCP 的三大支柱

它能帮你做什么

安装

安装之前

它能做什么

基础检查i

作者与仓库一致

仍在维护

有许可证

端点有响应

使用 OAuth 登录

工具描述中没有隐藏指令

与“其他”中的其他服务器比较i

常见问题

替代选择

Spec Driven Development

Remote Desktop Commander

FlyDocs

作者的 README

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