@reachpad/mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REACHPAD_API_KEY | No | Optional, per-environment scoped and revocable. When set, run_command uses it and needs no identity exchange. | |
| REACHPAD_ENDPOINT | No | Your reachpad host. Plaintext http:// to anything but loopback is refused before a socket opens. | |
| REACHPAD_MCP_HTTP_HOST | No | 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. | 127.0.0.1 |
| REACHPAD_MCP_HTTP_PORT | No | Serve HTTP instead of stdio. | |
| REACHPAD_MCP_HTTP_TOKEN | No | Bearer token, compared in constant time. Absent, every caller that can reach the port is authorized, and the server says so on stderr. | |
| REACHPAD_IDENTITY_CREDENTIAL | No | Your per-user credential. It names one account and can act for no other. | |
| REACHPAD_MCP_ALLOWED_ORIGINS | No | 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. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_credit_balanceA | Show this account's remaining compute credits. One credit runs one standard environment for one minute; paused environments use no compute credits. |
| create_environmentA | Create a persistent development environment: a filesystem and processes that survive between calls. Optionally clone a git repository into it. Returns the environment id used by every other tool. |
| list_environmentsA | List this account's environments, with how many forks each has. |
| get_environmentA | What an environment 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. |
| run_commandA | Run one command in an environment 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 environment resumes to serve this. |
| checkpoint_environmentA | Fork an environment 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. |
| delete_environmentA | Archive an environment, 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool addresses a distinct concern: credit balance, environment lifecycle, and command execution are cleanly separated. Even checkpoint_environment is unambiguous because it explicitly forks an environment into a new one.
All tools follow a consistent verb_noun pattern in snake_case, such as create_environment, list_environments, and delete_environment. Singular/plural usage is natural and predictable.
Seven tools is well-scoped for managing persistent development environments: credit checking, creation, listing, inspection, command execution, forking, and deletion/archival. No tool feels redundant or out of place.
The environment lifecycle is covered end-to-end: create, read (list/get), fork/checkpoint, execute commands, and delete/archive. The credit balance tool fills the one supporting need for running environments, leaving no obvious dead ends.