Clerk MCP Server
Provides comprehensive user management tools for Clerk, including listing users with pagination, permanently deleting users, and locking/unlocking user accounts to control login access.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Clerk MCP Server list the last 5 users who signed up"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
š Clerk MCP Server
Servidor MCP (Model Context Protocol) para gerenciamento completo de usuĆ”rios do Clerk. Este projeto permite que vocĆŖ integre facilmente as funcionalidades do Clerk com qualquer cliente MCP compatĆvel, incluindo Cursor AI, Claude Desktop e VS Code.
⨠Funcionalidades
Este servidor MCP expƵe 4 ferramentas essenciais para gerenciar usuƔrios do Clerk:
š ļø Ferramentas DisponĆveis
Ferramenta | Descrição | Parâmetros |
| Lista usuÔrios com paginação |
|
| Deleta permanentemente um usuƔrio |
|
| Bloqueia um usuƔrio (impede login) |
|
| Desbloqueia um usuƔrio (permite login) |
|
ā ļø ATENĆĆO: A operação
delete-userĆ© irreversĆvel! Use com muito cuidado.
Related MCP server: WorkOS MCP Server
š Instalação RĆ”pida
1. Clone o Repositório
git clone https://github.com/correaito/mcp_clerk.git
cd mcp_clerk2. Instale as DependĆŖncias
npm install3. Configure as VariƔveis de Ambiente
Opção A: Copie o arquivo de exemplo
cp env.example .env.localOpção B: Crie manualmente o arquivo .env.local
# Clerk API Keys
CLERK_SECRET_KEY=your_secret_key_here
NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY=your_publishable_key_here
# Server Configuration
PORT=50004. Obtenha suas Chaves do Clerk
Acesse Clerk Dashboard
Selecione seu projeto
VĆ” em API Keys
Copie:
Secret Key (comeƧa com
sk_live_ousk_test_)Publishable Key (comeƧa com
pk_live_oupk_test_)
5. Compile o Projeto
npm run buildāļø Configuração por Cliente MCP
šÆ Cursor AI (Recomendado)
Abra as configuraƧƵes do Cursor (
Ctrl/Cmd + ,)Procure por "MCP" na barra de pesquisa
Adicione a configuração:
{
"mcpServers": {
"Clerk": {
"command": "node",
"args": ["caminho/para/mcp_clerk/dist/server-stdio.js"],
"env": {
"CLERK_SECRET_KEY": "your_secret_key_here",
"NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY": "your_publishable_key_here"
}
}
}
}Exemplo com caminho completo:
{
"mcpServers": {
"Clerk": {
"command": "node",
"args": ["C:\\projetos\\mcp_clerk\\dist\\server-stdio.js"],
"env": {
"CLERK_SECRET_KEY": "your_secret_key_here",
"NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY": "your_publishable_key_here"
}
}
}
}Reinicie o Cursor
Teste: Digite
@Clerkno chat para ver as ferramentas disponĆveis
š¤ Claude Desktop
Abra o arquivo de configuração:
Windows:
%APPDATA%\Claude\claude_desktop_config.jsonmacOS:
~/Library/Application Support/Claude/claude_desktop_config.json
Adicione a configuração:
{
"mcpServers": {
"Clerk": {
"command": "node",
"args": ["caminho/para/mcp_clerk/dist/server-stdio.js"],
"env": {
"CLERK_SECRET_KEY": "your_secret_key_here",
"NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY": "your_publishable_key_here"
}
}
}
}Reinicie o Claude Desktop
š» VS Code
Instale a extensĆ£o MCP (se disponĆvel)
Configure via settings.json:
{
"mcp.servers": {
"Clerk": {
"command": "node",
"args": ["caminho/para/mcp_clerk/dist/server-stdio.js"],
"env": {
"CLERK_SECRET_KEY": "your_secret_key_here",
"NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY": "your_publishable_key_here"
}
}
}
}š Modo HTTP (Para Desenvolvimento)
Se preferir usar o servidor HTTP para testes:
1. Inicie o Servidor HTTP
npm start2. Teste com MCP Inspector
npx @modelcontextprotocol/inspectorConecte em:
http://localhost:5000/mcp
3. Teste com cURL
Health Check:
curl http://localhost:5000Listar UsuƔrios:
curl -X POST http://localhost:5000/mcp \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "list-users",
"arguments": {
"limit": 10,
"offset": 0
}
},
"id": 1
}'Bloquear UsuƔrio:
curl -X POST http://localhost:5000/mcp \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "lock-user",
"arguments": {
"userId": "user_xxxxxxxxxxxxx"
}
},
"id": 2
}'š Exemplos de Uso
No Cursor AI
@Clerk list-users limit=5
@Clerk lock-user userId=user_2abc123def456
@Clerk unlock-user userId=user_2abc123def456No Claude Desktop
Use a ferramenta Clerk para listar os últimos 10 usuÔrios cadastrados
Bloqueie o usuĆ”rio com ID user_2abc123def456š§ Scripts DisponĆveis
# Desenvolvimento
npm run dev # Servidor HTTP em modo dev
npm run dev:stdio # Servidor STDIO em modo dev
# Produção
npm run build # Compila o projeto
npm start # Servidor HTTP (porta 5000)
npm run start:stdio # Servidor STDIOš Estrutura do Projeto
mcp_clerk/
āāā src/
ā āāā server.ts # Servidor HTTP (porta 5000)
ā āāā server-stdio.ts # Servidor STDIO (para Cursor/VS Code)
ā āāā clerk-tools.ts # Implementação das ferramentas
āāā dist/ # Arquivos compilados
āāā env.example # Exemplo de configuração
āāā .env.local # Suas credenciais (NĆO commitado)
āāā .gitignore # Arquivos ignorados pelo Git
āāā package.json # DependĆŖncias e scripts
āāā tsconfig.json # Configuração TypeScript
āāā README.md # Este arquivoš”ļø SeguranƧa
ā Nenhuma chave hardcoded no código
ā Arquivo
.env.localprotegido pelo.gitignoreā VariĆ”veis de ambiente carregadas via
dotenvā ļø Nunca compartilhe suas credenciais do Clerk
ā ļø Operação
delete-userĆ© irreversĆvel - use com cuidado!
š Troubleshooting
Problema: "CLERK_SECRET_KEY não encontrada"
Solução: Verifique se o arquivo .env.local existe e contém a chave correta.
Problema: "Erro ao conectar com Clerk"
Solução: Verifique se suas chaves do Clerk estão corretas e ativas.
Problema: "Ferramentas não aparecem no Cursor"
Solução:
Verifique o caminho no arquivo de configuração
Reinicie o Cursor completamente
Verifique se o projeto foi compilado (
npm run build)
Problema: "Porta 5000 jĆ” estĆ” em uso"
Solução: Altere a porta no arquivo .env.local:
PORT=3001š¤ Contribuindo
Fork o projeto
Crie uma branch para sua feature (
git checkout -b feature/AmazingFeature)Commit suas mudanƧas (
git commit -m 'Add some AmazingFeature')Push para a branch (
git push origin feature/AmazingFeature)Abra um Pull Request
š LicenƧa
Este projeto estƔ sob a licenƧa MIT. Veja o arquivo LICENSE para mais detalhes.
š Agradecimentos
Clerk - Autenticação e gerenciamento de usuÔrios
Model Context Protocol - Protocolo para integração com IAs
Cursor AI - Editor de código com IA integrada
Feito com ā¤ļø para a comunidade de desenvolvedores
Available Tools
4 toolsdelete-userDeletar UsuƔrioA
Deleta permanentemente um usuĆ”rio do Clerk pelo ID. Esta ação Ć© irreversĆvel!
Inputs: userId (required). Returns: error, message, success
list-usersListar UsuƔriosB
Lista todos os usuÔrios cadastrados no Clerk com paginação
Inputs: limit, offset, orderBy. Returns: data, error, success
lock-userBloquear UsuƔrioA
Bloqueia um usuƔrio do Clerk, impedindo que ele faƧa login
Inputs: userId (required). Returns: error, message, success
unlock-userDesbloquear UsuƔrioB
Desbloqueia um usuƔrio do Clerk, permitindo que ele faƧa login novamente
Inputs: userId (required). Returns: error, message, success
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogā¦
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.
Related MCP Connectors
Clerk is an authentication and user management platform. Its MCP server lets coding agents set up and manage Clerk without leaving the editor. Agents can pull SDK snippets, quickstarts, and Clerkās agent skills. They can also create apps, update instance settings, and manage users and organizations. To go live, they can create a production instance and check its domain. Sign in with any Clerk account, including a free one. Secret keys are never returned in plain text.
Hosted MCP for Google Workspace, Atlassian and Notion: one OAuth, per-user accounts, write access.
Managed MCP gateway with OAuth, per-agent permissions, shared accounts and activity logs.
One MCP endpoint for your company's tools, with per-person sign-in, policy and audit.
Related MCP Servers
- AlicenseNot gradedqualityNot gradedmaintenanceEnables secure MCP server functionality with Clerk authentication and user-specific API key management. Provides Next.js documentation tools through protected endpoints with multiple authentication methods including OAuth 2.1 with PKCE.1-
- AlicenseNot gradedqualityDmaintenanceMCP server for WorkOS User Management API. Enables Claude to manage users, organizations, memberships, invitations, and sessions in WorkOS.17 npmMIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server for managing Okta users (CRUD operations) with full OAuth 2.1 compliance, enabling secure integration with Claude Desktop and other MCP clients.-
- AlicenseNot gradedqualityCmaintenanceEnables user creation and retrieval through MCP tools, resources, and prompts, with Google Gemini integration for natural language interaction.2,128 npmMIT