MCP gateway
Add servers once. One URL in every AI client.
mcpw connects the MCP servers you use to Claude, ChatGPT, Cursor and the rest through a single gateway URL. Your accounts and keys stay in the gateway; the model never sees them.
How it works
Three steps, about two minutes.
1Add a server
Pick one from the catalog or paste any MCP server URL. mcpw probes it and lists its tools.
2Connect it
Sign in to the service or paste a key. The credential is encrypted to the gateway on the spot; the dashboard and the model never hold it.
3Install
Copy your profile URL into any client. Install steps are written out for each one, and every client you connect sees the same tools.
Clients
One URL. Every client you already use.
Verified on the production gateway
- OAuthClaude Code
- OAuthclaude.ai
- OAuthChatGPT
Install steps included
- OAuthClaude Desktop
- OAuthCursor
- OAuthWindsurf
- OAuthVS Code
- OAuthGemini CLI
- OAuthCodex CLI
Everything else
- Header-only client
- Other OAuth-capable client
If it speaks MCP over HTTP, it can use mcpw: OAuth 2.1 with dynamic registration, or a bearer token you mint in the dashboard.
Security
Your keys stop at the gateway.
Encrypted per connection
Each credential is sealed with HPKE to a key only the gateway process holds. The dashboard stores it and cannot read it.
The model sees tools, not secrets
Clients get tool names and results. The gateway adds your credential to the upstream call and nothing about it comes back.
Activity you can audit
Every tool call is listed with its name, time, status and duration for thirty days. Arguments and results are never stored.
Leave cleanly
Disconnect a server or delete your account at any time. Deletion removes your data and queues revocation of every upstream token the gateway was given.
Coming: wrap your own APIs as MCP tools, and reusable skills your clients can share.