Connect Cursor or VS Code

Both editors keep your key out of the config file, but they do it differently and the shapes are not interchangeable. Use the one for your editor.

Cursor

Create a key and put it in your shell profile

Create the key on Settings → API & MCP and copy it — it is shown once.

export GOOSY_API_KEY="<paste the key you copied when you minted it>"

Add the server

Add this to ~/.cursor/mcp.json, or to .cursor/mcp.json in your project:

{
  "mcpServers": {
    "goosy": {
      "url": "https://app.goosybear.ai/api/mcp/mcp",
      "headers": {
        "Authorization": "Bearer ${env:GOOSY_API_KEY}"
      }
    }
  }
}

Reload the window, then open the MCP panel and confirm goosy is connected.

VS Code

VS Code prompts you for the key the first time and keeps it in its own secret storage, so no shell variable is needed. Add this to .vscode/mcp.json:

{
  "inputs": [
    {
      "type": "promptString",
      "id": "goosy-api-key",
      "description": "Goosy API key",
      "password": true
    }
  ],
  "servers": {
    "goosy": {
      "type": "http",
      "url": "https://app.goosybear.ai/api/mcp/mcp",
      "headers": {
        "Authorization": "Bearer ${input:goosy-api-key}"
      }
    }
  }
}

VS Code uses servers, and Cursor uses mcpServers. Cursor also needs the env: prefix on the variable reference. Swapping either one produces a file that parses and then fails to authenticate with nothing to show for it.

Both files stay safe to commit — neither contains the key itself.

Get started

Build with the API

Connect an assistant

API reference

Your CRM

Connect Cursor or VS Code

Cursor

VS Code

​Cursor

​VS Code

Cursor

VS Code