Ads-mcp Server

Ads-mcp is an MCP integration. MCP server for Google Ads and Meta Ads. Wraps both APIs directly to manage campaigns.

Packages and local setup

The published npm package is @gudlab/ads-mcp, version 0.1.1. Its declared MCP transport is stdio.

The package declares GOOGLE_ADS_CLIENT_ID (required): OAuth client ID from Google Cloud Console; GOOGLE_ADS_CLIENT_SECRET (required): OAuth client secret from Google Cloud Console; GOOGLE_ADS_DEVELOPER_TOKEN (required): Developer token from Google Ads API Center; GOOGLE_ADS_REFRESH_TOKEN (required): Refresh token minted via pnpm google:auth; GOOGLE_ADS_CUSTOMER_ID (required): Default Google Ads account ID, 10 digits, no dashes; GOOGLE_ADS_LOGIN_CUSTOMER_ID: MCC account ID, only if the customer account is managed under one; META_APP_ID (required): Meta App ID from developers.facebook.com; META_APP_SECRET (required): Meta App secret; META_ACCESS_TOKEN (required): Long-lived System User access token with ads_management scope; META_AD_ACCOUNT_ID (required): Default Meta ad account ID, numeric, no act_ prefix.

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 0.1.1 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related developer tools MCP servers for tools that cover the same kind of work.