Auth and identity for AI apps, agents, and MCP servers · Logto

Your AI apps, agents, and MCP servers inherit everything you already built in Logto: sign-in, enterprise SSO, MFA, RBAC, and Organizations. Ship AI features enterprises can actually adopt, in an afternoon.
Start with the problem you came with.
Dynamic app is CIMD (Client ID Metadata Document) under the hood, the client registration model the MCP spec recommends first. There is no parallel auth system to build and no spec to chase.
“Claude just returned 401 on your server. An enterprise prospect is asking whether agent access respects their SSO. And the spec moved to CIMD while you were building.”
AI agent or MCP client
Logto as identity provider
to manage agent access and consent
Turn your MCP server into a resource server and give AI agents scoped access, with user sign-in and explicit consent.
AI agent or MCP client
Logto as identity provider
to secure API access
Open your app or API to AI agents with access you choose. Logto manages authentication, scope, and tokens behind the scenes.
“Sign-in has to happen mid-conversation, without kicking the user out of the chat. Your CLI has no browser to redirect to. And half your new ‘users’ are scripts hammering the sign-up page.”
Can you show me my balance?
Sure! I can help you with that. Please sign in first.
Embed sign-in and SSO directly into your chatbot flow. Users are prompted when needed, and sent right back to the chat once signed in.
Opening your browser…
✓ Signed in as [email protected]
# headless box? device code
Visit example.com/device · AH7-3K9P
✓ Token saved to keychain
AI coding tools and agents ship as CLIs. Give them real sign-in: device code when there is no browser, authorization code with PKCE when there is.
Built-in security that is more than a CAPTCHA: layered protection right inside your sign-in experience. Logto brings security practices from SaaS to the agent world.
“Your agent needs the user’s Google Calendar. A token in a .env file is how incidents start.”
Your AI agent or client
to manage tokens and secrets
Third-party APIs or MCP servers
Enable your agent to act on behalf of users with third-party APIs. No manual token juggling, no storing secrets in plain text.
It is live in production today. Logto MCP Server docs →
That includes the hard part for B2B products: multi-tenancy. Every token an agent gets is scoped to one organization and to that user’s role in it.
Watch what it can do, then build the same for your product with the guides below.
How to build a remote MCP server for your SaaS product: MCP vs Agent Skills, OAuth integration, and MCP tools design.
Why token passthrough, M2M, and PAT all fell short, and how subject tokens with org-scoped access keep AI inside each user’s permissions.
Integrate Logto with your MCP server: authenticate users and retrieve their identity with the standard OpenID Connect flow.
Open your MCP server to third-party AI agents: client registration, user consent, and scoped access tokens.
AI surfaces keep changing. Your identity layer does not have to: point the one you already trust at whatever comes next.