Add OAuth to a FastMCP server
Point an agent at your FastMCP codebase and have it wire bearer-token auth plus the discovery endpoints MCP clients require.
Each card's body is the prompt. Fill in the bracketed placeholders, paste it into Claude Code or your agent of choice, and it carries the endpoint requirements so you don't have to.
Point an agent at your FastMCP codebase and have it wire bearer-token auth plus the discovery endpoints MCP clients require.
Build the thin proxy that owns discovery and DCR on your domain while Auth0 handles login and tokens — accepting Claude, ChatGPT, and Grok as clients.
Configure a 2026 Auth0 tenant for MCP connectors entirely through the Management API: DCR flag, resource-parameter audience profile, CIMD, and a JWKS-validating resource server.
A systematic run of the seven checks that isolate where an MCP OAuth connection breaks.
Enable Connected Apps, dodge the project-domain metadata trap, host the authorization page, and validate Stytch JWTs — with M2M-based headless tests.
Wrap a Workers-hosted MCP server with workers-oauth-provider so discovery, DCR, and tokens all live on the Worker.
Route /mcp and the OAuth discovery endpoints through Caddy with a Let's Encrypt certificate that renews itself.
Enable Supabase's OAuth Server beta, force the DCR toggle through the Management API, and validate the ES256 tokens in your MCP server — plus a fully headless CI proof.
Wire the redirect URI, CIMD/DCR client identification, and discovery endpoints ChatGPT expects from a custom MCP connector.
Prepare an OAuth-protected MCP server for Grok's Bring Your Own MCP connectors, without hardcoding callback URLs that may change.
Stand up your own authorization server for MCP connectors — Hydra on loopback behind Caddy, DCR enabled, the null-scrubbing registration proxy, and offline JWT validation.