You paste a server's URL into your assistant and, instead of tools, you get a sign-in page. Did something go wrong? Usually not. A server that works with your data in a service, such as your issues, your files or your CRM, needs to know it's acting for you, and you need a way to take that access back.
The three kinds of sign-in you'll meet
When our checks reach a hosted server that wants sign-in, it usually asks in one of three ways, and the listing page says which:
- OAuth. You're sent to the service's own login page, approve what the app may do, and come back. Your password never goes to the AI app, and you can revoke the access in the service's settings. This is the standard way, and the safest for you.
- A bearer token. The service gives you a token, and you add it as a header (
Authorization: Bearer …). Claude calls these Request headers; Grok Bot calls them HTTP headers. - An API key. Similar to a token, under a header name from the server's docs.
Tokens and keys work, but they're easy to leak and often have wide access. Prefer OAuth when a server offers it, and create a key with the smallest permissions the service allows when it doesn't.
What the apps let you choose
As of 19 November 2026, Claude's custom connector form offers Sign in now, Sign in when needed or No sign in, plus request headers for fixed credentials. ChatGPT offers OAuth, No authentication, or OAuth or no authentication, where listing tools needs no sign-in and each tool asks only if it needs to.
When your company manages it
In June 2026 the MCP project made Enterprise-Managed Authorization stable. Your IT team grants servers to people through the company's identity provider, and you're connected on first login without a separate consent screen per server. The MCP blog names Okta as the first identity provider and Claude, Claude Code and Cowork as clients, with VS Code support in preview. If your company uses it, you may see servers appear without signing in to each.
Behind the scenes
The July 2026 version of the MCP specification also changed how apps register for sign-in: an older method (Dynamic Client Registration) is deprecated in favour of Client ID Metadata Documents. You don't have to do anything about it as a user; it's one reason sign-in flows may look slightly different over the coming months.
In short
- Sign-in means the server works with your account; that's normal.
- OAuth is the best option for you; tokens and keys need more care.
- In companies, IT can manage access centrally, so you sign in once.
What to try next
Share this lesson- Check the rest of a server's trust signals: Is this MCP server safe?
- Want to see a server that needs no sign-in? Connect ours.