Clerk MCP

Clerk is a user management and authentication service that handles sign-in, sessions, organizations, and roles for an application. Its agent toolkit includes a Model Context Protocol entry point, which turns a subset of Clerk's backend API into tools an assistant can call. Run locally with a Clerk secret key, the server lets an agent inspect and administer the users and organizations of a Clerk instance rather than requiring someone to click through the dashboard. The exposed surface covers user records and their profile data, organizations along with their memberships and role assignments, and invitations. Tools are grouped into categories, and the server accepts a flag that restricts which categories load, so a deployment can be limited to a single domain such as organizations. Because it authenticates with a backend secret rather than an end user session, it belongs in trusted developer and operator contexts, not embedded in an agent that untrusted users talk to. Clerk also documents the other direction: using its OAuth server so that an MCP server you build yourself can authenticate the agents connecting to it, with guides for common server frameworks. That matters for anyone exposing their own product as tools, since MCP clients need a standard way to obtain and present authorization. Together the two pieces cover administering Clerk from an agent and putting Clerk in front of an agent-facing endpoint of your own.