Connect MetricDuck to your AI agent

Add the server with one command:

claude mcp add --transport http -s user metricduck https://mcp.metricduck.com/mcp

-s user registers it for every project; use -s project for just the current repo.

Then sign in (one command, or skip it — auth also triggers on first tool use):

claude mcp login metricduck

Your browser opens once for a quick Google/GitHub sign-in; after that it's automatic. On a remote or SSH session, add --no-browser to get a URL you can open anywhere and paste the redirect back.

Prefer a config file? Add this to .mcp.json:

{
  "mcpServers": {
    "metricduck": {
      "type": "http",
      "url": "https://mcp.metricduck.com/mcp"
    }
  }
}

Same as claude.ai — add it in the app: Settings → Connectors, click Add custom connector, paste the URL, then finish the one-time browser sign-in. The tools appear in any chat. (Every plan, including Free.)

On an older build, or prefer a config file? Bridge the remote server with mcp-remote in claude_desktop_config.json (Settings → Developer → Edit Config), then fully quit and relaunch:

{
  "mcpServers": {
    "metricduck": {
      "command": "npx",
      "args": ["mcp-remote", "https://mcp.metricduck.com/mcp"]
    }
  }
}

Works on every Claude plan — including Free (Free allows one custom connector, and MetricDuck is the one you want). Open Settings → Connectors, click Add custom connector, paste the URL below, then finish the one-time Google/GitHub sign-in. The tools appear in any chat afterward.

Menus move occasionally — see Anthropic's help center if a label has changed.

Add to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project) — or use Settings → MCP → Add new server:

{
  "mcpServers": {
    "metricduck": {
      "type": "http",
      "url": "https://mcp.metricduck.com/mcp"
    }
  }
}

ChatGPT connects to remote MCP servers as connectors (paid plans, with connectors / developer mode enabled). In Settings → Connectors, choose Add custom connector, paste the URL below, and complete the one-time Google/GitHub sign-in — the tools then show up in chat and the composer's connector menu.

The exact steps and plan availability change often — see OpenAI's remote-MCP docs. Building on the API? The Responses API accepts the same URL as a remote MCP tool.

Windsurf, VS Code, Zed, or your own agent — paste the URL into the client's MCP settings, or add the standard config. Transport is Streamable HTTP with automatic OAuth 2.1.

{
  "mcpServers": {
    "metricduck": {
      "type": "http",
      "url": "https://mcp.metricduck.com/mcp"
    }
  }
}

For automated pipelines with no browser, authenticate with an API key instead of OAuth:

{
  "mcpServers": {
    "metricduck": {
      "type": "http",
      "url": "https://mcp.metricduck.com/mcp",
      "headers": {
        "Authorization": "Bearer fda_your_api_key_here"
      }
    }
  }
}

Get your API key from the dashboard, then send it as Authorization: Bearer fda_… (no extra quotes or spaces).