Bring Authentication
to Claude Desktop
Learn how to connect Clerk to Claude Desktop and start using 6 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Clerk MCP Server?
Connect your Clerk account to any AI agent and take full control of your user authentication and multi-tenant management workflows through natural conversation.
What you can do
- User Orchestration — List and manage all users registered in your application programmatically, including retrieving detailed high-fidelity profiles and contact info
- Organization Architecture — Access and monitor organizations and multi-tenant environments to coordinate team collaboration and access control in real-time
- Invitation Lifecycle — Programmatically send and track user invitations via email with custom redirect URLs to streamline your onboarding pipeline
- Account Integrity — Retrieve detailed user metadata and manage authentication status directly through your agent for instant operational reporting
- Developer Visibility — Access complete directories of auth-related resources to maintain a perfectly coordinated and secure development ecosystem
How it works
1. Subscribe to this server
2. Retrieve your Secret Key from the Clerk Dashboard (API Keys section)
3. Start managing your user-centric applications from Claude, Cursor, or any MCP client
No more manual status checking or digging through user tables in the portal. Your AI acts as your dedicated auth architect and user management coordinator.
Who is this for?
- Developers & Admins — instantly retrieve user profiles and manage multi-tenant setups using natural language commands
- Operations Teams — automate the dispatch of invitations and monitor organization growth without leaving your workspace
- Customer Success — check user authentication history and manage invitations through simple AI queries
Built-in capabilities (6)
Send an invitation
Create an organization
Get user details
List invitations
List organizations
List all users
Why Claude Desktop?
Claude Desktop is the definitive way to connect Clerk to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 6 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
Clerk in Claude Desktop
Clerk and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Clerk 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 | 3,400+ 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 Clerk in Claude Desktop
The Clerk 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 6 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
Clerk for Claude Desktop
Every tool call from Claude Desktop to the Clerk MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my Clerk Secret Key?
Log in to the Clerk Dashboard, select your application, and navigate to API Keys in the sidebar.
Can I manage organizations via AI?
Yes! The create_auth_organization and list_auth_organizations tools allow your agent to manage B2B tenants and teams programmatically.
How do I send a user invitation?
Use the create_auth_invitation tool and provide the recipient's email address. You can also specify an optional redirect URL for the signup flow.
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.