Cursor

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.

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

Authorise

The first tool call opens a browser window for the OAuth authorisation. Approve it once and the grant persists. The browser is the only place credentials are ever entered; nothing about your ad accounts lives in the config file or in Cursor's settings.

1. Restart Cursor and open the MCP settings

   After saving the file, restart Cursor fully. Under Settings → MCP the mcp-ads entry should show a green status and a tool count. If the entry is missing, the file was not read; see Troubleshooting.

2. Trigger the sign-in

   Ask the agent anything that needs a tool. Cursor opens a browser tab on mcp-ads.com where you sign in and approve the grant. Close the tab when it says you can return to the editor.

3. Verify it works

   The first real tool call should come back with the platforms you have connected in the MCP Ads dashboard. If the list is empty, the server is reachable but no platform is connected yet; connect one from the dashboard and ask again.

   Try this firstCopy

   Using mcp-ads, list the platforms I have connected and
   the accounts on each.

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
• Editing a WordPress site from the same session that reads its Search Console data

Troubleshooting

• The server is not listed after a restart: the config is in the wrong place or is not valid JSON. Check the file is at ~/.cursor/mcp.json (user level) or .cursor/mcp.json in the project root, and that there is no trailing comma after the last entry. Cursor reports a parse error only in its MCP log, not in a dialog.
• The OAuth window never opens: a popup blocker or a browser that is not the system default. Cursor prints the authorisation URL in the MCP output panel; copy it into any browser and finish there.
• "A server with this URL already exists": the same URL is defined at both the user and project level, or in two entries with different names. Keep one entry and remove the other, then restart.
• The entry shows red or zero tools: the URL is wrong or the network blocks it. It must be exactly https://mcp-ads.com/mcp-slim with no trailing slash. On a corporate network, check that mcp-ads.com is reachable from a browser first.
• Tools appear but every call fails with an authorisation error: the grant was revoked or expired. Remove the server entry, restart, add it back and approve the sign-in again.

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.