MCP Elicitation vs MCP Authorization
People think URL mode elicitation is how a client signs in to an MCP server. It is not. MCP authorization is the OAuth sign-in between the client and the server, and it gives the client a token. URL mode elicitation is for the server's own needs, such as a key for some other service. You type that secret on a web page, and the client never sees it.
MCP Elicitation
A server stops a job to ask the user a quick thing, like a date.
MCP elicitation lets a server ask the user for more facts in the middle of a task. The server answers a request with a message and a simple form, such as a date or a yes or no choice. The client shows the form, and the user can answer, decline or cancel. Then the client sends the first request again with the answer, and the task goes on. A server must never use a form to ask for passwords or keys. It sends a web link for those.
MCP Authorization
How a remote MCP server checks who may use it. It uses OAuth sign-in.
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.
In one line
- MCP Elicitation
- A server stops a job to ask the user a quick thing, like a date.
- MCP Authorization
- How a remote MCP server checks who may use it. It uses OAuth sign-in.