Skip to main content
Claude web also works out of the box. If you prefer to use Cometly in the claude.ai web interface or mobile app, add the connector there instead — claude.ai and claude.com work out of the box. The steps are the same: paste the MCP endpoint URL and approve access on first use.

​
Prerequisites

  • A Cometly workspace and a Space you have Use Public API permission in.
  • Claude Desktop (latest — MCP support is in all current builds).
  • Your numeric Space ID — copy it from the ID row at the bottom of the dashboard sidebar, or from Space Settings → Space Details. See Finding your Space ID for step-by-step instructions.

​
Add the server

In Claude Desktop, open Settings → Connectors (or Settings → MCP depending on your build). Click Add custom connector and fill in:
FieldValue
NameCometly
URLhttps://app.cometly.com/mcp/{your-space-id}/public-api
Click Save. Or, if you’d rather edit the config file directly, open the Claude Desktop config:
  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
…and add: 
{
  "mcpServers": {
    "cometly": {
      "type": "http",
      "url": "https://app.cometly.com/mcp/42/public-api"
    }
  }
}
Replace 42 with your Space ID, save, and restart Claude Desktop.

​
Authorize

The first time Claude tries to call a Cometly tool, it’ll open your browser to the Cometly authorization page. Log in, confirm the Space, and click Approve. You’ll see a green dot next to Cometly in the connectors list once the handshake succeeds.

​
Verify

Open a new chat and ask:
Using the Cometly connector, list my conversion events from the last 7 days.
You should see Claude call the list_events tool and respond with real data. The first response is sometimes a little slower (cold connection); subsequent calls are fast.

​
Troubleshooting

Make sure you fully quit and reopened Claude Desktop after editing claude_desktop_config.json — it only reads the config at startup.
Older Claude Desktop builds occasionally swallow the OAuth URL. Re-add the connector via the Connectors UI instead of the config file; the UI flow is more reliable.
Your access token is missing or wrong. Remove the connector, restart Claude Desktop, and add it back — you’ll re-walk the OAuth flow.

​
What you can ask

  • “Show me purchases attributed to Facebook over the last 14 days with linear attribution.”
  • “Compare CPA between Google and Meta this month vs last month.”
  • “Find every contact created this week where Customer Plan is Premium.”
  • “Pull a full journey for contact 8231 and summarize it.”
Claude will pick the right tool (query_ad_metrics, list_events, list_contacts, get_contact…) automatically and refer to your custom fields by their configured labels in its response.