Setup
These instructions work with VS Code, Zed, Windsurf, and other MCP-compatible editors. Follow your editor’s specific process for adding MCP servers.Get your config
From the Octave dashboard, click Connect Via MCP and copy the MCP config.
Add to your editor's MCP config
If you have no existing MCP servers, use this as your MCP configuration: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.Add Octave routing rules (recommended)
These editors don’t have an “organization preferences” setting the way Claude does, so the equivalent is a project rules or instructions file that every team member picks up from the repo. With Octave connected alongside tools like HubSpot, Salesforce, Gong, or Granola, this gives the agent a hint to route GTM questions through Octave’s synthesis layer instead of reaching for raw CRM data.Paste the canonical Octave routing instructions into whichever file your editor reads:
Source: Octave org instructions for Claude and other MCP clients — pick
| Editor | File |
|---|---|
| VS Code (Copilot / Claude Dev) | .github/copilot-instructions.md or AGENTS.md |
| Zed | .zed/AGENT.md or AGENTS.md |
| Windsurf | .windsurfrules |
| Other MCP-compatible editors | Check your editor’s docs for its rules / memory file convention; AGENTS.md is the emerging cross-editor default |
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. 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?”The agent should call
get_deal_deep_dive without the word “Octave” in the prompt. See the full guide and test prompts for more.