MCP Connect Auth: Publish MCP Servers with OAuth Clients Can Actually Use
TL;DR
- MCP Connect Auth gives every published
/skillslisting a tenant authorization server — DCR, PKCE, protected-resource metadata, and federation to your existing sign-in. - Path B (bundle URL): publish, configure federation, point Claude/Cursor/ChatGPT at
https://mcp.mcpbundles.com/bundle/{slug}/— no pip install on your MCP server. - Path A (vendor origin): add
mcpbundles-mcp-connectwhen clients hit your own MCP URL. - Full reference: MCP Connect Auth integration doc.
If you've tried to publish a remote MCP server and stalled on OAuth, you're not alone. Certified MCP clients expect dynamic client registration, PKCE, protected-resource metadata, and a coherent authorization server. Rolling that stack while also shipping tools is a common reason listings sit at /skills with zero connections.