Reachpad MCP is answering right now. Last checked 3 min ago. It exposes 11 tools. Last commit 1 Sep 2026.
Coding agents build full-stack apps in persistent workspaces and share them by link.
Installs per day
peak 684 · avg 88 · -1% w/w
a month agotoday
Uptime history
20 days of history
20 days agonow
100.0%
Uptime 24h
91 of 91 checks
11
Tools
read from the server
510 ms
Response time
average over 24h
3
Stars
last commit 1 Sep 2026
Tools have disappeared from this server
A tool that vanishes takes a piece of your agent with it, and the change arrives silently. Watch this server and every such change lands in your inbox.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.
run in your terminal
claude mcp add reachpad-mcp --transport http https://reachpad.dev/mcp~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"reachpad-mcp": {
"url": "https://reachpad.dev/mcp"
}
}
}~/.codex/config.toml
[mcp_servers.reachpad-mcp]
url = "https://reachpad.dev/mcp".cursor/mcp.json
{
"mcpServers": {
"reachpad-mcp": {
"url": "https://reachpad.dev/mcp"
}
}
}.vscode/mcp.json
{
"mcpServers": {
"reachpad-mcp": {
"url": "https://reachpad.dev/mcp"
}
}
}Available tools 11
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
workspace
create_workspace
Create a persistent development workspace: a filesystem and processes that survive between calls. Optionally clone a git repository into it. Returns the workspace id used by every other tool.
delete_workspace
Archive a workspace, freeing the plan slot it holds. Nothing is deleted: its snapshots and history survive, it simply stops counting as live and can no longer be used. A RUNNING workspace cannot be archived — pause_workspace first, or this is refused with `lease_held`.
get_workspace
What a workspace resumes from: its head snapshot, how far its log had got, and its fork tree. Every start is a cold boot from the head snapshot: files survive, running processes do not.
checkpoint
checkpoint_workspace
Fork a workspace from its last sealed snapshot into a new one. The original is untouched. This is how you try several approaches from one prepared state — the fork costs a delta, not a rebuild.
command
run_command
Run one command in a workspace and get its exit code and output. Not a shell: pass argv as a list, and ask for a shell explicitly with ["/bin/sh","-lc","…"] if you want one. A paused workspace resumes to serve this.
credit
get_credit_balance
Show this account's remaining compute credits. One credit runs one standard workspace for one minute; paused workspaces use no compute credits.
expose
expose_port
Open a port inside a workspace and get back a link that reaches it. This is how something you built becomes something a person can open. Idempotent per port: re-running it returns the link the port already has.
pause
pause_workspace
Save the workspace's disk and stop the meter. Files survive; RUNNING PROCESSES DO NOT — a paused workspace cold-boots, so anything you started with run_command has to be started again. The next run_command resumes it automatically. Pause when you are done: a running workspace spends a credit a minute whether or not anything is happening in it, and it cannot be archived while it runs.
ports
list_ports
The ports this workspace has open to the web, oldest first, with their links. Revoked ports are not listed: a closed link never comes back.
revoke
revoke_port
Close one port to the web. The link stops working at the visitor’s next request. NOT reversible in the way callers expect: re-opening the same port later mints a DIFFERENT link, so revoke only when the people holding the current one should lose it.
workspaces
list_workspaces
List this account's workspaces, with how many forks each has.
Tools removed
These were exposed before and are gone now. No other catalogue tracks this.
checkpoint_environment
removed 25 Aug 2026
create_environment
removed 25 Aug 2026
delete_environment
removed 25 Aug 2026
get_environment
removed 25 Aug 2026
list_environments
removed 25 Aug 2026
pause_environment
removed 25 Aug 2026
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://reachpad.dev/mcp | streamable-http | answering | 370 ms | 3 min ago |
Alternatives to Reachpad MCP
same job, measured the same wayTakoCode
by takocode
Build, preview and publish full-stack web apps with TakoCode's hosted coding agent.
Cdbx
by cdbx
Build Apps and run code in 30 languages — sandboxed, with persistent sessions for agent loops.
Builderforce
by seanhogg
Run tickets, boards, OKRs and cloud coding agents in your Builderforce workspace
OBTO
by obto
Your AI builds, deploys, and runs full-stack apps on a hosted workspace created at first sign-in.
Charming
by tambo-ai
Build personal interactive apps with real URLs and persistent storage, using any AI.
Writespace MCP
by write-space
Persistent docs and memory for AI agents — read, write, organize & search a shared workspace.
Floot
by floot
Build and publish full-stack web and mobile apps on Floot from any MCP client. Building is free.
MCP Light Memory
by peterpirog
Local-first persistent memory for coding agents and MCP clients.
Reachpad MCP — questions
Answers built from our own checks of this server.
What can Reachpad MCP do?
It exposes 11 tools, read directly from the server on our last check. Among them: checkpoint_workspace, create_workspace, delete_workspace, expose_port, get_credit_balance, get_workspace and 5 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
Is Reachpad MCP working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 510 ms. The bar chart above shows every period we have measured.
Did Reachpad MCP ever remove tools?
Yes. checkpoint_environment, create_environment, delete_environment, get_environment and 2 more are no longer exposed — we recorded the date each one disappeared. A tool vanishing usually means a breaking change for anything that depended on it.
How do I connect Reachpad MCP?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Reachpad MCP need an API key?
No. Reachpad MCP completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 11 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Reachpad MCP?
It answers our handshake in 510 ms on average, which is faster than 33% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Reachpad MCP open source?
Yes — it is published under the MIT licence, written in JavaScript and 3 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.