MCP Authentication in 2026
The Model Context Protocol (MCP) changed how agents talk to servers. It started with local tools like calculators. Now it runs on remote servers. This shift made authentication a requirement.
If you want to add OAuth to your MCP server, prepare for a moving target. The spec changes every few months. Different agents use different versions of the rules.
Here is the current state of MCP authentication.
The Core Shift
Your MCP server is not an authorization server. It is a resource server.
In the past, the spec forced servers to handle tokens and logins. This made servers heavy and hard to scale. Experts like Aaron Parecki and Christian Posta called this out. They argued that MCP servers should only validate tokens.
Today, the standard follows this flow:
• An unauthenticated request gets a 401 error. • The error tells the client where to find resource metadata. • The client finds the correct authorization server (like Okta or Keycloak). • The client gets a token and presents it to your MCP server. • Your server validates the token and runs the tool.
The Fragmentation Problem
Even though a standard exists, every agent implements it differently.
• Claude Desktop: Runs the full OAuth flow. • Claude API: Requires you to pass your own bearer token. • ChatGPT: Uses CIMD for registration and supports the latest spec. • Gemini: Uses Google Cloud IAM and API keys. • VS Code: Supports GitHub and Entra providers.
This means a server built for one agent might fail on another. One vendor might require a full login flow, while another expects you to manage the token yourself.
Three Lessons for Developers
Target the Resource Server model. Do not try to become an identity provider. Use RFC 9728 to serve metadata and validate the audience.
Support two worlds. Build your server to handle both "bring your own token" API calls and full OAuth flows.
Expect constant updates. The spec is still evolving. OAuth 2.1 is still a draft, and the MCP protocol is still finding its footing.
Building MCP servers is difficult right now. The rules change fast. If you stay flexible and stick to the resource server model, you will survive the shifts.
Optional learning community: https://t.me/GyaanSetuAi