Spec Driven Development
by formulahendry
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Runs on your computer★ 440MITUpdated 14 months ago
Install
Reachpad MCP
Overview
Description from the maker (original English)
Coding agents build full-stack apps in persistent workspaces and share them by link.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Computer or cloud
- Transport: stdio, Streamable HTTP
- Category: Other
- You need to fill in: REACHPAD_IDENTITY_CREDENTIAL
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on the maker’s server: what you ask it goes through their server.
- You fill in yourself:
REACHPAD_ENDPOINT,REACHPAD_IDENTITY_CREDENTIAL
Values marked secret are keys to your account. Never share them or paste them into a chat.
You need
- Runs in the cloudNothing to install; it connects over the internet
- npmNode.js installed (for the npx command)
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
- Open Settings → Connectors
- Press Add custom connector
- Paste the address below and press Add
- If it asks you to sign in, sign in with the maker
https://reachpad.dev/mcpOr run it on your computer
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"reachpad": {
"command": "npx",
"args": [
"-y",
"@reachpad/mcp"
],
"env": {
"REACHPAD_ENDPOINT": "your-value",
"REACHPAD_IDENTITY_CREDENTIAL": "your-value"
}
}
}
}Run this in your terminal
claude mcp add --transport http reachpad https://reachpad.dev/mcpOr run it on your computer
claude mcp add reachpad --env REACHPAD_ENDPOINT=your-value --env REACHPAD_IDENTITY_CREDENTIAL=your-value -- npx -y @reachpad/mcpFill in the empty values before running it.
Or copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"reachpad": {
"url": "https://reachpad.dev/mcp"
}
}
}Or run it on your computer
Or copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"reachpad": {
"command": "npx",
"args": [
"-y",
"@reachpad/mcp"
],
"env": {
"REACHPAD_ENDPOINT": "your-value",
"REACHPAD_IDENTITY_CREDENTIAL": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"reachpad": {
"type": "http",
"url": "https://reachpad.dev/mcp"
}
}
}Or run it on your computer
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"reachpad": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@reachpad/mcp"
],
"env": {
"REACHPAD_ENDPOINT": "your-value",
"REACHPAD_IDENTITY_CREDENTIAL": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
- Open ChatGPT on the web → Settings → Connectors (Apps)
- Press Create or Add (some plans need Developer mode under Advanced first)
- Paste the address below, give it a name and save
- If it asks you to sign in, sign in with the maker
https://reachpad.dev/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
Values you fill in
REACHPAD_ENDPOINTenvYour reachpad host. Defaults to m1.reachpad.dev.- Your per-user credential from reachpad.dev/connect. Names one account and can act for no other.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
We have not read this server’s tool list yet; we check endpoints in rotation.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account Reachpad, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- … Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
- … Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
- … Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint
Compared with others in Otheri
- More stars than 0% of the other 32655 servers in this category
- Published to the registry more recently than 32% of the other 32655 servers in this category
- Basic checks equal to or better than 100% of the other 32655 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Reachpad MCP safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
You need to fill in: REACHPAD_IDENTITY_CREDENTIAL
Does it run on my computer or in the cloud?
Either way works: install it on your computer or connect to the cloud version.
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.4.2) reached the registry 2 months ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
What can I use instead?
In the same category: Spec Driven Development, Remote Desktop Commander, SuperCollider
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Remote Desktop Commander
by desktop-commander
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Runs in the cloud★ 211Updated 2 days ago
Install
SuperCollider
by Tok
Make sound with SuperCollider: synths, drums, chords, melodies and soundscapes over OSC.
Runs on your computerUpdated today
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
@reachpad/mcp
reachpad lets Claude, Codex and other coding agents build full-stack apps in persistent workspaces and share them by link, without a separate deployment. A workspace is a cloud development computer an agent operates itself: a repo, a filesystem, installed dependencies and build state that all survive between calls, not an ephemeral sandbox that forgets. Processes are the exception; see below.
This is the MCP server. It lets Claude, ChatGPT, Cursor, OpenCode or your own agent create a workspace, run commands in it, fork it, and come back to it later, without a developer keeping a laptop open for them.
- It persists. Pause it and the disk is sealed; the next call boots from that seal with the files, installs and git state intact, rather than rebuilding. Processes are the exception: a start is always a cold boot.
- It forks. Twenty attempts from one prepared state cost a delta each, not twenty rebuilds — because the workspace is a snapshot chain, not a machine.
- It can keep secrets out of the workspace. A brokered credential is called at the boundary on your behalf and its value never enters the workspace, the log or the store. A credential written into the workspace instead is readable there, by design.
- It is agent-agnostic. The REST API is canonical; this server, the SDK and the CLI are translations of it. Bring your own agent.
The API is the product boundary, not a web UI: reachpad.dev.
Install
npx -y @reachpad/mcp # stdio, for a local clientIn Claude Code:
claude mcp add reachpad -e REACHPAD_IDENTITY_CREDENTIAL=… -- npx -y @reachpad/mcpTwo transports, one implementation
npx @reachpad/mcp # stdioREACHPAD_MCP_HTTP_PORT=8722 npx @reachpad/mcp # streamable http
stdio is what a local client talks to; Streamable HTTP is what a remote connector talks to. Same tools, same behaviour — added rather than forked, because two implementations of one surface is how they drift.
The HTTP side answers 405 to `GET`: every tool here is request/response, and the spec permits declining the server-initiated stream rather than holding a connection open for traffic that never comes. There are no sessions — nothing is held across calls that a restart could not rebuild. And it carries no credential of its own: whatever authorizes the HTTP request is what authorizes reachpad.
It is authenticated by default. Set REACHPAD_MCP_HTTP_TOKEN and that is the bearer token; set nothing and one is generated for the run and printed on stderr, because a port that bridges to your account with run_command behind it should not be open to every other process on the machine:
reachpad mcp: streamable http on http://127.0.0.1:8722reachpad mcp: no REACHPAD_MCP_HTTP_TOKEN was set, so this one was generated for this run:
Authorization: Bearer 3Qk…
reachpad mcp: it changes every restart. Set REACHPAD_MCP_HTTP_TOKEN to pin it, or reachpad mcp: REACHPAD_MCP_HTTP_NO_AUTH=1 to serve with no authentication at all.
Serving with no authentication is still available and is now something you say out loud: REACHPAD_MCP_HTTP_NO_AUTH=1.
Configure
| variable | meaning |
|---|---|
REACHPAD_ENDPOINT | your reachpad host. Plaintext http:// to anything but loopback is refused before a socket opens. |
REACHPAD_IDENTITY_CREDENTIAL | your per-user credential. It names one account and can act for no other — the server takes the identity from the credential's own record, never from the request. |
REACHPAD_API_KEY | optional, per-workspace scoped and revocable. When set, run_command uses it and needs no identity exchange. |
REACHPAD_MCP_HTTP_PORT | serve HTTP instead of stdio. |
REACHPAD_MCP_HTTP_HOST | default 127.0.0.1. This process bridges to a control plane with your credentials, so binding it to the world is a decision made on purpose, behind a proxy that terminates TLS. |
REACHPAD_MCP_HTTP_TOKEN | bearer token, compared in constant time. Absent, one is generated for the run and printed on stderr — the endpoint is never unauthenticated by omission. |
REACHPAD_MCP_HTTP_NO_AUTH | 1 serves with no authentication at all: every caller that can reach the port is authorized. An affirmative choice, not a default. |
REACHPAD_MCP_ALLOWED_ORIGINS | comma-separated. A request carrying an unlisted Origin is refused — a browser cannot forge it, which closes DNS rebinding. No Origin at all is a non-browser client and is allowed. |
If several credentials are set, the narrowest wins, and a refused credential is never retried under a broader one — falling back would be privilege escalation nobody chose to perform.
Tools
| tool | what it does |
|---|---|
get_credit_balance() | remaining compute credits. One credit runs one standard workspace for one minute. |
create_workspace(repo?, ref?, name?) | a new workspace, optionally with a repository cloned into $HOME/work. Reachpad generates its display name when omitted. |
list_workspaces() | your workspaces and how many forks each has |
get_workspace(workspace) | what it boots from: its head snapshot, its log position and its fork tree |
run_command(workspace, argv, cwd?, env?, timeout_ms?) | one command, its exit code and its output. A paused workspace resumes to serve it. |
checkpoint_workspace(workspace, name?) | fork from the last sealed snapshot; the original is untouched |
expose_port(workspace, port, check?) | open a port to the web and get the link that reaches it. Idempotent per port. |
list_ports(workspace) | the ports this workspace has open, oldest first, with their links |
revoke_port(workspace, port) | close one port. Re-opening it later mints a different link. |
delete_workspace(workspace) | archive it and free the plan slot. Nothing is deleted — snapshots and history survive. |
Renamed in 0.4.0. Six tools used to be spelled *_environment and took an environment argument, while the CLI, the manual and the dashboard all said workspace. There was only ever one object; now there is only one word for it. The old names and the old argument still work and are not advertised, so nothing that already calls them breaks — but write new calls against the workspace spelling.
Not here, deliberately: starting an agent inside the workspace. It is in reachpad's roadmap and not in the fleet yet — a tool that always fails costs a model a turn and teaches it to distrust the rest, so this server advertises nothing it cannot serve.
What a port link is, and is not
Worth reading before you hand one to somebody, because none of it is discoverable from the URL:
- Anyone signed in to Reachpad who has the link can open it. It is not a private URL and not a secure one. Treat it like a preview deployment.
- The link is an address, not a copy. Restart the app on the same port and the same link serves the new version.
- A running process does not survive a pause. The workspace cold-boots with its files intact and nothing running, so after a pause the link answers with an error until something is listening on that port again. A visitor's request wakes a paused workspace; it does not restart anything inside it.
- `expose_port` dials the port afterwards and tells you if nothing answered, because a link to a port nothing is serving looks exactly like a link that works. Pass
check: falseto skip it — the dial resumes a paused workspace. - With only `REACHPAD_API_KEY`, the key must be `--role owner`. A
collaboratorkey is refused: listing hands back live tokens, and a token is a capability.
The rules it is built to
These are the ways a naive client of a streaming exec API misleads a model, and what this one does instead.
- An unterminated stream is UNKNOWN, never success. If the response ends without a terminal event, the tool says so in those words. It is not a zero exit, and an agent must not retry a non-idempotent command on the strength of it.
- Its deadline is looser than the server's, so a server-side answer always wins the race. A client that gives up first turns "your build finished" into "unknown", and the numbers are mirrored from the server rather than guessed.
- Refusals carry remedies, not codes. At your plan limit you get the limit, your current count, and what to do — the numbers come from the server, because a limit hardcoded in a client is a lie the moment your plan changes.
- Results are handles, not payloads. Output is tailed with the dropped byte count named. Build logs can be megabytes, and an MCP result that size destroys the caller's context window.
- A refusal is a result, not a transport error, so the model can read it and act. Only an unknown *tool* is a protocol error.
Test
node --test 'test/*.test.mjs'No network and no credentials. The protocol suite spawns the shipped server as a child process and speaks real JSON-RPC over its stdio against a stub control plane on a real socket, so nothing under test is an internal import. One test runs the same arc against a real reachpad and skips when no endpoint is configured.
Repository
This repository is the source. It is deliberately separate from the reachpad backend: this code is public, it is published to npm, and its release workflow holds publishing rights — none of which belong in the same repository as the control plane. Nothing here can read the backend's source, and no job in the backend copies files out to here.
Two server constants are mirrored in src/client.js — the exec grace period and the default exec timeout. A mirrored constant normally rots; this one does not, because the backend's own CI fetches this published package and fails if they disagree. The check lives where the number would change.