> ## 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.

# Claude Desktop

> Connect Octave to Claude Desktop using a custom connector or remote MCP config

## Option 1: Custom Connector (Recommended)

The simplest way to connect Octave to Claude Desktop.

1. Navigate to your [Octave dashboard](https://app.octavehq.com) and click **Connect Via MCP**

2. Copy the custom connector link

3. In Claude Desktop, go to **Settings > Connectors > Add custom connector**

4. Paste the connection URL and authenticate

## Option 2: Remote MCP Config

For organizations that restrict custom connectors, you can add Octave as a remote MCP server.

<Steps>
  <Step title="Get your config">
    From the Octave dashboard, click **Connect Via MCP** and copy the remote config.
  </Step>

  <Step title="Edit your Claude Desktop config">
    In Claude Desktop, go to **Settings > Developer > Edit Config** to open your `claude_desktop_config.json`.
  </Step>

  <Step title="Add the Octave MCP server">
    If you have no existing MCP servers, replace the file contents with:

    ```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 URL is provided in the **Connect Via MCP** dialog.
    </Note>
  </Step>

  <Step title="Restart Claude Desktop">
    Save the config file and restart Claude Desktop for the changes to take effect.
  </Step>
</Steps>

<Warning>
  You will need [Node.js](https://nodejs.org/en/download/) installed for the remote MCP config option.
</Warning>

## Set Claude org preferences (recommended)

Applies to both install options above. With Octave connected alongside tools like HubSpot, Salesforce, Gong, or Granola, Claude needs a hint to route GTM questions through Octave's synthesis layer instead of reaching for raw CRM or call-transcript data. Set this once at the org level and every rep gets it automatically — no need to prefix prompts with "Using Octave, …".

<Steps>
  <Step title="Copy the canonical instructions">
    Open the [**Octave org instructions for Claude**](https://github.com/octavehq/lfgtm/tree/main/docs/org-instructions) and pick a version:

    * **`short.md`** (\~1,700 chars) — leaves headroom to layer workspace-specific rules on top (custom ICPs, named motions, vertical terminology).
    * **`long.md`** (\~2,950 chars) — recommended when HubSpot, Salesforce, Gong, Granola, Fathom, or Clay are also connected. Adds explicit demotion of raw-data tools and LFGTM plugin routing.

    Click into the file, view **Raw** on GitHub, and copy the full contents.
  </Step>

  <Step title="Paste into Claude org preferences">
    In Claude Desktop (or [claude.ai](https://claude.ai)), go to **Settings → Organization preferences** and paste. Save.

    <Note>
      Organization preferences are **admin-only** (Teams / Enterprise) and can take **up to 1 hour** to propagate across Claude products. Individual Pro users can paste the same text into **Settings → Personal preferences** instead.
    </Note>
  </Step>

  <Step title="Test the routing">
    After propagation, start a new conversation and run this prompt **without** mentioning Octave:

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

    Claude should call `get_deal_deep_dive` directly. If it still reaches for a CRM tool first, tighten the *Routing vs. other connectors* section of your org preferences. See the [full install and test guide](https://github.com/octavehq/lfgtm/tree/main/docs/org-instructions) for more prompts, customization tips, and troubleshooting.
  </Step>
</Steps>