# Connect Brev to Claude, ChatGPT and Cursor

Add Brev to the AI assistant you already use, so it can read and update your goals, check-ins, meetings and actions.

Bring your goals, check-ins and meetings into the AI assistant you already use. Brev connects over MCP, the standard Claude, ChatGPT, Cursor and other assistants use to reach outside tools.

## What you can do with it

Once connected, ask your assistant to work with Brev as you. For example:

- Prepare for a leadership review: pull a team's goals, their progress and the latest check-ins.
- Draft check-ins from what was said in a meeting.
- Find goals that are at risk or behind, and see what was last said about them.
- See how child goals roll up into the goal above them.
- List and update your actions.

The assistant sees only what your Brev account can see, and every change it makes is made as you.

## Connect your assistant

Each assistant needs the Brev MCP server URL, which you can also copy from [Settings → MCP](https://help.brev.io/settings-ai-automation/#mcp). Clients that read a config file take the .mcp.json form instead:

**Server URL**

```
https://mcp.brev.io/mcp
```

**.mcp.json**

```json
{
  "mcpServers": {
    "brev": {
      "type": "http",
      "url": "https://mcp.brev.io/mcp"
    }
  }
}
```

**Claude Code**

```bash
claude mcp add --transport http --scope user brev https://mcp.brev.io/mcp
```

![Settings \> MCP with the External MCP clients switch, the Brev MCP server URL to copy, and the .mcp.json snippet open.](https://help.brev.io/doc-assets/screenshots/settings-mcp.png)

*The server URL and the .mcp.json snippet in Settings → MCP.*

Assistants change their menus often. If a step below doesn't match what you see, look for "custom connector" or "MCP server" in your assistant's settings.

### Claude (web, desktop and Cowork)

Claude on the web, Claude Desktop and Cowork share one set of connectors, so you add Brev once:

1. In Claude, go to **Customize → Connectors** (**Plugins** in newer versions).
2. Click **Add**, then **Add custom connector**.
3. Name it Brev, paste the server URL and click **Continue**.
4. Keep the detected sign-in settings and click **Add**.
5. Sign in to Brev and click **Approve** on the [sign-in screen](https://help.brev.io/mcp-authorize/#what-the-page-shows-during-real-flow). If your MCP access is off, the button reads **Enable MCP & Approve** and turns it back on.

On a Claude Team or Enterprise plan, an owner adds the connector once in **Organization settings → Connectors**. Everyone else finds it under **Customize → Connectors** (or **Plugins**), clicks **Connect** and approves Brev.

### ChatGPT

Adding a custom MCP server depends on your ChatGPT plan and workspace settings. On Business, only admins and owners can add one; on Enterprise and Edu, admins can also allow members to. If you don't see Add custom MCP server, ask an admin to add Brev for you. On some plans ChatGPT can only read from Brev, not make updates. To add Brev:

1. In ChatGPT, open **Plugins** and click the plus button.
2. Choose **Add custom MCP server**.
3. Name it Brev and paste the server URL as the **Server URL**.
4. Set authentication to **OAuth**.
5. Accept the warning and click **Create as a plugin**.
6. Install the plugin, then use it in a chat.
7. Sign in to Brev and click **Approve** on the [sign-in screen](https://help.brev.io/mcp-authorize/#what-the-page-shows-during-real-flow). If your MCP access is off, the button reads **Enable MCP & Approve** and turns it back on.

### Cursor

1. Open `~/.cursor/mcp.json` for every project, or `.cursor/mcp.json` for one project.
2. Add the .mcp.json snippet above. If the file already lists servers, add the brev entry next to them.
3. Save the file and restart Cursor.
4. Sign in to Brev and click **Approve** on the [sign-in screen](https://help.brev.io/mcp-authorize/#what-the-page-shows-during-real-flow). If your MCP access is off, the button reads **Enable MCP & Approve** and turns it back on.

### Claude Code and other file-based clients

1. In Claude Code, run the Claude Code command above. It adds Brev for all your projects; drop --scope user to add it to the current project only. In another client, add the .mcp.json snippet to the file it reads its MCP servers from.
2. In Claude Code, run `/mcp`, pick brev and follow the sign-in steps in your browser.
3. Sign in to Brev and click **Approve** on the [sign-in screen](https://help.brev.io/mcp-authorize/#what-the-page-shows-during-real-flow). If your MCP access is off, the button reads **Enable MCP & Approve** and turns it back on.

> **Warning: Sign in, never paste an API key**
>
> A Brev API key in a shared connector header makes everyone act as the key's owner, so each person signs in instead.

## Check it works

1. Ask your assistant something only Brev knows, such as "What are my goals this quarter?"
2. Look for Brev's tools in your assistant's tool or connector list. Most of their names start with brev\_.

## Turn off or disconnect

- To disconnect one assistant, remove the Brev connector in that assistant's own settings. Brev doesn't list your connected clients. See [Disconnecting a client](https://help.brev.io/mcp-authorize/#revoking).
- To cut off every assistant you connected at once, turn off **External MCP clients** in [Settings → MCP](https://help.brev.io/settings-ai-automation/#mcp). Turning it back on reconnects them.

## Troubleshooting

### My assistant says it can't reach the server.

Check that **External MCP clients** is on in [Settings → MCP](https://help.brev.io/settings-ai-automation/#mcp). With it off, every client you connected stops working, and most report it as being unable to reach the server.

### The sign-in screen says Authorization expired.

The request timed out or its link was changed. Start the connection again from your assistant.

### The sign-in screen shows Unrecognized permission.

Your assistant asked for a permission this version of Brev can't describe, so Approve stays disabled. Cancel, then start the connection again from your assistant. Contact support if it keeps happening.

### Clicking Approve or Cancel says my Brev session ended.

You were signed out while the screen was open. Sign in to Brev again, then start the connection again from your assistant.