Skip to main content

​
Setup

1

Get your config

From the Octave dashboard, click Connect Via MCP and select Cursor. Copy the MCP config.
2

Add to Cursor config

If you have no existing MCP servers, use this as your Cursor MCP config:
{
  "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.
Replace YOUR_CONTEXT with the value from your Octave dashboard. The full config is provided in the Connect Via MCP dialog.
3

Restart Cursor

Save the config and restart Cursor for the changes to take effect.
4

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:Commit the file so every team member gets consistent routing.
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.
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 for more.