mcp-forge
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-forgelist steps for an http-api project"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-forge
An MCP stdio server that serves the mcp-forge prompt library — a deterministic, enterprise-grade system for rewriting any Node.js project to production-quality TypeScript.
Connect this server to any MCP client and call its tools to retrieve the exact prompts needed to rewrite a project step by step. The same source code always produces the same output — deterministic by design.
Supported project types: http-api · library · cli · worker · mcp-server
Tools
Tool | Description |
| List all 15 rewrite steps. Pass |
| Get the full prompt for a specific step (0–14). Step 8 requires |
| Get the Step 8 entrypoint prompt for a given project type. |
| Get the single-pass master prompt for small projects (< 2 000 lines). |
| Validate an |
Setup
git clone https://github.com/Flagler-County-BoCC/mcp-forge
cd mcp-forge
npm install
npm run setupnpm run setup builds the project and automatically registers it in Claude Desktop's config file. It detects your OS, finds the right config path, and merges the entry without touching any other servers you have configured.
Restart Claude Desktop after running setup.
Manual setup (Cursor or other MCP clients)
Add this to your client's MCP config:
{
"mcpServers": {
"mcp-forge": {
"command": "node",
"args": ["/absolute/path/to/repo/dist/stdio.js"]
}
}
}Build first if you haven't already: npm run build
PROMPTS_DIRdefaults to.claude/commandsinside the repo — no environment variable needed.
How to use it
Incremental rewrite (large projects, recommended):
get_step({ step: 0 })→ run the audit prompt, receive anAUDIT_MANIFESTJSONvalidate_manifest({ manifestJson: "..." })→ confirm it's validlist_steps({ projectType: "mcp-server" })→ see which steps applyget_step({ step: 1 })→get_step({ step: 7 })→ scaffold in orderget_entrypoint({ projectType: "mcp-server" })→ entrypoint layer (Step 8)get_step({ step: 9 })→get_step({ step: 14 })→ testing, security, CI, docs
Single-pass rewrite (small projects, < 2 000 lines):
get_master_prompt()→ paste your entire project source into context with the returned prompt
Environment variables
Variable | Default | Description |
|
| Override the prompts directory location |
|
| Environment |
|
| pino log level |
Development
npm run dev # tsx watch mode
npm test # run all tests (25 unit + integration)
npm run typecheck # TypeScript check
npm run lint # ESLint
npm run build # compile to dist/Prompt library layout
.claude/commands/
shared/ Steps 00–07, 09–14 (all project types, conditional sections)
entrypoints/ Step 08 — one file per project type
masters/ MASTER.md — universal single-pass promptLicense
MIT
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Flagler-County-BoCC/mcp-forge'
If you have feedback or need assistance with the MCP directory API, please join our Discord server