plug.directory
Add my server

Install Ads in Continue

What you need first

  • Continue, installed.
  • Node.js, which gives the npx command the server starts with.
  • Your own values for YOUR_GOOGLE_ADS_CLIENT_ID,YOUR_GOOGLE_ADS_CLIENT_SECRET,YOUR_GOOGLE_ADS_DEVELOPER_TOKEN,YOUR_GOOGLE_ADS_REFRESH_TOKEN,YOUR_GOOGLE_ADS_CUSTOMER_ID,YOUR_META_APP_ID,YOUR_META_APP_SECRET,YOUR_META_ACCESS_TOKEN,YOUR_META_AD_ACCOUNT_ID.

Steps

  1. Open ~/.continue/config.yaml. On Windows it is %USERPROFILE%\.continue\config.yaml.
  2. Add this entry. If the file already has mcpServers, add only the item from - name on.
mcpServers:
  - name: "ads-mcp"
    type: stdio
    command: "npx"
    args:
      - "-y"
      - "@gudlab/[email protected]"
    env:
      "GOOGLE_ADS_CLIENT_ID": "YOUR_GOOGLE_ADS_CLIENT_ID"
      "GOOGLE_ADS_CLIENT_SECRET": "YOUR_GOOGLE_ADS_CLIENT_SECRET"
      "GOOGLE_ADS_DEVELOPER_TOKEN": "YOUR_GOOGLE_ADS_DEVELOPER_TOKEN"
      "GOOGLE_ADS_REFRESH_TOKEN": "YOUR_GOOGLE_ADS_REFRESH_TOKEN"
      "GOOGLE_ADS_CUSTOMER_ID": "YOUR_GOOGLE_ADS_CUSTOMER_ID"
      "META_APP_ID": "YOUR_META_APP_ID"
      "META_APP_SECRET": "YOUR_META_APP_SECRET"
      "META_ACCESS_TOKEN": "YOUR_META_ACCESS_TOKEN"
      "META_AD_ACCOUNT_ID": "YOUR_META_AD_ACCOUNT_ID"
  1. Replace YOUR_GOOGLE_ADS_CLIENT_ID,YOUR_GOOGLE_ADS_CLIENT_SECRET,YOUR_GOOGLE_ADS_DEVELOPER_TOKEN,YOUR_GOOGLE_ADS_REFRESH_TOKEN,YOUR_GOOGLE_ADS_CUSTOMER_ID,YOUR_META_APP_ID,YOUR_META_APP_SECRET,YOUR_META_ACCESS_TOKEN,YOUR_META_AD_ACCOUNT_ID with your own values.
  2. Save the file and restart Continue.

Check it worked

Ask Continue: List the tools of ads-mcp.

If it does not start

spawn npx ENOENT
Node.js is not on the PATH that Continue sees. Install it, or write the full path of npx in the config.
The server starts, but its tools fail
A YOUR_… placeholder is still in the config, or its value is wrong.
Nothing changes after a restart
The file is not valid YAML any more. Check that the entry is indented like the lines around it.

Back to Ads