Clerk MCP. Manage every user account and organization structure.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Clerk manages user authentication and multi-tenant structures directly through your AI client. Get instant programmatic control over user profiles, organizations, and invitation lifecycles without touching a dashboard.
It's full auth governance via natural conversation.
What your AI agents can do
Create auth invitation
Sends a new, trackable email invitation to a specified recipient's address.
Create auth organization
Establishes a new, isolated organizational environment within your application.
Get auth user details
Fetches specific, detailed metadata for one individual user based on their ID.
Retrieves the complete list of every active and dormant account in your application.
Sets up a new multi-tenant container, allowing you to segment and manage different groups within one system.
Fetches detailed metadata for a single user, including their full contact information and authentication status.
Shows you all the distinct organizational structures currently set up in your system.
Dispatches trackable email invites to new users, complete with custom redirect URLs for smooth onboarding.
Ask AI about this MCP
Supported MCP Clients
OAuth 2.0 Compatible Gemini Waiting for input…
Clerk: Authentication Management (6 Tools)
These six tools give your agent full command over user directories, organization structures, invitation lifecycles, and individual account metadata.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Clerk on Vinkius019dd0cecreate auth invitation
Sends a new, trackable email invitation to a specified recipient's address.
019dd0cecreate auth organization
Establishes a new, isolated organizational environment within your application.
019dd0ceget auth user details
Fetches specific, detailed metadata for one individual user based on their ID.
019dd0celist auth invitations
Provides an overview of all pending and past user invitations that have been sent out.
019dd0celist auth organizations
Shows all multi-tenant containers or organizations that currently exist in the system.
019dd0celist auth users
Retrieves a comprehensive list of every registered user in the application's directory.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Clerk, then connect any of our 4,800+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,800+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Clerk. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 6 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
The Pain Point: Manual User Auditing
Right now, checking who has access to what is a nightmare. You open the admin dashboard, click through multiple tabs, and copy/pasting user IDs into spreadsheets just to see if they belong to the correct organization. If you need to track down a single person's full history—their current status, their contact info, which department they fall under—you spend half an hour clicking around.
With this MCP, your agent handles it in one go. You simply ask your AI client for details on a specific user or list all the tenants available. The information flows directly to you, giving you immediate operational reports without leaving your chat window.
Getting Clarity with Clerk's Auth Tools
The manual steps that vanish are navigating between user listings and organization views. You don't have to manually verify if an invitation was sent correctly, or which organizational container the new account belongs in.
Now you can build complex auth workflows—like creating a new department, inviting three users, and confirming their details—all by speaking to your agent. It’s instant governance.
What you can do with this MCP connector
Managing user access used to mean digging deep into separate dashboards or writing complex scripts just to check if an account was active. This MCP lets your agent handle that complexity in plain language. You can list and manage every registered account, pull detailed profiles for any specific user, and coordinate the entire organization structure programmatically.
Need to bring a new team member on board? Your agent handles sending trackable invitations via email. If you need to check who's in what department or if an organization needs restructuring, it figures out the relationships for you. Because this MCP deals with sensitive credentials, Vinkius routes all keys through a zero-trust proxy; your secrets never sit on disk.
This means you can treat user authentication as just another conversation topic—your AI acts like a dedicated auth architect managing everything from user directory listings to invitation tracking.
019dd0ce-c3f0-73b3-b778-ae7b3c0abfa7 
How Clerk MCP Works
- 1 First, subscribe to this MCP and retrieve your Secret Key from the Clerk Dashboard.
- 2 Next, you talk to your agent using natural language commands—for instance, asking it to list all users or create a new organization.
- 3 Finally, your agent executes the required actions, returning structured data on user status, invitation IDs, and organizational details.
The bottom line is that you manage complex user workflows by talking to your AI client instead of clicking through multiple developer portals.
Who Is Clerk MCP For?
The Platform Engineer who gets frustrated having to switch between the auth dashboard, CRM, and ticketing system just to verify permissions. The Ops Manager tired of manual onboarding processes that require dozens of clicks.
Uses this MCP to programmatically list all users or create new organizations as part of a feature build, validating access roles before deployment.
Automates the onboarding pipeline by sending invitations and tracking the lifecycle status without needing manual intervention on the dashboard.
Quickly checks user authentication history or lists all existing organizations to audit access control across your multi-tenant environment.
What Changes When You Connect
- List all users: Instead of exporting a CSV just to count accounts, asking your agent to list all users gives you an instant directory view. You know exactly who's registered right now.
- Organization architecture control: Need to see how many separate teams exist? Calling the tool to list organizations shows you every tenant boundary in real time, letting you coordinate complex team setups.
- Automated onboarding: Use the invitation tools to dispatch emails and track them. Your agent handles sending the invite and recording its status so you never lose a signup lead.
- Deep user visibility: Never guess about a profile again. You can retrieve detailed user profiles—getting all the metadata you need—without jumping through five different tabs.
- Auditability: Need to know who was supposed to get access? Listing invitations lets you monitor the entire onboarding pipeline, checking every sent invite's status.
Real-World Use Cases
Onboarding a new department
The Ops Manager needs 10 people added. They ask their agent to first create a new organization, then list all the users in that group, and finally dispatch invitations for every single person on the approved roster.
Auditing team access rights
A Security Admin needs to confirm if anyone has suspicious credentials. They ask the agent to get user details for a specific ID and then list all organizations that ID belongs to, verifying least privilege.
Reactivating dormant accounts
The Product Manager discovers an old organization needs updating. They use the tool to list existing organizations first, identify the correct slug, and then get user details on key personnel for review.
Debugging a failed signup flow
A Developer notices a new signup link isn't working. They ask their agent to list invitations, find the specific invitation ID, and check its status to see if it was accepted or if there’s a redirect issue.
The Tradeoffs
Treating user data as static
Assuming that just because you know an email address, the user account must exist and be active. You might try to build logic based only on a simple list of emails.
→
Don't guess. Always use list_auth_users first to confirm existence, then follow up with get_auth_user_details if you need specific metadata. This confirms the account is live.
Skipping organizational setup
Trying to invite users before defining which team or department they belong to, leading to orphaned accounts and unclear access roles.
→
Always start with create_auth_organization when onboarding a new group. This establishes the correct multi-tenant container for all subsequent user activities.
Manual invitation tracking
Sending invites via email and then having to check an external spreadsheet or dashboard days later to see who clicked the link.
→
Use create_auth_invitation through your agent. The system tracks it, and you can monitor its status by calling list_auth_invitations. It's automatic.
When It Fits, When It Doesn't
Use this MCP if your core problem is managing the lifecycle of users and the boundaries (organizations) they operate within. You need to know who exists, what groups they belong to, and how they got there. If you just need a simple list of emails without any associated user metadata or ability to control tenancy, then this MCP is overkill. Don't use it if your only goal is basic contact management; stick with a general-purpose directory tool instead. However, if you are building an app that requires strict user provisioning and multi-tenancy controls, this combination of tools—especially create_auth_organization paired with invitation tracking—is non-negotiable.
Common Questions About Clerk MCP
How do I check if an account exists using the list_auth_users tool? +
You use list_auth_users first to get a directory of all IDs. If you find the ID, then call get_auth_user_details to confirm its current status and full profile data.
What is the difference between list_auth_organizations and create_auth_organization? +
list_auth_organizations reads the existing structure, showing you all active tenants. create_auth_organization actually builds a new container for an entirely separate group of users.
Can I track invitations using list_auth_invitations? +
Yes. list_auth_invitations gives you a record of all sent invites, letting you see their status and ensuring no new user signups are falling through the cracks.
Do I need to use get_auth_user_details when creating an invitation? +
No. While get_auth_user_details fetches existing data, you only need to call create_auth_invitation if the user does not yet have an active account.
When I use get_auth_user_details, what specific high-fidelity data points can my agent pull on a user's authentication status? +
It pulls detailed metadata covering the full lifecycle of an account. You can access current contact info, historical authentication records, and the precise operational status of the user without needing to manually check separate logs.
What is the process for ensuring I have multi-tenant visibility when running list_auth_organizations? +
You need access to view all organizations and their related team structures. The agent can monitor these environments in real time, allowing you to coordinate access control across multiple distinct operational silos.
If I use create_auth_invitation, how do I verify that the invitation was sent correctly and track its unique ID? +
You run list_auth_invitations immediately after sending. This shows you a comprehensive directory of all invitations, confirming the dispatch and providing the specific ID for tracking purposes.
If I need to build an automated workflow starting with list_auth_users, can my agent then use that data to perform another action? +
Yes. Your AI client uses the user directory from list_auth_users as input context for subsequent calls. For instance, it can take a list of users and automatically trigger multiple create_auth_invitation commands.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.