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

# Connect Claude Desktop

> Add Goosy Bear to the Claude desktop app through the standard remote-server bridge.

Claude Desktop reaches remote servers through a small bridge that runs on your
machine. You need Node.js installed; your key stays in your shell environment
rather than in the file.

<Steps>
  <Step title="Create a key">
    On **Settings → API & MCP**, create a key and copy it — it is shown once.
  </Step>

  <Step title="Put the key in your shell profile">
    ```bash theme={null}
    export GOOSY_API_KEY="<paste the key you copied when you minted it>"
    ```
  </Step>

  <Step title="Open the config file">
    In Claude Desktop, go to the Claude menu → Settings → Developer → Edit
    Config. It opens `claude_desktop_config.json`.
  </Step>

  <Step title="Add the server">
    ```json theme={null}
    {
      "mcpServers": {
        "goosy": {
          "command": "npx",
          "args": [
            "-y",
            "mcp-remote",
            "https://app.goosybear.ai/api/mcp/mcp",
            "--header",
            "Authorization:Bearer ${GOOSY_API_KEY}"
          ],
          "env": {
            "GOOSY_API_KEY": "${GOOSY_API_KEY}"
          }
        }
      }
    }
    ```

    Save, then fully quit and reopen Claude Desktop.
  </Step>

  <Step title="Check it">
    Open the connectors menu in the message box and confirm **goosy** is listed.
  </Step>
</Steps>

<Note>
  Claude Desktop's "Add custom connector" dialog takes a URL and then runs the
  server's own sign-in flow — it has no field for an API key, and Goosy Bear's
  programmatic surface authenticates with a key rather than a sign-in at this
  stage. The bridge above is what carries your key.
</Note>