Prerequisites
- A Cometly workspace and a Space you are a member of.
- Claude Desktop (latest — MCP support is in all current builds).
Add the server
In Claude Desktop, open Settings → Connectors (or Settings → MCP depending on your build). Click Add custom connector and fill in:Claude Desktop’s Save the file and restart Claude Desktop; the proxy opens the same Cometly authorization page in your browser.
claude_desktop_config.json only starts local (stdio) servers, so a remote URL can’t go in that file directly. Connectors are the supported way to add Cometly. On a plan without connectors, bridge it with the mcp-remote proxy instead:Authorize
The first time Claude tries to call a Cometly tool, it’ll open your browser to the Cometly authorization page. Log in, choose which Spaces to grant (all of yours or specific ones, with a default) and click Approve. You’ll see a green dot next toCometly 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
Claude Desktop doesn't see the server
Claude Desktop doesn't see the server
Make sure you fully quit and reopened Claude Desktop after editing
claude_desktop_config.json — it only reads the config at startup.OAuth window doesn't open
OAuth window doesn't open
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.
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.”
query_ad_metrics, list_events, list_contacts, get_contact…) automatically and refer to your custom fields by their configured labels in its response.