Workbench MCP Server
Provides git status and command execution capabilities within the project, including viewing recent commits and running git commands.
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., "@Workbench MCP ServerUse project_info to get an overview of the 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.
Workbench MCP Server
An MCP server for remote access to a project over the network. It lets a
Claude CLI running on another machine read/write files, search code, run
allow-listed commands and work with git in the context of a chosen project — and
also launch a Claude CLI on the host machine in the background (claude_start).
Originally built for Workbench, but it
works with any project — the path is set via MCP_PROJECT_ROOT.
Quick start
git clone https://github.com/jazz-max/workbench-mcp.git && cd workbench-mcp
npm install
cp .env.example .env
# edit .env: set MCP_AUTH_TOKEN and MCP_PROJECT_ROOT
npm startOn a successful start you'll see:
MCP server listening on http://0.0.0.0:3100/mcp (auth enabled)
Project root: /path/to/your/projectInstall via npm / npx
Without cloning the repository:
# one-off run, no install
MCP_AUTH_TOKEN=<token> MCP_PROJECT_ROOT=/path/to/project npx workbench-mcp
# or install globally
npm install -g workbench-mcp
MCP_AUTH_TOKEN=<token> MCP_PROJECT_ROOT=/path/to/project workbench-mcpWhen run via
npx/global install there is no.envnext to the server — set the configuration via environment variables directly. In this caseMCP_PROJECT_ROOTis required (otherwise the server doesn't know which project to serve).
Run via pm2 (recommended for long-running use)
pm2 start server.mjs --name workbench-mcp
pm2 save
pm2 startup # start on boot (one-time)
pm2 logs workbench-mcp # logs
pm2 restart workbench-mcp # restart after changesRelated MCP server: pokeclaw
Configuration (.env)
Variable | Default | Description |
|
| Server port |
| (empty) | Bearer token. Without a token the server runs without authentication (use only on a trusted local network) |
| parent directory | Absolute path to the project the server serves |
Generate a token: node -e "console.log(crypto.randomUUID())"
Connecting Claude CLI (from another machine)
# host IP (macOS): ipconfig getifaddr en0
claude mcp add workbench \
--transport http \
--url http://<IP>:3100/mcp \
--header "Authorization: Bearer <TOKEN_FROM_.env>"
claude mcp list # verify
claude mcp remove workbenchTools
Tool | Description |
| Project overview: |
| Read a file (path relative to project root), up to 1 MB, with line numbers |
| Write a file (creates directories). Forbidden: |
| List a directory (optionally recursive, name filter), up to 500 entries |
| Search by content (regex/grep), glob filter, excludes |
| A command from the allowlist, |
| Current branch, |
| Launch |
| Status and result of a background task by |
allowlist for run_command: git, php, composer, npm, node, npx, ls, cat, head, tail, find, grep, rg, wc, diff, file, which, pwd, echo
Scenario: remote development from two machines
Machine A — the project and the MCP server. Machine B — the Claude CLI for exploration.
LAN (port 3100)
Machine B ──────────────────────> Machine A
Claude CLI MCP server
(research, specs) (project files, git, commands)Note: Claude Code CLI must be installed on both machines — on B as the client that connects to the MCP server and drives the work, and on A, where
claude_startruns Claude locally on the host for coding.
A typical flow for a new feature:
The MCP server is running on machine A.
In the Claude CLI on machine B:
> Use project_info to understand the project structure > Read app/Servlets/BaseServlet.php — the base class > Read app/Servlets/DemoBooksScraper.php — an example > Research example.com and write a spec to docs/spec.mdWithout switching to machine A, ask your Claude to delegate the coding to the host:
> Ask claude on the workbench to write the parser per docs/spec.mdClaude on machine B calls
claude_start→ a separate Claude CLI launches on machine A ("the workbench") and writes the code. Collect the result viaclaude_result.
Security
Requests are protected by a Bearer token (
MCP_AUTH_TOKEN). Without a token the server runs without authentication — only expose it on a trusted network.run_commandis restricted to an allowlist and usesexecFile(no shell injection).write_fileforbids writing to.env*,node_modules/,vendor/.The server grants remote access to files and command execution — do not expose it to the public internet without a separate reverse proxy with TLS and authentication.
Troubleshooting
Cannot connect: both machines on the same network; check the IP;
curl http://localhost:3100/mcpshould return 405; check the firewall (macOS may ask to allow Node.js).Unauthorized: the token in
--headermust matchMCP_AUTH_TOKEN.Command not allowed: the command is not in the allowlist.
Port in use:
lsof -ti:3100 | xargs kill -9.
License
MIT.
This server cannot be installed
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/jazz-max/workbench-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server