Authorization: Bearer <their token>. Your system decides what each person may see and do, and every call is attributable to them.
Set it up
1. Turn on the sign-in broker
Theclient-auth service runs each sign-in and keeps the token.
Air-Gapped values:
2. Create a client at your identity provider
Confidential, authorization code flow, the redirect URI above (also shown as Redirect URL in step 4), scopesopenid profile email offline_access. The access token must name your MCP connector in its audience (aud). xpander does not send the RFC 8707 resource parameter, so the identity provider must add it (Keycloak: an Audience mapper on the client’s dedicated scope).
3. Make the MCP connector accept the token
Publish OAuth metadata on the MCP connector’s origin (How xpander finds your identity provider, below). Answer a missing or bad token with401 and a WWW-Authenticate header:
email_verified: false, the sample refuses them, and they just see the Sign in to card again.
How xpander finds your identity provider
How xpander finds your identity provider
xpander finds your identity provider from the MCP connector’s origin, using the first address that answers:
/.well-known/oauth-authorization-serveron the MCP connector’s origin (RFC 8414)./.well-known/oauth-protected-resourceplus the server URL’s path (RFC 9728). xpander reads the firstauthorization_serversentry, then that server’s RFC 8414 metadata.
scopes_supported, so list only your client’s scopes.Any 401 or 403, or any WWW-Authenticate header, means “sign-in needed” to xpander. It uses the addresses above, not the header’s resource_metadata link. Send the header anyway for other MCP clients.Why the token checks matter
Why the token checks matter
- Verified email only. Anyone can type an email into a profile.
email_verifiedsays the identity provider checked it. If you can map people bysub(the stable user id), use that instead. - Keycloak: Verify email is off by default (Realm settings > Login). Turn it on, or set Email verified per user.
- Audience check. The MCP spec forbids accepting a token not issued for the server. If your identity provider cannot add an audience, check
azpequals the step 2 client instead. That is weaker: it trusts every token issued to that client.
4. Register it for the organization
Settings > Skills > MCP servers tab > Add server: Shared with Organization, the server URL, Authentication OAuth2, the Client ID and Client secret. Admins can also use the Skills registry, and owners an agent’s Add skill (where to register).
Add server with OAuth2. Shown with sample data.
5. Attach it to a shared agent
In the agent’s settings, Add skill, pick the entry (shown as Organization), and give the agent Org-wide access.
Add skill lists the organization entry. Shown with sample data.
What two people see
Alice and Bob ask the same agent “What equipment do I have?”. Each signs in once, then gets only their own equipment.
Alice's first prompt: sign in once. Shown with sample data.

Alice gets her equipment. Shown with sample data.

Bob's first prompt on the same agent: his own sign-in. Shown with sample data.

Bob gets his equipment, not Alice's. Shown with sample data.
Limits
- Runs nobody started. A schedule, a webhook, or a Slack, Teams or email message from a non-member has no person to sign in. The call uses the agent’s Default background user (agent settings, Skills > Background runs) or the server’s User for background runs, who must have signed in once. With none set, the call is refused. See What an unattended run may use. A message from a member runs as that member.
- Who can read the answers. An answer fetched with a person’s token stays in their conversation. On an Org-wide agent, every member can open that conversation, and the creator can on any agent. For owner-only data, share the agent with named people instead. See Permissions.
Sign in ahead of time, or disconnect
A person can sign in before any agent asks: Settings > My tools lists the MCP and API connectors they can use, and Sign in connects them once for every agent and AI tool. The same page shows each sign-in they hold, with the agents that use it (My tools). To disconnect, open the sign-in and choose Disconnect, or Disconnect all in the page’s menu (shown when there is more than one). Pasted keys stay. xpander deletes its copy of the token but does not revoke it at your identity provider; end your session there to revoke it. The next request shows the Sign in to card again.If it fails
Messages and causes
Messages and causes
Next steps
Add skills served over MCP
Where skills are added.
Choose whose credential an agent uses
Agent and conversation permissions.
Set a user for background runs
Unattended runs.

