JecBridge MCP

🇬🇧 English · 🇺🇿 O'zbekcha

Connects any code project on your computer to any AI over MCP: claude.ai, ChatGPT, Claude Desktop, Cursor, Claude Code, VS Code. The AI can read the project, change it, run its tests or build it from scratch. A checkpoint is taken automatically before every change, so if the AI makes a mistake you roll back with one command.

Quick start

The only requirement is Node.js 22+. Then one line:

npx jecbridge my-app --tunnel

That's it. The folder is created if it doesn't exist, the tunnel tool (cloudflared) is downloaded automatically the first time, and the connector URL is copied to your clipboard. Paste it into your AI:

• claude.ai: Settings → Connectors → Add custom connector

• ChatGPT: Settings → Apps & Connectors → Developer mode → Create

• Gemini: Settings → Connected Apps → Add a custom app

Then ask, for example: "Build a calculator with HTML and CSS in this project." or "Create a Vite + React site and start it." The AI starts the dev server itself and gives you the http://localhost:... link.

git is optional but recommended: with it, every change gets an automatic checkpoint and can be undone. Without git, everything else works.

Related MCP server: codebase-mcp

Install from source

git clone https://github.com/sanakulovme/jecbridge.git
cd jecbridge
npm install
npm link        # optional: makes the "jecbridge" command available everywhere

Windows

Install Node.js (and optionally git) once, from PowerShell:

winget install OpenJS.NodeJS.LTS
winget install Git.Git        # optional: enables checkpoints and undo

Close and reopen PowerShell, then:

npx jecbridge $HOME\Desktop\my-app --tunnel

Windows notes:

• Paths with spaces. Put them in quotes: npx jecbridge "C:\My Projects\app" --tunnel

• npx in JSON config. Claude Desktop on Windows may not find npx directly; use "command": "cmd" with "args": ["/c", "npx", "-y", "jecbridge", ...].

• JSON config. In Claude Desktop or Cursor config, write \ twice ("C:\Users\Abbos\my-app") or use / ("C:/Users/Abbos/my-app").

• Windows Firewall. If asked, allow Private networks. The server only listens on 127.0.0.1 and is reachable from outside only through the tunnel.

• CRLF files. Windows line endings (CRLF) are handled automatically: edits don't break the file format.

1. Web AIs (claude.ai, ChatGPT, Gemini)

A web AI can't see your computer, so JecBridge opens a tunnel:

npx jecbridge ~/projects/my-app --tunnel

The terminal prints a public URL like https://xxxx.trycloudflare.com/mcp/<token> and copies it to the clipboard. If cloudflared isn't installed, the official binary is downloaded once from Cloudflare's GitHub releases into ~/.jecbridge/bin.

⚠️ The URL contains a secret token, never share it. The token is stored in .jecbridge/token; delete that file to get a new one. A quick tunnel URL changes on every start. For a permanent address, use a Cloudflare named tunnel or an ngrok static domain.

2. Local clients (stdio)

Claude Desktop (claude_desktop_config.json) and Cursor (.cursor/mcp.json):

{
  "mcpServers": {
    "jecbridge": {
      "command": "npx",
      "args": ["-y", "jecbridge", "/FULL/PATH/my-app", "--stdio"]
    }
  }
}

Claude Code:

claude mcp add jecbridge -- npx -y jecbridge /path/my-app --stdio

3. A new project from scratch

npx jecbridge ~/projects/new-project --tunnel

Then tell the AI: "Build a Next.js + Tailwind landing page in this folder and check it with npm run build."

Options

Tools the AI gets

Security

• Folder jail. ../, absolute paths and symlinks can't escape the project.

• Secrets are hidden. .env*, .git/, *.pem, *.key and SSH keys can't be read, written or found by search.

• Command allowlist. By default only npm, node, python, pytest, go, cargo… are allowed. Chaining with &&, |, ;, $(, plus git push and git -C / --git-dir, is blocked.

  • Command arguments are checked too: cat .env, cat ../file, ls / and --prefix=.. are rejected.

  • Environment variables whose names contain TOKEN, SECRET, PASSWORD, API_KEY or AUTH are not passed to commands.

  • No shell is used: %VAR% isn't expanded on Windows, and arguments with spaces stay intact.

  • On timeout the command is stopped together with all its child processes.

  • Change the list: --allow npm,node,python

  • Allow everything: --allow-all-commands. Only on your own machine and with an AI you trust.

• Separate checkpoints. Stored in .jecbridge/shadow.git. Your own .git history is never touched.

• Token. Required on every HTTP request, in the URL or as Authorization: Bearer.

• --read-only. Read-only mode (for code review). Nothing is written into the project; server data lives in the temp folder.

⚠️ Safe mode is not a sandbox. Allowed programs such as node, python or npm test run project code, and that code can read any file on disk. The allowlist protects against accidents, not against a malicious AI or project. For real isolation, run JecBridge inside a Docker container or as a separate user.

Add .jecbridge/ to your own .gitignore.

AIs without MCP support

Plain APIs like DeepSeek, Ollama or the OpenAI API need an agent with an MCP client, for example:

• Cline or Continue (VS Code). They work with any OpenAI-compatible API and MCP servers.

• OpenAI Agents SDK. Connect to the same URL with MCPServerStreamableHttp.

Tests

npm test     # 28 end-to-end tests: build from scratch, edit, undo, security, dev servers, stdio, read-only, no-git

License

MIT