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

> Add Goosy Bear to Claude Code with a project-level .mcp.json your whole repository picks up.

Claude Code reads a `.mcp.json` in your project root, so everyone working in
that repository gets Goosy Bear without setting it up again.

<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">
    These clients read the value from the environment of the process that
    launches them, so it belongs in the profile that starts your terminal
    (`~/.zshrc` or `~/.bashrc`) rather than in a project `.env` file. Open a new
    terminal afterwards so the variable is set.

    ```bash theme={null}
    export GOOSY_API_KEY="<paste the key you copied when you minted it>"
    ```
  </Step>

  <Step title="Add the server">
    Create or edit `.mcp.json` in your project root:

    ```json theme={null}
    {
      "mcpServers": {
        "goosy": {
          "type": "http",
          "url": "https://app.goosybear.ai/api/mcp/mcp",
          "headers": {
            "Authorization": "Bearer ${GOOSY_API_KEY}"
          }
        }
      }
    }
    ```
  </Step>

  <Step title="Check it">
    Start Claude Code in that project and ask it what Goosy tools it can see.
  </Step>
</Steps>

<Note>
  This file is safe to commit: it names your key as `${GOOSY_API_KEY}` rather
  than containing it. Claude Code fails the config parse when the variable is
  unset, so a missing key is loud rather than a silent anonymous connection.
</Note>