OAuth & Auth
MCPs that handle authentication, identity, and access control
TL;DR
OAuth MCP servers handle user authentication, access tokens, and role-based permissions so agents can act on a user's behalf without hardcoded credentials. Supabase Auth, Clerk, Auth0, and Google OAuth all expose MCP-compatible flows. Required for any multi-user agent product.
About OAuth & Auth
OAuth MCPs manage the authentication lifecycle — user login, token refresh, role-based access, and secret vaulting. They let agents operate on behalf of users securely without exposing credentials.
Common use cases
- Let an agent authenticate as a user via OAuth before reading their data
- Auto-refresh expired access tokens without user intervention
- Enforce per-user RLS (row-level security) from within the agent
- Integrate social login (Google, GitHub) into a multi-tenant app
- Vault and rotate API keys for downstream MCPs
Related recipes
Auto DB Migrations on Push
Every push to main triggers a Supabase migration automatically. Schema diffs are committed and applied with zero manual steps.
Issue → Branch → PR Pipeline
A Linear issue assigned to a developer automatically creates a git branch, syncs status changes, and opens a draft PR.
Related tags
Frequently asked questions
Does MCP support OAuth 2.1?
Yes — the MCP specification defines a standard OAuth 2.1 authorization flow for server-to-client and user-delegated access, including refresh tokens.
How do I avoid leaking secrets to the LLM?
Store secrets server-side. The MCP server holds tokens and passes only tool results to the LLM — credentials never enter the prompt.
Can I revoke agent access?
Yes — revoke the OAuth token at the provider (Google, GitHub, etc.) and the agent loses access immediately on next refresh.
Which is better for MCP: Clerk or Auth0?
Both work well. Clerk has a simpler developer experience; Auth0 has deeper enterprise features (SAML, SSO). Pick based on your team's needs.
Install OAuth & Auth MCPs
Browse the full directory or explore all tags to find the right MCPs for your stack.