# OAuth 2.1 authorization for MCP, defined with a sourced example

GLOSSARY, read 10 Nov 2026

**The short answer.** The sign-in flow the MCP specification defines for HTTP servers. A user approves access in a browser, and the client holds a token scoped to that user. Calls then run with that person's permissions, not a shared secret. Per Monte Carlo's docs, its hosted MCP server supports OAuth 2.1 with Dynamic Client Registration, and requires an Editor role or above.

## Definition

The sign-in flow the MCP specification defines for HTTP servers. A user approves access in a browser, and the client holds a token scoped to that user. Calls then run with that person's permissions, not a shared secret.

## Example from a real server

**Example.** Per Monte Carlo's docs, its hosted MCP server supports OAuth 2.1 with Dynamic Client Registration, and requires an Editor role or above.

## Related terms

- [persona scoping](/glossary/persona-scoping/): Limiting what an agent can see or do by the persona of the signed-in person, such as admin, member or guest.
- [personal access token](/glossary/personal-access-token/): A long-lived secret a person creates in a tool to let a script or agent act as them.
- [monitor as code](/glossary/monitor-as-code/): Defining a data monitor as configuration kept in a repository instead of clicking it together in a UI.

## Where to read more

- [The directory](/)
- [All glossary terms](/glossary/)

## Sources

- docs.getmontecarlo.com/docs/mcp-server: https://docs.getmontecarlo.com/docs/mcp-server (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://datamcpservers.com/glossary/oauth-2-1-authorization-for-mcp/
