Proxy Setup
Route your MCP clients through MCPHub's transparent proxy to enable logging, monitoring, and alerting.
Proxy Setup
MCPHub's proxy sits between your MCP client and server. It requires zero changes on the server side — you only update the URL your client uses.
Finding your proxy URL
After registering a server, open its detail page. The proxy URL is shown at the top:
The server_id is the UUID assigned when you registered the server.
Authentication
Requests to the proxy must include one of:
- JWT —
Authorization: Bearer <access_token>(from login) - API key —
X-API-Key: <key>(from workspace settings)
For automated agents and CI/CD, use an API key. For interactive use, the access token works.
Claude Desktop
Update your claude_desktop_config.json:
If the server uses a custom transport that accepts headers directly:
Custom agent (Python)
Custom agent (TypeScript)
Verifying it works
After routing a request through the proxy:
- Go to Tool Calls in the sidebar
- Your tool call should appear within a few seconds
- Check the Servers page — the server status should update after the first probe
If calls aren't appearing, check that your API key belongs to the same workspace as the registered server.