> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sazabi.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Clerk

> Give the Sazabi agent tools to work with your Clerk applications, instance configuration, users, and domains, and to pull Clerk SDK snippets.

[All Clerk integration capabilities](https://docs.sazabi.com/catalogs/integrations/clerk)

## About

Clerk is an MCP connector that gives the Sazabi agent tools from Clerk's hosted MCP server at `https://mcp.clerk.com/mcp`. You sign in with the Clerk account you use for the Clerk Dashboard and pick a workspace. Sazabi then acts as you in that workspace, limited to what your workspace Role and the permissions you grant allow. Clerk never returns instance secret keys through the MCP server.

**What the agent can do:**

* List and inspect applications and instance configuration
* Find and create users in an instance
* Check the DNS records and verification status of production domains
* Retrieve Clerk SDK snippets and setup bundles

## Prerequisites

* A Clerk account with access to the workspace you want to connect

## Set up in the dashboard

Configure connectors in the dashboard under [**Settings > MCP connectors**](https://app.sazabi.com/settings/mcp-connectors).

**Step 1**

### Open the connector

Find Clerk in [**Settings > MCP connectors**](https://app.sazabi.com/settings/mcp-connectors).

**Step 2**

### Authorize

Optionally narrow the permissions, then start the connection. Sazabi redirects you to Clerk, where you sign in, pick the workspace, and approve the permissions, then back.

## Set up with the CLI

You can also connect Clerk with the [Sazabi CLI](https://docs.sazabi.com/reference/cli.md) (installed and authenticated — see [`sazabi mcp-connectors` reference](https://docs.sazabi.com/reference/cli/mcp-connectors)).

Clerk authenticates over OAuth, so the CLI opens a browser to complete authorization:

```bash theme={"system"}
sazabi mcp-connectors connect clerk
```

Add `--read-only` to restrict the connector to read-only tools, or `--project-id <project>` to target a specific project. In `--json` mode the command prints an authorization URL and exits immediately. Open the URL to complete authorization, then check the result separately with `sazabi mcp-connectors list`.

## Verify

Open the connector's connection page under [**Settings > MCP connectors**](https://app.sazabi.com/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. If no tools appear, confirm the connection is authorized.

## Troubleshooting

**Unauthorized or no tools discovered** — Disconnect and reconnect from [**Settings > MCP connectors**](https://app.sazabi.com/settings/mcp-connectors) to restart the Clerk sign-in.

**A tool returns a permission error** — Your workspace Role doesn't allow the request, or the connection is missing a permission the tool needs. Reconnect and grant the permission, or ask a workspace Owner or Admin to check your Role.

**Wrong workspace** — Disconnect, then reconnect and pick a different workspace during sign-in.

## Further reading

> [card] [Agent tools](https://docs.sazabi.com/guides/investigate/agent-tools.md)
>
> How the agent uses connector tools.

> [card] [MCP connectors](https://docs.sazabi.com/catalogs/mcp-connectors.md)
>
> Browse the connector catalog.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.