# How does sign-in (OAuth) work for MCP servers?

OAuth is the standard way a remote MCP server gets permission to act on your account: you approve on the service's own sign-in page and the app gets a token for that server. Under the 2026-07-28 spec, apps identify themselves with Client ID Metadata Documents (CIMD) instead of Dynamic Client Registration.

## For users

You approve access on the service's own page, your password never goes to the AI app, and you can revoke access in the service's settings. See [why does this server ask me to sign in?](https://ai-powered.com/academy/connect-mcp-servers/why-sign-in)

## For builders

The 2026-07-28 release deprecates Dynamic Client Registration (DCR) in favour of CIMD, requires clients to validate the issuer (`iss`) before redeeming an authorization code, and adds `application_type` for desktop and CLI clients with localhost redirects. The security best practices add: accept only tokens issued for your server, never pass a client's token through to another API, and ask for the smallest scopes first.

## Sources

Official documentation, checked on 19 November 2026:

- [The 2026-07-28 specification release (MCP blog)](https://blog.modelcontextprotocol.io/posts/2026-07-28/)
- [Security best practices (modelcontextprotocol.io)](https://modelcontextprotocol.io/docs/tutorials/security/security_best_practices)
- [Custom connectors using remote MCP (Claude Help Center)](https://support.claude.com/en/articles/11175166-getting-started-with-custom-connectors-using-remote-mcp)

## Related terms

- [Enterprise-Managed Authorization](https://ai-powered.com/academy/glossary/enterprise-managed-authorization): Enterprise-Managed Authorization (EMA) is an MCP extension that lets an organisation grant access to MCP servers through its identity provider. Admins set the policy once, and people get the approved servers when they sign in, without a separate consent screen for each server.
- [MCP](https://ai-powered.com/academy/glossary/mcp): MCP (Model Context Protocol) is an open standard for connecting AI applications to outside tools and data. An AI app connects to small programs called MCP servers, asks each one what it offers, and calls those tools when a task needs them.
- [Remote vs local MCP server](https://ai-powered.com/academy/glossary/remote-vs-local-mcp-server): A local MCP server is a program the AI app starts on your own computer and talks to over standard input and output (stdio). A remote MCP server runs on someone else's machine and the app reaches it over the internet by URL, using Streamable HTTP and usually a sign-in.
