parallelsandbox-mcp
OfficialClick on "Deploy 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., "@parallelsandbox-mcpsync the current project to sandbox box ab12cd and run the test suite"
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.
parallelsandbox-mcp
stdio adapter for the ParallelSandbox MCP server. It exposes the same tools as https://mcp.parallelsandbox.com/mcp
(sandbox_*, logs_*), forwarding every call with your API key, and implements sandbox_sync and sandbox_pull
locally: an agent can upload its working directory into a box without committing, and write files from the box back to
its machine. Get an API key (psbx_…) in the app: https://app.parallelsandbox.com → Account → API keys.
Use
PARALLELSANDBOX_API_KEY=psbx_... npx parallelsandbox-mcpClaude Code:
claude mcp add parallelsandbox -e PARALLELSANDBOX_API_KEY=psbx_... -- npx -y parallelsandbox-mcpAny other MCP client: run the command above as a stdio server.
If you never need sandbox_sync or sandbox_pull, you can skip this package and connect directly (over plain HTTP
those two tools return an error, because they read and write files on your machine):
claude mcp add --transport http parallelsandbox https://mcp.parallelsandbox.com/mcp --header "Authorization: Bearer psbx_..."Related MCP server: scriptit
Environment
Variable | Default | Purpose |
| required | API key from the app |
|
| MCP endpoint |
|
| REST base used by |
sandbox_sync
{"id": "<box id>", "localPath": "/abs/path/to/repo", "dest": "repo"} syncs localPath into /work/<dest> on the box.
Pass an absolute path: a relative one resolves against this adapter's working directory (where your MCP client started
it), which is not necessarily the agent's. In a git working tree it takes the tracked files plus the untracked files .gitignore does not
exclude, asks the box which of them differ from what is already in dest, and uploads only those, so syncing after an edit
sends just that edit. A file changed inside the box counts as different and gets the local version back. Outside git it
uploads the whole directory, excluding node_modules, .git, dist, build, coverage, .venv and similar. Files
deleted locally stay in the box.
sandbox_pull
{"id": "<box id>", "path": "<path under /work>", "localPath": "/abs/path/on/your/machine"} downloads a file or a
directory from the box. A directory arrives as a tar.gz and is extracted into localPath (pass "extract": false to keep
the archive); a file is written to localPath. Relative paths resolve the same way as for sandbox_sync.
Which conversation is using a box
Each time the adapter starts it picks a random id and sends it as X-Psbx-Agent on every call. After the first tool call
it reports to /v1/agents/<id>/heartbeat once a minute, and when its conversation closes (stdin ends, or SIGTERM, SIGINT
or SIGHUP) it reports /v1/agents/<id>/leave. The app uses this to tell a box the AI is still working in from one whose
conversation was closed without sandbox_review or sandbox_stop; a conversation killed outright (no leave) counts as
gone three minutes after its last heartbeat. Nothing else is sent: no prompt, no transcript.
Timeouts
sandbox_takeover blocks until a person hands the box back, up to 30 minutes; the adapter waits 31 minutes for it and
65 minutes for other calls (a foreground sandbox_exec runs at most 60 minutes).
Source and issues
Source: https://github.com/parallel-sandbox/parallelsandbox-mcp. Report bugs there as issues, or from inside a session
with the sandbox_feedback tool. MIT licensed.
Related MCP Connectors
Develop, manage, and debug Railway projects, services, and deployments from within agents.
Read a project's prompts, logs and agents, and send new work to the agent on your own machines.
Securely control computers you explicitly pair through files, terminals, processes, screenshots, desktop UI/input, clipboard, browser automation, diagnostics, and document tools.
Get share links, publish and manage websites, artifacts and agents. No account needed.
Related MCP Servers
- AlicenseNot gradedqualityAmaintenanceEnables MCP clients to connect to a local workspace over a public tunnel and lets them run shell commands and transfer files bidirectionally.262 npm21GPL 3.0
- FlicenseNot gradedqualityCmaintenanceEnables agents to connect to remote MCP servers once, access their tools through a compact MCP endpoint, pair a CLI inside sandboxes, and create watches that turn command or tool output into pollable structured events.2-
- AlicenseAqualityBmaintenanceEnables an AI agent to run local tools on the user's own machine via stdio, including command execution, workspace file read/write, and system status checks.52MIT
- AlicenseAqualityBmaintenanceEnables Codex to use an installed Devin CLI as an additional worker by starting, polling, and cancelling bounded tasks through local MCP tools. It runs as a local stdio server in a given working directory, so jobs execute with the Devin account's model and permissions while Codex's own routing rules still decide when to delegate.31MIT