mcp-proxy
Provides MCP integration with Sentry, using dynamic client registration to authenticate and forward MCP requests to Sentry's MCP server.
Provides MCP integration with Slack, allowing Claude to connect to Slack workspaces via a custom Slack app and interact with Slack through the MCP server.
Provides MCP integr
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-proxySend a message to the #general Slack channel"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-proxy — mcp.austindevs.com
Multi-account front door for remote MCP servers that only let claude.ai connect one account per URL.
https://mcp.austindevs.com/<service>/<account>/mcpservice | upstream | upstream auth |
slack | your own internal Slack app per workspace — entered in claude.ai as Use your own OAuth client (or Worker vars) | |
sentry | dynamic client registration (automatic) | |
trello | dynamic client registration (automatic) |
<account> is a free-form label (zollege, paycove, …). It exists so each claude.ai custom
connector has a unique URL and therefore its own token; the actual workspace/org is picked on the
upstream consent screen.
How it works
Toward Claude, the Worker is an OAuth 2.1 authorization server with dynamic client registration (
@cloudflare/workers-oauth-provider), so any custom connector "just works".When Claude hits
/authorize, the Worker reads the RFC 8707resourceparam to learn which<service>/<account>the connector is for, then bounces you through the upstream's own OAuth (discovered via RFC 9728 / RFC 8414). The upstream token is stored in KV under a random id that is sealed into the Claude-facing grant.Every MCP request on
/<service>/<account>/mcpis forwarded to the upstream with that token (refreshing it when it expires).Mcp-Session-Idand streaming responses pass straight through.
Related MCP server: Box MCP Proxy Server
Adding an account in claude.ai
Customize → Connectors → Add custom connector → URL https://mcp.austindevs.com/slack/zollege/mcp
(no client id/secret needed) → Connect → log into the workspace you want.
Slack (bring your own client, no Worker config)
Slack's MCP server has no dynamic client registration and only allows internal (or
Marketplace-listed) apps, so you need one Slack app per workspace. Then, in claude.ai's Add custom
connector dialog, choose OAuth client → Use your own OAuth client and paste that app's
client ID and secret. The Worker recognises the 1234567890.1234567890 ID format, uses it as the
Slack app for that connector, and completes the Slack code exchange with the secret Claude sends
at /token — nothing to configure on the Worker.
Per workspace at api.slack.com/apps: create app → Agents → enable Slack Model Context Protocol
(MCP) Server → OAuth & Permissions → add redirect URL https://mcp.austindevs.com/callback and
the user scopes you want (see https://mcp.slack.com/.well-known/oauth-protected-resource) →
copy Client ID / Client Secret from Basic Information.
Config (optional Worker vars/secrets)
SLACK_<ACCOUNT>_CLIENT_ID/SLACK_<ACCOUNT>_CLIENT_SECRET(orSLACK_CLIENT_ID/SLACK_CLIENT_SECRET) — alternative to BYO client: lets a plain DCR connector work for/slack/<account>/mcp.<SERVICE>_<ACCOUNT>_SCOPES/<SERVICE>_SCOPES— trim the scopes requested upstream.SENTRY_*/TRELLO_*— optional; DCR is used when unset.
Build & deploy
npm install
npm run build # dist/worker.min.js
npx wrangler deploy # or: PUT dist/worker.min.js via the Workers APITool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
No tool schema history has been recorded yet.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Hosted MCP server with managed OAuth for 15+ toolkits: Google Workspace, Fitbit, Oura, Kalshi, etc.
OAuth scope approvals and consent receipts for remote MCP servers.
Governed MCP gateway: one endpoint for your tools, with credential custody and audit log.
MCP server connecting AI agents to 100+ apps (Gmail, Slack, Notion, GitHub) via one-click OAuth.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceAuthenticating reverse proxy for MCP servers providing credential isolation, OAuth2 token management, and composite tool aggregation.BSD Zero Clause
- FlicenseNot gradedqualityDmaintenanceA proxy server that bridges MCP clients with Box's remote MCP server, handling OAuth 2.0 authentication and message forwarding over HTTP.1-
- AlicenseNot gradedqualityBmaintenanceBridge that lets stdio-only MCP clients connect to remote MCP servers with OAuth and other auth support, enabling local clients to use remote, authorized MCP servers.24353MIT
- AlicenseNot gradedqualityBmaintenanceEnables clients to access multiple backend MCP servers through a single endpoint, with OAuth 2.1 authorization, namespaced tools, and secure credential management.MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/kevincolten/mcp-proxy'
If you have feedback or need assistance with the MCP directory API, please join our Discord server