RELATED 01
CodeQL Development MCP Server
OFFICIAL SERVERWrite, test, run and profile CodeQL queries from an AI assistant through the local CodeQL CLI
39GitHub stars
838/wknpm downloads
51popularity score
Clerk MCP Server
Clerk's hosted server for managing Clerk applications, users and domains and fetching SDK code snippets
Official · Clerk Remote (hosted) · Streamable HTTP SecurityDeveloper tools
69 popularity score ★ 55 ↓ 103k/wk
Connect your client
Remote (hosted)
Add in one click
Opens the app, which asks before it adds the server.
Or add it by command or config
Claude Codeterminal; then /mcp, select clerk, Authenticate
claude mcp add clerk --transport http https://mcp.clerk.com/mcpClaude Desktopclaude_desktop_config.json (Claude Desktop); on Claude.ai add a custom connector with the URL
{
"mcpServers": {
"clerk": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.clerk.com/mcp"]
}
}
}Codexterminal
codex mcp add clerk --url https://mcp.clerk.com/mcpCursorCursor MCP configuration JSON
{
"mcpServers": {
"clerk": {
"url": "https://mcp.clerk.com/mcp"
}
}
}VS CodeMCP: Add Server, then enter https://mcp.clerk.com/mcp
{
"servers": {
"clerk": {
"type": "http",
"url": "https://mcp.clerk.com/mcp"
}
}
}windsurfWindsurf MCP config JSON
{
"mcpServers": {
"clerk": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.clerk.com/mcp"]
}
}
}zedZed settings.json
{
"context_servers": {
"clerk": {
"command": {
"path": "npx",
"args": ["-y", "mcp-remote", "https://mcp.clerk.com/mcp"]
}
}
}
}fxterminal; then fx mcp auth clerk
fx mcp add --transport http clerk https://mcp.clerk.com/mcpWhat it does
Clerk runs this server itself at https://mcp.clerk.com/mcp. You sign in with the account you use for the Clerk Dashboard and pick one workspace. From then on an assistant can list, inspect and create applications in it. It can also read instance configuration and change it, with a dry run to preview the change first. Users can be listed and created, and for a domain it shows the DNS records Clerk wants and can ask for a fresh check. When you are ready to launch, it turns a development instance into a production one and stores the OAuth provider credentials production needs.
If you run your own MCP server with Clerk, a newer tool, list_application_feedback, reads the feedback that agents reported through that server, filtered by kind, impact or user. Two snippet tools hand back Clerk code for one feature or for a setup bundle such as b2b-saas or organizations.
The docs now list 21 tools. The official MCP registry entry (version 0.1.0, published 2026-03-09) still calls it a docs, snippets and quickstart server, which is older than the account tools. Its sign-in metadata names https://clerk.clerk.com as the authorization server and lists eight scopes: the seven in the docs plus organizations:read, which the docs do not mention.
There is nothing to install. The clerk npm package and the github.com/clerk/cli repository hold Clerk's general command-line tool. Its `clerk mcp` command manages the connection to this server for editors, while commands such as `clerk feedback` and `clerk security` belong to the CLI and are not tools of the server.
What it needs
| Clerk | Any tool call needs a Clerk account and a workspace in it; your workspace Role bounds what the tools may do |
|---|---|
| Also |
|
Codex needs `codex mcp login clerk` to sign in again later. On Claude Team and Enterprise plans an Owner must add the connector in Organization settings before members can use it.
Limits
- Limit Streamable HTTP only. The docs say there is no SSE endpoint.
- Not covered Tools never return instances' secret keys and redact sensitive values in configuration, so take keys from the Dashboard or `clerk env pull`.
- Limit create_production_instance cannot be undone and requires confirm: true.
- Not covered User tools list and create users. The docs name no tool to update or delete a user.
- Limit Switching workspace means signing out and connecting again. With mcp-remote that is deleting ~/.mcp-auth, which signs out of every server it bridges.
- Limit Every tool, the snippet tools included, needs a signed-in Clerk account.
Streamable HTTP only; there is no SSE endpoint. Tools never return instances' secret keys, and sensitive values are redacted when configuration is read, so keys must come from the Dashboard or `clerk env pull`. Creating a production instance cannot be undone and that tool requires confirm: true. User tools list and create users only; the docs name no update or delete tool. Switching workspace means signing out and connecting again (with mcp-remote, deleting ~/.mcp-auth, which signs out of every server it bridges).
Who it suits
Developers already building on Clerk who want an assistant to set up applications, inspect or change instance settings, prepare production domains and OAuth credentials, or pull official code snippets without leaving the editor. Because it acts as you and can change configuration and create users and production instances, use a client that asks before running tools marked as changing things. If you only want SDK snippets, note that every tool, snippets included, still requires signing in to a Clerk account.
Tools 20
whoami- Shows the signed-in user, chosen workspace and granted permissions
list_applications- Lists the applications in the workspace, with publishable keys
get_application- Returns one application and its instances
create_application- Creates a new application
get_instance_config- Reads an instance's configuration, with sensitive values redacted
get_instance_config_schema- Returns the schema of instance configuration
patch_instance_config- Updates parts of an instance's configuration, with optional dry run
put_instance_config- Replaces an instance's configuration, with optional dry run
list_users- Finds users in an instance using filters
create_user- Adds a user to an instance
list_domains- Lists the domains of an application
get_domain_status- Shows a domain's required DNS records and verification state
check_domain_dns- Asks Clerk to run a fresh DNS check for a domain
get_deploy_oauth_providers- Shows which OAuth providers need credentials before going to production
create_production_instance- Creates a production instance from development; irreversible, needs confirm: true
set_oauth_provider_credentials- Stores production OAuth client credentials for a provider
submit_feedback- Sends a problem report to Clerk, including user and workspace IDs
get_more_tools- Tells Clerk about a task no existing tool covers
clerk_sdk_snippet- Returns a code snippet for a Clerk feature or a bundle for a common setup
list_clerk_sdk_snippets- Lists available snippets and bundles, optionally by tag