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

# Connect Claude

> Add the Tanvik MCP connector to Claude and authorize it

Connecting takes a couple of minutes: add the Tanvik server as a custom connector in Claude, then authorize it with your Tanvik API key. Claude walks you through an OAuth sign-in — you paste your key once, and Claude stores the resulting authorization, not the key itself.

## Before you start

<Steps>
  <Step title="Confirm API access is on your plan">
    MCP access requires a Pro or Enterprise plan. Check **Settings → API Keys** in your [Tanvik dashboard](https://app.tanvik.io) — if you don't see the API Keys page, your plan doesn't include it yet.
  </Step>

  <Step title="Generate an API key">
    On **Settings → API Keys**, generate a key (`tvk_live_...`) if you don't already have one. You'll paste this during authorization. See [Authentication](/authentication) for details on keys.
  </Step>
</Steps>

## The MCP server URL

Add this as a custom connector in Claude:

```text theme={null}
https://xwialxkobwygraiddimj.supabase.co/functions/v1/mcp-client
```

## Add the connector in Claude

The exact menu labels vary slightly by Claude client and change over time, but the flow is the same:

<Steps>
  <Step title="Open connector settings">
    In Claude, go to **Settings → Connectors** (on some clients this is under a "Custom connectors" or "Add integration" option).
  </Step>

  <Step title="Add a custom connector">
    Choose to add a custom / remote MCP server and paste the server URL above. Give it a recognizable name like **Tanvik**.
  </Step>

  <Step title="Authorize">
    Claude opens the Tanvik authorization page. Paste your `tvk_...` API key and click **Authorize**. This completes an OAuth 2.1 handshake — Claude receives an authorization token, and your raw key isn't stored inside Claude.
  </Step>

  <Step title="Confirm the connection">
    Back in Claude, the connector should show as connected, and Tanvik's tools become available to the assistant. You can also verify from **Settings → API Keys** in your Tanvik dashboard, which has a "Test connection" button.
  </Step>
</Steps>

<Note>
  Custom connector support depends on your Claude plan. If you don't see an option to add a custom or remote MCP server, check that your Claude plan supports connectors.
</Note>

## What happens during authorization

For the curious, the connection uses standard OAuth 2.1 with PKCE:

1. Claude registers itself with Tanvik's authorization server (dynamic client registration) and redirects you to the Tanvik authorization page.
2. You paste your `tvk_...` key to prove you own the workspace.
3. Tanvik issues a short-lived authorization code, which Claude exchanges for a token.
4. Claude uses that token on every request to the MCP server; each request is still resolved back to your specific client account server-side.

You never expose your key to other users, and you can revoke access at any time by rotating the API key from **Settings → API Keys** — rotating immediately invalidates the old connection.

## After connecting

By default Claude can only **read** your workspace data plus send WhatsApp session messages. To grant or restrict specific actions, head to [Permissions](/mcp/permissions). To see the full list of what's available, see [Available tools](/mcp/tools).

<Warning>
  Treat a connected Claude like anyone holding your API key: it can see your workspace data and perform whatever actions you've enabled. Only connect from Claude accounts you control, and review your enabled action tools on the Permissions page.
</Warning>