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

# Cursor

> Set up the Octave MCP server in Cursor to give your AI assistant access to your GTM knowledge base and agents.

## Setup

<Steps>
  <Step title="Get your config">
    From the [Octave dashboard](https://app.octavehq.com), click **Connect Via MCP** and select **Cursor**. Copy the MCP config.
  </Step>

  <Step title="Add to Cursor config">
    If you have no existing MCP servers, use this as your Cursor MCP config:

    ```json theme={null}
    {
      "mcpServers": {
        "octave-myWorkspace": {
          "command": "npx",
          "args": ["-y", "mcp-remote", "https://mcp.octavehq.com/mcp?ctx=YOUR_CONTEXT"]
        }
      }
    }
    ```

    If you already have MCP servers configured, add the `octave-myWorkspace` entry to your existing `mcpServers` object.

    <Note>
      Replace `YOUR_CONTEXT` with the value from your Octave dashboard. The full config is provided in the **Connect Via MCP** dialog.
    </Note>
  </Step>

  <Step title="Restart Cursor">
    Save the config and restart Cursor for the changes to take effect.
  </Step>

  <Step title="Add Octave routing rules (recommended)">
    Cursor doesn't have an "organization preferences" setting the way Claude does, so the equivalent is a **project rules file** that every team member picks up from the repo. With Octave connected alongside tools like HubSpot, Salesforce, Gong, or Granola, this gives Cursor's agent a hint to route GTM questions through Octave's synthesis layer instead of reaching for raw CRM data.

    Create `.cursor/rules/octave.mdc` (or append to your existing `AGENTS.md`) with the canonical Octave routing instructions:

    * [**Octave org instructions for Claude and other MCP clients**](https://github.com/octavehq/lfgtm/tree/main/docs/org-instructions) — pick `short.md` (\~1.7k chars) for most teams, or `long.md` (\~2.95k chars) when HubSpot/Salesforce/Gong/Granola/Fathom/Clay are also connected.

    Commit the file so every team member gets consistent routing.

    <Note>
      Individual users can also paste the same text into Cursor's **Rules for AI** in user settings. Rules files take effect immediately — no propagation delay.
    </Note>

    After the rules are in place, test with a new chat:

    > *"What's the status of my deal with Acme and what should I be doing next?"*

    Cursor's agent should call `get_deal_deep_dive` without the word "Octave" in the prompt. See the [full guide and test prompts](https://github.com/octavehq/lfgtm/tree/main/docs/org-instructions) for more.
  </Step>
</Steps>