Reachpad/reachpad-mcp

Overview

MCP server for reachpad that lets coding agents like Claude and Codex build full-stack apps in persistent workspaces and share them via link, without a separate deployment step. Written in JavaScript.

Best for

Best for
Developers experimenting with MCP-driven agent workspaces

Use cases

• Give Claude a persistent workspace for a multi-file app build
• Share a working app prototype by link from an agent session
• Let an agent manage deployment through MCP without manual steps

How to use

Install

npx -y @reachpad/mcp          # stdio, for a local client

Tools exposed

• REACHPAD_ENDPOINT
• REACHPAD_IDENTITY_CREDENTIAL
• REACHPAD_API_KEY
• REACHPAD_MCP_HTTP_PORT
• REACHPAD_MCP_HTTP_HOST
• REACHPAD_MCP_HTTP_TOKEN
• REACHPAD_MCP_HTTP_NO_AUTH
• REACHPAD_MCP_ALLOWED_ORIGINS

Tested with

Claude Code, Cursor, ChatGPT

Notes

MCP server for reachpad that lets coding agents like Claude and Codex build full-stack apps in persistent workspaces and share them via link, without a separate deployment step. Written in JavaScript.

3 stars on GitHub. Last updated 2026-09-02. Licensed MIT.

Use cases

• Give Claude a persistent workspace for a multi-file app build
• Share a working app prototype by link from an agent session
• Let an agent manage deployment through MCP without manual steps

Pros

• Persistent workspaces keep context across agent sessions
• Link-based sharing simplifies demos and handoffs
• No separate deployment process required

Cons

• Very low adoption with only 3 GitHub stars
• Requires an MCP client and a reachpad service to function
• Unclear production readiness or maintenance activity

Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.