---
title: Connect a tool
description: Step-by-step setup for Claude Desktop, Claude Code, Cursor, Windsurf and any other MCP client.
---

<span class="vy-eyebrow">AI tools</span>

# Connect a tool

Everything you need is on the **AI tools** page in Vythos: the server address,
a key, and a ready-made snippet per tool. Copy from there rather than from
here — the address is shown to you rather than hard-coded, so it's always the
right one for your workspace.

::: tip Two ways to prove who you are
**Claude Desktop** signs in with your Vythos account (OAuth): no key to paste
or keep safe. **Everything else** uses a key sent as an
`Authorization: Bearer …` header. Either way, the connection carries the access
of the person it belongs to.
:::

## Claude Desktop

1. In Vythos, open **AI tools** and copy the server address.
2. In Claude Desktop: **Settings → Connectors → Add → Custom connector**.
3. Paste the address and choose **Connect**.
4. Your browser opens. Sign in to Vythos and approve.

No key needed. The connection appears on the AI tools page, where you can see
when it was last used.

## Claude Code

1. In Vythos, **AI tools → New key**, give it a label such as `Claude Code`,
   and copy both the key and the address.
2. Run the command shown on the page:

```bash
claude mcp add --transport http vythos <server-address> \
  --header "Authorization: Bearer <your-key>"
```

Use `--transport http`. The address ends in `/sse` for historical reasons, but
the server speaks Streamable HTTP — `--transport sse` fails to connect.

## Cursor

Create or edit `.cursor/mcp.json` in your project root:

```json
{
  "mcpServers": {
    "vythos": {
      "url": "<server-address>",
      "headers": { "Authorization": "Bearer <your-key>" }
    }
  }
}
```

## Windsurf

**Settings → MCP**, or edit `~/.codeium/windsurf/mcp_config.json` with the same
shape as Cursor's config above.

## Any other MCP client

Three values, and every MCP client needs them:

| | |
|---|---|
| **Server URL** | From the AI tools page |
| **Transport** | Streamable HTTP (POST) |
| **Auth header** | `Authorization: Bearer <your-key>` |

Most tools that advertise MCP support work with this. The ones listed on the
AI tools page are the ones we've connected ourselves.

## Check it worked

Ask your tool to do something that needs your rules:

> "Using Vythos, what are our standard payment terms?"

or, better, a real task:

> "Draft a project proposal for Acme for a three-month retainer. Get the rules
> from Vythos first, and check the draft before you show it to me."

You should see the tool call Vythos, quote figures that match your Playbook,
and — on the check — either report nothing found or name the rule a line
breaks.

## If it doesn't connect

| Symptom | Likely cause |
|---|---|
| The client can't reach the server | Check the address is exactly the one on the AI tools page, including `/sse` |
| Connects, then every call is rejected | The key is wrong, revoked, or missing its `Bearer ` prefix |
| Claude Code connects then drops | You used `--transport sse`. Use `--transport http` |
| Connects but returns nothing useful | Check the access of whoever owns the key. A category set to no access is never sent |
| The address keeps changing | Your workspace is pointed at a temporary development address. The AI tools page says when that's the case — ask us for the permanent one |

## Keys and hygiene

A key is shown **once**, when you create it. Keep it where you keep other
secrets, one key per tool, and revoke any you're unsure about — revoking takes
effect immediately. See [Keys](/ai-tools/keys).