AI Clients

Cursor

Cursor supports MCP servers through a JSON config file. Add MCP Ads there and your ad accounts are available alongside your codebase.

Add the server

Cursor reads MCP servers from a config file. Create it if it does not exist, then restart Cursor so it picks up the change.

~/.cursor/mcp.json

{
  "mcpServers": {
    "mcp-ads": {
      "url": "https://mcp-ads.com/mcp-slim"
    }
  }
}

Note

This is a remote server entry, so it takes a url rather than a command. There is no package to install and no API key field.

Authorise

The first tool call opens a browser window for the OAuth authorisation. Approve it once and the grant persists.

Where this helps

Checking campaign performance without leaving the editor
Building landing pages while reading the search terms that will point at them
Wiring up conversion tracking with the GA4 and GTM tools open beside the code

Go further

Windsurf

Same JSON shape, different config path.

GTM and GA4 tools

Tag manager and analytics tools for tracking work.

Conversion tracking skills

Workflows for setting up and auditing tracking.

Common questions

Where exactly does the config live?

A user-level file at ~/.cursor/mcp.json, or a project-level .cursor/mcp.json inside a repository. Cursor reads both; the user-level one applies everywhere.

Do I need to restart Cursor?

Yes. MCP servers are read at startup, so a running instance will not pick up a new entry.

Why is there no API key in the config?

Because MCP Ads authenticates with OAuth in the browser rather than a static key. The only value in the config is the server URL.

Ready to connect?

Start free, connect the platforms you use, and run your first workflow from Claude in minutes.

Start now Read the guides ?