Provides a permissioned local agent for filesystem editing, terminal access, Git workflows, and semantic browser testing from AI clients.
Also known as t1ktakdev/ForgeBridge
- Stars
- 1
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 0.1.0-alpha.4
- Last commit
- Sep 21, 2026
- License
- Apache-2.0
What is ForgeBridge MCP?
ForgeBridge provides a permissioned local agent for filesystem editing, terminal access, Git workflows, and semantic browser testing from AI clients.
Summary generated from the project's README
About ForgeBridge MCP server
ForgeBridge acts as a permissioned local agent designed for developers who want to grant AI clients controlled access to their workstation. It facilitates filesystem editing, terminal interaction, Git workflows, and semantic browser testing. The server operates locally and can be connected to AI clients via stdio or through an outbound HTTPS path using the OpenAI Secure MCP Tunnel for web-based interfaces like ChatGPT.
Users manage the agent through a local Control Center to review permissions, monitor active jobs, and inspect audit trails. The system uses a deny-first permission engine to ensure all actions remain within authorized canonical roots. Developers can use the project_inspect tool to quickly learn about the project stack, host operating system, and Git state. While it provides high levels of automation, it maintains security by requiring approvals for write operations and keeping browser sessions isolated by default.
What you can do with it
- 1Automated project environment discoveryAn AI client can use a single command to identify the current project stack, shell, and Git status.
- 2Controlled filesystem and Git managementDevelopers can allow an AI to perform routine coding tasks and Git operations within specific project boundaries.
- 3Supervised terminal executionUsers can monitor and approve interactive terminal sessions and long-running jobs through a dedicated interface.
Written from the project's README. Every use case is checked against a quote from it.
How to install ForgeBridge MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall ForgeBridge MCP in Claude Code
$ claude mcp add forgebridge -- npx -y forgebridgeInstall ForgeBridge MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"forgebridge": {
"command": "npx",
"args": [
"-y",
"forgebridge"
]
}
}
}Install ForgeBridge MCP in VS Code
.vscode/mcp.json
{
"servers": {
"forgebridge": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"forgebridge"
]
}
}
}Install ForgeBridge MCP in VS Code CLI
$ code --add-mcp '{"name":"forgebridge","type":"stdio","command":"npx","args":["-y","forgebridge"]}'Install ForgeBridge MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"forgebridge": {
"command": "npx",
"args": [
"-y",
"forgebridge"
]
}
}
}Install ForgeBridge MCP in Codex
$ codex mcp add forgebridge -- npx -y forgebridgeInstall ForgeBridge MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.forgebridge] command = "npx" args = ["-y", "forgebridge"]
Install ForgeBridge MCP in Gemini CLI
$ gemini mcp add -s user forgebridge npx -- -y forgebridgeInstall ForgeBridge MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"forgebridge": {
"command": "npx",
"args": [
"-y",
"forgebridge"
]
}
}
}Automated checks
Ran Nov 15, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablet1ktakdev/forgebridge is public and reachablegithub.com/t1ktakdev/forgebridge ↗Pass
- Package names this repository as its sourceforgebridge names t1ktakdev/forgebridge as sourcenpmjs.com/package/forgebridge ↗Pass
- Build provenance (Sigstore attestation)No build attestation published for this releaseNot checked
- Open source license (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-09-21github.com/t1ktakdev/forgebridge ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from forgebridgePass
- No critical advisory in the package or its dependencies106 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubForgeBridge
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.
Control Center
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.
Project status
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.
Quick start
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.
Design
ForgeBridge keeps privileged enforcement on the workstation:
- every action is checked by a deny-first permission engine;
- paths are restricted to canonical allowed roots;
- write approvals are bound to the exact action and expire;
- terminal and job output is bounded and paginated;
- browser sessions are isolated by default;
- the default BACKGROUND execution profile forces headless browsers and defers focus-changing desktop actions;
- attempted and completed actions are written to a redacted, hash-chained audit log.
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:
- Model-first development workflow
- Research
- Architecture
- Security model
- Security validation matrix
- Windows validation record
- 2026-09-15 model-UX hardening validation
- Release-readiness audit
- Permission model
- Threat model
- Secure tunnel runbook
- Windows autostart
- Background execution and focus protection
- Implementation plan
Development
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
Trusted local development
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.
Local installation
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.
Security
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.
License
Apache License 2.0. See LICENSE.
ForgeBridge MCP questions
How do I add ForgeBridge MCP to Claude Code?
Run claude mcp add forgebridge -- npx -y forgebridge in your terminal. Add --scope user to make it available in every project.
How do I add ForgeBridge MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What can ForgeBridge do for my development workflow?
It enables filesystem editing, interactive terminal access, Git workflows, and semantic browser testing through compatible AI clients.
How does ForgeBridge handle security and permissions?
It uses a deny-first permission engine where every action is checked, paths are restricted to allowed roots, and write approvals are time-bound.
Is there a way to monitor what the agent is doing?
Yes, it includes a local Control Center to review permissions, follow jobs and sessions, and inspect the audit trail.