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

# Cursor

> Connect the Brivvy MCP Server with Cursor to access brand voice and templates during AI-assisted coding and content generation.

Cursor supports remote MCP servers over Streamable HTTP with built-in OAuth authentication. You can add Brivvy by dropping a single entry into your MCP configuration file. Once connected, Cursor's Agent can call Brivvy tools to retrieve brand voice rules and template instructions directly in your coding workflow. This is useful for generating on-brand README files, API documentation, code comments and user-facing text without leaving the editor.

## Before you start

* Cursor installed (v1.0 or later).
* A Brivvy account on a plan that includes MCP access.

## Steps

1. Open Cursor and click the gear icon in the top right to open **Settings**. In the left sidebar, click **Tools & Integrations**.

2. Under **MCP Tools**, click **Add Custom MCP**. Cursor opens the `mcp.json` configuration file in the editor.

3. Paste the following configuration. If an `mcpServers` block already exists, add `"brivvy"` as an additional entry rather than creating a second block.

   ```json theme={null}
   {
     "mcpServers": {
       "brivvy": {
         "url": "https://mcp.brivvy.io"
       }
     }
   }
   ```

4. Save the file. Brivvy will appear in your MCP Tools list with a **Needs login** status.

5. Click **Needs login** next to Brivvy. Cursor opens a browser window where you can sign in to Brivvy and authorize the connection. After you approve, Cursor stores the OAuth credentials locally.

6. Back in Cursor, confirm the Brivvy server shows a green **Connected** status under MCP Tools. You can expand the entry to see the available tools: `list_voices`, `get_voice`, `list_templates` and `get_template`.

<Tip>You can also place the configuration at `.cursor/mcp.json` inside a specific project directory to scope the connection to that project only. The global configuration at `~/.cursor/mcp.json` applies across all projects.</Tip>

## How to know it worked

Open a new Agent conversation in Cursor and send a prompt that requires brand voice context, for example: "Using Brivvy, get the brand voice rules and write a two-sentence product update." The Agent will call the appropriate Brivvy tool and return a response shaped by your brand voice rules rather than a generic output.