Turn any MCP server into a remote HTTPS endpoint

Rmcp, a new open-source control plane, lets developers turn any MCP server into a remote HTTPS endpoint deployable to AWS Lambda or a local gateway, with support for Streamable HTTP, bearer or OAuth auth, and generated client snippets for VS Code, Cursor, Claude, and Notion. The tool, requiring Node >= 22 and pnpm, handles packaging, credentials, and transport, and verifies deployments with a real MCP initialize handshake.

Turn any MCP server into a remote HTTPS endpoint your AI clients can reach. Most MCP servers are npm packages that run as a local subprocess over stdio. That works on one machine, for one client. The moment you want the same server in Claude Desktop and VS Code and on your phone, you need it to be a remote server speaking Streamable HTTP — with TLS, authentication, and somewhere to keep the API keys. rmcp is the small control plane that does that. You paste an mcp.json-style definition into a web UI, click Deploy, and get back a URL and a config snippet for your client. It handles the packaging, the credentials, and the transport. php flowchart LR UI "Web UI<br/ define + deploy " -- API "Control plane<br/ Hono + SQLite" API -- |"target: local"| GW "Local gateway<br/ :8788" API -- |"target: lambda"| LAM "AWS Lambda<br/ + Function URL" GW -- B1 "bridge" LAM -- B2 "bridge" B1 -- S1 "stdio subprocess<br/ <i or</i upstream HTTP" B2 -- S2 "stdio subprocess<br/ <i or</i upstream HTTP" C "VS Code · Cursor · Claude" -.- |"Streamable HTTP<br/ + bearer or OAuth"| GW C -.- LAM Two server types. A stdio server is any npm-published MCP server — the kind you'd normally run with npx . rmcp installs it and runs it behind a Streamable HTTP bridge. An http server is one that's already remote; rmcp proxies it and injects the auth headers server-side, so your clients never hold the upstream credential. Two deploy targets , chosen per server at deploy time: local | lambda | | |---|---|---| | Runs on | your machine or your own box | AWS Lambda behind a Function URL | | Reachable at | http://<host :8788/<id LAN , or a public HTTPS URL if you front it with a reverse proxy | the Function URL | | Auth | bearer token or OAuth | bearer token | | Needs AWS | no | yes | | Cold start | none — kept warm while rmcp runs | yes | | Secrets live in | local SQLite | SSM Parameter Store | A fully local flow needs no AWS account at all. Client snippets, generated. Every deployed server has an Export view with ready-to-paste config for VS Code, Cursor, the Claude CLI, Claude Desktop, and Notion custom agents — with the right auth already filled in. - Node = 22 and pnpm corepack enable - macOS or Linux Only for the Lambda target: AWS credentials in ~/.aws , with permissions for Lambda, IAM role creation , SSM Parameter Store, and S3 packages over 45 MB are staged through an rmcp-deploy-<account -<region bucket . pnpm install pnpm --filter @rmcp/bridge build bundle the bridge — required before first run pnpm dev API on :8787, UI on :5173 Open http://localhost:5173 http://localhost:5173 . - Create a server. Give it a name a-z0-9- , up to 40 chars and either an npm package + version stdio or an upstream URL http . Declare each env var or header, marking the sensitive ones as secret . - Set the secrets on the server's page. Values go into rmcp's local SQLite database, and are pushed to SSM Parameter Store only when you deploy to Lambda. - Deploy — locally or to Lambda. Either way rmcp finishes by running a real MCP initialize handshake against the new endpoint, so a green deploy means the server actually answered. - Connect — open Export and copy the snippet for your client. Undeploy removes the compute but keeps your secrets. Deleting a server purges its secrets, and for servers with an AWS footprint, everything under /rmcp/<id / in SSM. VS Code — merge into .vscode/mcp.json : { "servers": { "my-server": { "type": "http", "url": "https://…/<id ", "headers": { "Authorization": "Bearer <token " } } } } Claude CLI — one command: claude mcp add --transport http my-server https://…/<id \ --header "Authorization: Bearer <token " Claude Desktop — depends on the target. Local servers front an OAuth authorization server that Claude Desktop speaks natively: add a custom connector, paste the client ID and secret from the Export view, and click Connect. A browser tab opens and closes by itself — there's nothing to approve. Lambda servers have no authorization server, so they go through the mcp-remote stdio bridge instead the Export view generates that config too . Cursor and Notion custom agents are also covered in the Export view. Endpoints are keyed by the server's UUID, not its name — renaming a server never changes its URL. Every endpoint is protected by a per-server bearer token, enforced identically on both targets. Local endpoints additionally accept OAuth access tokens, which resolve to the same bearer internally. The local gateway listens on all interfaces, so other devices on your LAN can reach it. To expose it to the internet, put a reverse proxy in front — see self-hosting /datascope-romania/rmcp/blob/main/docs/self-hosting.md , which covers exactly that with Caddy and automatic TLS. The UI follows your system theme, with a manual light/dark/auto toggle in the header. — how the control plane, gateway, bridge, and deployer fit together, and what a request actually does. Architecture /datascope-romania/rmcp/blob/main/docs/architecture.md — authentication, the OAuth server, where secrets live, and what this tool explicitly does not defend against. Security model /datascope-romania/rmcp/blob/main/docs/security.md — settings, environment variables, and the HTTP API. Configuration /datascope-romania/rmcp/blob/main/docs/configuration.md — running it on a Linux box behind Caddy with public HTTPS endpoints. Self-hosting /datascope-romania/rmcp/blob/main/docs/self-hosting.md apps/api control plane Hono , local gateway, OAuth server apps/web React + Vite UI packages/bridge Streamable HTTP → stdio / http-proxy; runs in Lambda and in-process packages/deployer AWS pipeline: stage, zip, IAM role, SSM params, function, healthcheck packages/shared zod schemas shared across the workspace pnpm test vitest across the workspace pnpm typecheck tsc --noEmit across the workspace pnpm e2e end-to-end deploy against real AWS needs credentials The bridge is the piece worth understanding first: the same makeHandler runs inside the Lambda and in-process behind the local gateway, which is why both targets behave identically down to the auth check. MIT — see LICENSE /datascope-romania/rmcp/blob/main/LICENSE .