Clerk MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | The port number for the HTTP server | 5000 |
| CLERK_SECRET_KEY | Yes | Your Clerk secret key (starts with sk_live_ or sk_test_) | |
| NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY | Yes | Your Clerk publishable key (starts with pk_live_ or pk_test_) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list-usersB | Lista todos os usuários cadastrados no Clerk com paginação |
| delete-userA | Deleta permanentemente um usuário do Clerk pelo ID. Esta ação é irreversível! |
| lock-userA | Bloqueia um usuário do Clerk, impedindo que ele faça login |
| unlock-userB | Desbloqueia um usuário do Clerk, permitindo que ele faça login novamente |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: delete-user removes users permanently, list-users retrieves user data, lock-user blocks login access, and unlock-user restores it. There is no overlap in functionality, making tool selection straightforward for an agent.
All tool names follow a consistent verb_noun pattern (delete-user, list-users, lock-user, unlock-user), using hyphen separation and clear action verbs. This uniformity enhances readability and predictability.
With 4 tools, the count is reasonable for user management, but it feels slightly thin as it lacks create-user and get-user operations. This may limit full CRUD coverage, though the existing tools are well-scoped.
The tool set covers deletion, listing, locking, and unlocking users, which handles lifecycle management well. However, there are notable gaps: no create-user or get-user tools, which are essential for a complete user management surface, potentially causing agent workarounds.