Skip to content

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

Glossary entry. Checked on 19 November 2026 against MCP spec 2026-07-28.

OAuth for MCP, in plain words

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?

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.

Share this definition

Lessons that use this term

Sources

Official documentation, checked on 19 November 2026. Products change: if a step differs, the source has the current version.