AI & Machine Learning
reachpad.dev
Provides persistent infrastructure for running coding agents continuously until tasks are completed.
ENDPOINT 1
https://reachpad.dev/mcp
MCP server metadata
- Name
- reachpad
- Version
- 0.4.1
This reachpad connection is NOT authenticated: the tools below can be read but none of them can be called. Every tools/call answers 401 until the connection is authorized through https://reachpad.dev/.well-known/oauth-protected-resource. Say that before attempting a tool, rather than reporting the tool as broken.
Known tools 11
create_workspaceCreate a persistent development workspace: a filesystem and processes that survive between calls.
Potential side effectsget_workspaceWhat a workspace resumes from: its head snapshot, how far its log had got, and its fork tree.
Inferred read-onlycheckpoint_workspaceFork a workspace from its last sealed snapshot into a new one.
Inferred read-onlylist_portsThe ports this workspace has open to the web, oldest first, with their links.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.reachpad]
url = "https://reachpad.dev/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"reachpad": {
"type": "http",
"url": "https://reachpad.dev/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: reachpad
Remote MCP URL: https://reachpad.dev/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"reachpad": {
"url": "https://reachpad.dev/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"reachpad": {
"type": "http",
"url": "https://reachpad.dev/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "reachpad",
"transport": "streamable-http",
"url": "https://reachpad.dev/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.