WorkOS AuthKit for MCP
WorkOS AuthKit guide and support for securing MCP servers that require authentication.
Tags
Description
Client ID Metadata Document (CIMD) support is off by default and enabled in the WorkOS Dashboard; Dynamic Client Registration (DCR) can be enabled for backwards compatibility with MCP clients that don't yet support CIMD.
Agent access
Related
- MCP Authorization (OAuth 2.1 for MCP): The MCP specification's transport-level authorization flow for HTTP-based MCP servers, based on a subset of OAuth 2.1 and related RFCs.
- OAuth Client ID Metadata Document (CIMD): IETF OAuth draft letting a client identify itself with a URL as its client_id, pointing to a metadata document, without prior dynamic registration.
- WorkOS Vault: Developer-friendly enterprise key management (EKM) to encrypt and optionally store tokens, passwords, certificates, files and other customer data.
Guides & comparisons
- Add OAuth authorization to your own MCP server (Guide): A server-side walkthrough of the MCP 2026-07-28 authorization spec: publish RFC 9728 protected resource metadata, answer 401 and 403 challenges, verify JWT audience per RFC 8707, enforce per-tool scopes, and never pass tokens through. Tested with the MCP TypeScript SDK v2.
- Agent auth and delegated access, step by step (Guide): How an agent acts for a user without holding their passwords: CIMD client registration, the MCP 2026-07-28 OAuth flow with resource indicators and audience checks, no token passthrough, vaulted third-party tokens, CIBA approvals and Cross App Access (ID-JAG).
- Connect an agent to a remote MCP server (Guide): How remote MCP works over Streamable HTTP in the 2026-07-28 spec, how OAuth sign-in is discovered, and copy-paste configs for Claude Code, Codex, Cursor, Gemini CLI, VS Code and Claude connectors.
- Agent identity and MCP authorization platforms (Comparison): Descope, Stytch Connected Apps, Auth0 for AI Agents, WorkOS AuthKit and Arcade compared on their role in MCP OAuth, DCR and CIMD support, delegated tokens for third-party APIs, human approval, pricing and SDKs.
Sources
Machine-readable
- JSON
- Markdown
- Source file on GitHub (edit via pull request)