Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
A local, permissioned MCP agent for authorized developer workstations.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
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": {
"forgebridge": {
"command": "npx",
"args": [
"-y",
"forgebridge"
]
}
}
}Run this in your terminal
claude mcp add forgebridge -- npx -y forgebridgePaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"forgebridge": {
"command": "npx",
"args": [
"-y",
"forgebridge"
]
}
}
}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.
Paste into .vscode/mcp.json in your project
{
"servers": {
"forgebridge": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"forgebridge"
]
}
}
}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.
Runs on your computer; the tool list appears in your AI app after you install it.
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
The registry name was verified with the GitHub account t1ktakdev, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
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.
The registry does not list a required key, though some servers ask you to sign in on first use.
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).
The GitHub repo last changed –, and the latest version (0.1.0-alpha.4) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, debuff
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
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Let coding agents play, test and tune your 2D web game: live state, explained errors, replays, fuzz.
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.
Русская документация
Status: public alpha / beta testing. ForgeBridge is available for early real-world testing,
but it is not a stable production release yet. Commands, MCP schemas, configuration, and behavior
may change between alpha/beta versions. The project will continue to receive updates, fixes, UX
improvements, and new capabilities.
ForgeBridge is a local, permissioned MCP agent for development work on a computer the user owns and explicitly authorizes. It is designed for filesystem editing, interactive terminals, durable jobs, Git workflows, and semantic browser testing from compatible AI clients. For model-driven development, ForgeBridge exposes semantic project inspection, Git reads, and reviewed validation operations so routine work does not require arbitrary shell commands. Start with project_inspect to learn the project stack, Git state, host OS, and shell in one bounded call. See the model-first workflow.
This repository is under active development toward v0.1 and should be treated as test/beta software. Current status and verified limitations are tracked in the implementation plan. Issues and feedback are welcome; future releases will continue improving stability, onboarding, remote/multi-device UX, and tool coverage.
ForgeBridge includes a local Control Center for understanding what the agent is doing, reviewing permissions, following jobs and sessions, and inspecting the audit trail without digging through raw state files.
| Projects | Approvals |
|---|---|
The interface supports English and Russian, dark and light themes, responsive layouts, live jobs, sessions, approvals, project policies, and a redacted audit feed backed by the real local Control API.
Current public release: v0.1.0-alpha.4 · Channel: next · Estimated v1.0 readiness: ≈68%
The percentage is a weighted milestone estimate, not a quality score or release date. It is
updated as major product blocks move from experimental to release-ready.
| Area | Status |
|---|---|
| Local agent, permissions, audit, filesystem, Git, terminal, durable jobs, browser | ✅ Shipped |
| Control Center, RU/EN, themes, lifecycle actions, guided setup | ✅ Shipped |
| Cross-platform CI, npm package, MCP Registry, SBOM/checksums | ✅ Shipped |
| Update / repair / recovery | 🟡 In progress |
| Public API stability, migrations, deprecation policy | 🟡 In progress |
| Multi-device / remote routing | 🟠 Next major product block |
| Compatibility matrix + independent security pass | 🟠 Required before 1.0 |
Next milestone: 0.2.0-beta.1 — multi-device foundation, lifecycle/update UX, and the first compatibility freeze.
See the full Road to 1.0.
The public alpha package name is forgebridge; the installed command stays forgebridge. Once the first npm release is live:
npm install --global forgebridge@next
forgebridge init --root /path/to/your/project forgebridge doctor forgebridge browser install forgebridge serve --transport stdio
MCP clients that launch stdio servers can run ForgeBridge without a global install:
npx -y forgebridge@next serve --transport stdio
ForgeBridge is also prepared for discovery through the official MCP Registry as io.github.t1ktakdev/forgebridge. Browser automation needs a reviewed Chromium/Chrome/Edge installation; Windows UI Automation remains opt-in. See installation and packaging for platform-specific setup.
ForgeBridge keeps privileged enforcement on the workstation:
For ChatGPT web, the preferred v0.1 transport is OpenAI Secure MCP Tunnel, which creates an outbound HTTPS path without publishing a port on the workstation. Local MCP clients can use stdio directly.
See:
Requirements: Node.js 22 or newer, pnpm 11, Git, and Windows 10/11 for native validation.
pnpm install
pnpm check pnpm build node dist/cli.js init --root C:\src\my-project node dist/cli.js serve --transport stdio
For a repository you explicitly trust, ForgeBridge can remove repeat approval prompts for reviewed repository-defined validation while keeping the same canonical root boundary and hard-deny rules:
forgebridge project trust C:\src\my-project
This creates a per-project FULL profile with autonomy: trusted-local. It is intentionally local configuration: repository files cannot enable it. Reviewed project_check plans can then run without a fresh approval, while destructive commands, Git push, elevation, persistence, secret access, consequential browser/Windows submissions, and anything outside the configured root remain gated or denied. Revert with forgebridge project set PATH --mode balanced --autonomy standard or remove the project profile with forgebridge project remove PATH.
ForgeBridge is packaged as an npm-compatible tarball because node-pty is a native dependency and Playwright browser binaries are platform-specific. Nothing is published by the release scripts.
pnpm run package:artifact
pnpm run package:validate .\scripts\install-windows.ps1 -PackagePath .\release\forgebridge-0.1.0-alpha.4.tgz -InstallChromium
The artifact includes a CycloneDX SBOM and a SHA-256 checksum. Validation installs the actual tarball in a disposable prefix and exercises the installed CLI, MCP stdio, filesystem, terminal, and headless browser paths. See installation and upgrade instructions.
Optional Windows autostart is available after installation through configure-autostart-windows.ps1. It creates a current-user scheduled task only after explicit local configuration and stores the least-privilege tunnel runtime key with Windows DPAPI; the default installer still creates no startup entry.
Optional Windows UI Automation is disabled by default. Set windowsUiAutomation.enabled to true in the local config to expose bounded semantic Windows element trees and control-pattern actions. It requires an unlocked interactive desktop and never bypasses cross-user or elevation boundaries. Focus-changing actions are durably deferred in BACKGROUND and GAMING profiles and require local approval plus an explicit switch to NORMAL.
The agent never installs auto-start or a background service implicitly. Do not expose its local HTTP endpoint to a network interface.
Before any public alpha, complete the remaining external gates listed in the release-readiness audit, including a separate clean Windows VM run, artifact signing, and an independent security review. Live Secure MCP Tunnel/ChatGPT validation has already passed for the recorded Windows configuration.
ForgeBridge is powerful by design. An approved arbitrary shell has the authority of the OS account running the agent. For containment, use a dedicated low-privilege account, Windows Sandbox/VM, or another OS-enforced isolation boundary. Read SECURITY.md before using the agent on sensitive systems.
Apache License 2.0. See LICENSE.