Clerk

About

Clerk is an MCP connector that gives the Sazabi agent tools to search Clerk's public documentation and SDK implementation snippets. Clerk's official MCP server (https://mcp.clerk.com/mcp) is a read-only Streamable HTTP endpoint that serves public Clerk documentation and SDK code patterns. It exposes two tools: list_clerk_sdk_snippets to list available SDK snippets and implementation bundles, and clerk_sdk_snippet to retrieve a specific SDK code pattern. No authentication is required because the server only serves public documentation. It does not read or manage users, organizations, sessions, or secrets in a Clerk instance.

What the agent can do:

• Search Clerk's documentation and SDK guides semantically
• Retrieve up-to-date SDK implementation snippets and bundles
• Ground agent coding help in current Clerk auth patterns

Prerequisites

• None. The Clerk MCP server is public and requires no authentication.

Set up in the dashboard

Configure connectors in the dashboard under Settings > MCP connectors.

Set up with the CLI

Clerk's hosted MCP server requires no credentials, and sazabi mcp-connectors connect only supports OAuth providers — so add this connector from the dashboard first (above). Once it's connected, the Sazabi CLI can inspect and manage it (installed and authenticated — see sazabi mcp-connectors reference):

sazabi mcp-connectors list
sazabi mcp-connectors details <connection-id>

Find the connection ID with sazabi mcp-connectors list.

Verify

Open the connector's connection page under Settings > MCP connectors and confirm Sazabi lists the tools it discovered. Then, in a thread, ask the agent to use one of those tools and confirm it runs.

Troubleshooting

No tools discovered — Disconnect and reconnect from Settings > MCP connectors; the Clerk MCP server is public and needs no credentials, so a reconnect should resolve any discovery issue.

Connection shows needs attention — Disconnect and reconnect from Settings > MCP connectors.

Further reading