All servers / Identity / Clerk
Clerk
Clerk user management.
Tested by ConnectATDScore 51 out of 100. Tested 2026-11-17 on package version 0.0.13. Package: @clerk/clerk-mcp
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 10 / 20 | |
| Package safety | 12 / 20 | |
| Maintenance | 3 / 20 | |
| Adoption | 8 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (19.1 seconds including download)
- Tools offered: 14
- Last published: 2025-05-22
- Weekly downloads (npm): 557
- License: none listed · Direct dependencies: 2
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
CreateClerkNextJSAppno parametersQuickstart for creating a clerk next js app
CreateClerkReactAppno parametersQuickstart for integrating Clerk into a React app
GetSession0 of 2 parameters describedRetrieve the details of a session
GetUserList0 of 2 parameters describedReturns a list of all users. The users are returned sorted by creation date, with the newest users appearing first.
CreateUser0 of 2 parameters describedCreates a new user. Your user management settings determine how you should setup your user model. Any email address and phone number created using this method will be marked as verified. Note: If you are performing a migration, check out our guide on [zero downtime migrations](https://clerk.com/docs/deployments/migrate-overview). A rate limit rule of 20 requests per 10 seconds is applied to this endpoint.
GetUsersCount0 of 2 parameters describedReturns a total count of all users that match the given filtering criteria.
GetUser0 of 2 parameters describedRetrieve the details of a user
DeleteUser0 of 2 parameters describedDelete the specified user
UpdateUser0 of 3 parameters describedUpdate a user's attributes. You can set the user's primary contact identifiers (email address and phone numbers) by updating the `primary_email_address_id` and `primary_phone_number_id` attributes respectively. Both IDs should correspond to verified identifications that belong to the user. You can remove a user's username by setting the username attribute to null or the blank string "". This is a destructive action; the identification will be deleted forever. Usernames can be removed only if they are optional in your instance settings and there's at least one other identifier which can be used for authentication. This endpoint allows changing a user's password. When passing the `password` parameter directly you have two further options. You can ignore the password policy checks for your instance by setting the `skip_password_checks` parameter to `true`. You can also choose to sign the user out of all their active sessions on any device once the password is updated. Just set `sign_out_of_other_sessions` to `true`.
BanUser0 of 2 parameters describedMarks the given user as banned, which means that all their sessions are revoked and they are not allowed to sign in again.
ListInvitations0 of 2 parameters describedReturns all non-revoked invitations for your application, sorted by creation date
CreateInvitation1 of 2 parameters describedCreates a new invitation for the given email address and sends the invitation email. Keep in mind that you cannot create an invitation if there is already one for the given email address. Also, trying to create an invitation for an email address that already exists in your application will result to an error.
RevokeInvitation0 of 2 parameters describedRevokes the given invitation. Revoking an invitation will prevent the user from using the invitation link that was sent to them. However, it doesn't prevent the user from signing up if they follow the sign up flow. Only active (i.e. non-revoked) invitations can be revoked.
ListDomains0 of 1 parameter describedUse this endpoint to get a list of all domains for an instance. The response will contain the primary domain for the instance and any satellite domains. Each domain in the response contains information about the URLs where Clerk operates and the required CNAME targets.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.