Bietet einen berechtigungskontrollierten lokalen Agenten für Filesystem-Edits, Terminal-Zugriff, Git-Workflows und semantisches Browser-Testing von AI-Clients aus.
Auch bekannt als t1ktakdev/ForgeBridge
- Stars
- 1
- Tools
- —
- Downloads, 30 Tage
- —
- Neueste Version
- 0.1.0-alpha.4
- Letzter Commit
- 21. Sept. 2026
- Lizenz
- Apache-2.0
Was ist ForgeBridge MCP?
Bietet einen berechtigungskontrollierten lokalen Agenten für Filesystem-Edits, Terminal-Zugriff, Git-Workflows und semantisches Browser-Testing von AI-Clients aus.
Zusammenfassung generiert aus dem README des Projekts
Über ForgeBridge MCP server
ForgeBridge fungiert als berechtigungskontrollierter lokaler Agent für Entwickler, die AI-Clients kontrollierten Zugriff auf ihre Workstation gewähren möchten. Es erleichtert Filesystem-Edits, Terminal-Interaktionen, Git-Workflows und semantisches Browser-Testing. Der Server läuft lokal und kann über stdio oder über einen ausgehenden HTTPS-Pfad mittels OpenAI Secure MCP Tunnel mit AI-Clients verbunden werden, um webbasierte Interfaces wie ChatGPT zu nutzen.
Nutzer verwalten den Agenten über ein lokales Control Center, um Berechtigungen zu prüfen, aktive Jobs zu überwachen und Audit Trails zu inspizieren. Das System nutzt eine Deny-First-Permission-Engine, um sicherzustellen, dass alle Aktionen innerhalb der autorisierten canonical Roots bleiben. Entwickler können das project_inspect Tool nutzen, um schnell Informationen über den Project Stack, das Host-Betriebssystem und den Git-Status zu erhalten. Während es ein hohes Maß an Automatisierung bietet, wird die Sicherheit durch erforderliche Approvals für Write-Operationen und standardmäßig isolierte Browser-Sessions aufrechterhalten.
Was du damit machen kannst
- 1Automatisierte Discovery der ProjektumgebungEin AI-Client kann mit einem einzigen Befehl den aktuellen Project Stack, die Shell und den Git-Status identifizieren.
- 2Kontrolliertes Filesystem- und Git-ManagementEntwickler können einer AI erlauben, Routine-Coding-Aufgaben und Git-Operationen innerhalb spezifischer Projektgrenzen auszuführen.
- 3Überwachte Terminal-AusführungNutzer können interaktive Terminal-Sessions und langlaufende Jobs über eine dedizierte Interface überwachen und freigeben.
Geschrieben aus dem README des Projekts. Jeder Use Case wurde gegen ein Zitat daraus geprüft.
So installierst du ForgeBridge MCP
Formate geprüft am 10. Nov. 2026Zu Cursor hinzufügenZu Goose hinzufügenForgeBridge MCP in Claude Code installieren
$ claude mcp add forgebridge -- npx -y forgebridgeForgeBridge MCP in Cursor installieren
~/.cursor/mcp.json
{
"mcpServers": {
"forgebridge": {
"command": "npx",
"args": [
"-y",
"forgebridge"
]
}
}
}ForgeBridge MCP in VS Code installieren
.vscode/mcp.json
{
"servers": {
"forgebridge": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"forgebridge"
]
}
}
}ForgeBridge MCP in VS Code CLI installieren
$ code --add-mcp '{"name":"forgebridge","type":"stdio","command":"npx","args":["-y","forgebridge"]}'ForgeBridge MCP in Claude Desktop installieren
claude_desktop_config.json
{
"mcpServers": {
"forgebridge": {
"command": "npx",
"args": [
"-y",
"forgebridge"
]
}
}
}ForgeBridge MCP in Codex installieren
$ codex mcp add forgebridge -- npx -y forgebridgeForgeBridge MCP in Codex config.toml installieren
~/.codex/config.toml
[mcp_servers.forgebridge] command = "npx" args = ["-y", "forgebridge"]
ForgeBridge MCP in Gemini CLI installieren
$ gemini mcp add -s user forgebridge npx -- -y forgebridgeForgeBridge MCP in Gemini settings.json installieren
~/.gemini/settings.json
{
"mcpServers": {
"forgebridge": {
"command": "npx",
"args": [
"-y",
"forgebridge"
]
}
}
}Automatisierte Checks
Geluften am 15. Nov. 2026Vollständiger Bericht →Unsere automatisierten Checks bestanden. Das ist kein Security-Audit: Lies den Code und gib dem Server nur den minimal notwendigen Zugriff. Wie die Checks funktionieren
- Source Repository verknüpft und erreichbart1ktakdev/forgebridge is public and reachablegithub.com/t1ktakdev/forgebridge ↗Bestanden
- Paket nennt dieses Repository als Quelleforgebridge names t1ktakdev/forgebridge as sourcenpmjs.com/package/forgebridge ↗Bestanden
- Build-Provenienz (Sigstore-Attestierung)No build attestation published for this releaseNicht geprüft
- Open Source Lizenz (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗Bestanden
- Commit oder Release im letzten JahrLast commit or release 2026-09-21github.com/t1ktakdev/forgebridge ↗Bestanden
- OpenSSF ScorecardNicht geprüft
- Package-Name ähnelt keinem populären PackageNo popular package one edit away from forgebridgeBestanden
- Keine kritischen Advisories im Paket oder seinen Abhängigkeiten106 resolved dependencies checked; no critical advisoryosv.dev ↗Bestanden
- Keine versteckten Anweisungen an das Modell0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersBestanden
- Destruktive Tools sind markiertNicht geprüft
- Remote-Endpoint beantwortet den MCP-HandshakeNicht geprüft
README
Auf GitHub ansehenForgeBridge
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 Fragen
Wie füge ich ForgeBridge MCP zu Claude Code hinzu?
Führe claude mcp add forgebridge -- npx -y forgebridge in deinem Terminal aus. Füge --scope user hinzu, damit der Server in jedem Projekt verfügbar ist.
Wie füge ich ForgeBridge MCP zu Cursor hinzu?
Öffne ~/.cursor/mcp.json und füge den Server unter mcpServers hinzu, mit der Cursor-Config aus dem Installationsabschnitt oben.
Was kann ForgeBridge für meinen Development-Workflow tun?
Es ermöglicht Filesystem-Edits, interaktiven Terminal-Zugriff, Git-Workflows und semantisches Browser-Testing über kompatible AI-Clients.
Wie regelt ForgeBridge Sicherheit und Berechtigungen?
Es nutzt eine Deny-First-Permission-Engine, bei der jede Aktion geprüft wird, Pfade auf erlaubte Roots beschränkt sind und Write-Approvals zeitlich begrenzt sind.
Gibt es eine Möglichkeit zu überwachen, was der Agent tut?
Ja, es gibt ein lokales Control Center, um Berechtigungen zu prüfen, Jobs und Sessions zu verfolgen und den Audit Trail zu inspizieren.