Clerk FAQs

Question 1

How does Clerk MCP integrate with AI assistants?

Accepted Answer

It integrates seamlessly via the Model Context Protocol. Once configured, you can use your AI assistant (e.g., Claude, Cursor, VS Code Copilot, Windsurf) to issue commands in plain language, performing actions like listing organizations, creating users, updating roles, and managing invitations directly.

Question 2

What is the Clerk MCP Server?

Accepted Answer

The Clerk MCP Server is a Model Context Protocol (MCP) server designed to enable direct management and querying of your Clerk organizations, users, members, roles, and invitations through various AI assistants like Claude, Cursor, and VS Code Copilot, using natural language prompts.

Question 3

What Clerk entities can I manage using this tool?

Accepted Answer

You gain comprehensive create, read, update, and delete (CRUD) capabilities for Clerk Organizations, Members (including roles and metadata), Invitations, and Users (including profiles and metadata). This allows for full administrative control via AI.

Question 4

Is Clerk MCP secure, and how is my Clerk Secret Key handled?

Accepted Answer

Security is paramount. In Hosted Mode, your Clerk Secret Key should be stored securely as an environment variable (e.g., `CLERK_SECRET_KEY`) and never committed to Git. In Public Mode, the server itself stores no keys; clients provide their key securely via an `X-Clerk-Secret-Key` HTTP header with each request, creating a fresh Clerk client for every interaction.

Question 5

What are the two operational modes of Clerk MCP?

Accepted Answer

Clerk MCP supports 'Hosted Mode,' where the server stores a single Clerk Secret Key for all requests (ideal for personal or internal use), and 'Public Mode,' where clients provide their own key per-request via HTTP headers, suitable for multi-tenant or shared deployments without storing keys on the server.

Clerk

Clerk

Acerca de

Características Principales

Casos de Uso

Acerca de

Características Principales

Casos de Uso