Compatible with every major AI agent and IDE
What is the Logto (Auth Platform) MCP Server?
Connect your Logto authentication platform to any AI agent and take full control of your identity management and access control workflows.
What you can do
- User Management — List, fetch, update, or delete users from your tenant with full metadata access.
- RBAC & Permissions — Create and list global roles and API resources to manage granular access control.
- Organizations — Handle multi-tenant structures by creating organizations and managing their memberships.
- Security & Verification — Verify user passwords and manage account-level security settings.
- Account API — Access and update the current user's profile and MFA settings using end-user tokens.
How it works
- Subscribe to this server
- Provide your Logto Management API credentials (Endpoint, App ID, and App Secret)
- Start managing your auth infrastructure from Claude, Cursor, or any MCP-compatible client
Who is this for?
- DevOps & Security Engineers — Quickly audit user lists, roles, and resource permissions without leaving the terminal.
- Full-stack Developers — Manage test users and organization structures directly from the code editor.
- Support Teams — Inspect user metadata and account statuses to resolve identity-related tickets faster.
Built-in capabilities (23)
Bind a new MFA factor (TOTP, WebAuthn)
Create a new organization
Create a new API resource
Create a new role
Delete a Logto user
Retrieve current user profile (Account API)
Get details for a specific Logto user
List registered MFA factors for the current user
List members of an organization
List organizations in Logto
List API resources in Logto
List global roles in Logto
List roles assigned to a user
List Logto users
Remove an MFA factor
Send email/SMS code for verification
Update basic profile (username, name, avatar)
Update user password
Update or link primary email
Update extended profile (address, etc.)
Update an existing Logto user
Verify password to get a verification ID
Verify a user password (Management API)
Why Claude Desktop?
Claude Desktop is the definitive way to connect Logto (Auth Platform) to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 23 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
Logto (Auth Platform) in Claude Desktop
Logto (Auth Platform) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Logto (Auth Platform) to Claude Desktop through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Logto (Auth Platform) in Claude Desktop
The Logto (Auth Platform) MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 23 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Claude Desktop only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Logto (Auth Platform) for Claude Desktop
Every tool call from Claude Desktop to the Logto (Auth Platform) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I see which roles are assigned to a specific user?
Yes! Use the list_user_roles tool with the target User ID to retrieve all global roles associated with that account.
Is it possible to manage multi-tenant organizations through this server?
Absolutely. You can use list_organizations to see existing ones, create_organization to add new ones, and list_organization_users to audit membership.
Can I update user profiles or suspend accounts?
Yes, the update_user tool allows you to modify the username, name, avatar, and the isSuspended status of any user.
How does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.
Explore More MCP Servers
View all →
User-Agent Parser
1 toolsDecode raw HTTP User-Agent strings instantly. Extract structured Browser, OS, and Device data for accurate IT log analysis.

Mailjet
12 toolsDeliver emails at scale with collaborative template editing, real-time monitoring, and deliverability analytics in one platform.

HTML to Text Extractor
1 toolsStop wasting AI context on messy HTML code. Instantly strip CSS, tags, and scripts to extract perfectly readable Plain Text.

MLflow (ML Lifecycle Management)
6 toolsManage ML lifecycle via MLflow — track training runs, monitor metrics, and audit the model registry.
