Skip to content
BENIBIX Learn

MCP Authorization

AI🔌 MCPTransports and Authorization

Also known as MCP Auth, MCP OAuth

How a remote MCP server checks who may use it. It uses OAuth sign-in.

Think of it like

Think of it like a ticket at a gate. You show it, and the guard lets you in to the parts you paid for.

Example

Jack links his agent to his company's remote sales server. A sign-in window opens and he logs in once. The agent can then read only the accounts Jack can see.

Why it matters

Remote servers hold real data. This makes sure each user can reach only their own.

Definition

MCP authorization is how a remote MCP server checks that a client may use it, and for whom. It is based on OAuth, the same sign-in method many websites use. When a client first calls, the server says it needs a token. The client sends the user to a sign-in page, gets a token, and adds it to each request. Local stdio servers skip this and get their keys from the computer they run on.
Refused at first, the client sends the user to sign in, gets a token, and tries again.

Common mistake

Giving all users the same admin token. Each person's agent should only get what that person can see.

Key takeaways

  1. 1
    Built on OAuth. Standard sign-in.
  2. 2
    A token per user. Sent with each request.
  3. 3
    Remote servers only. Local ones use the computer.

Compare