Other · Local MCP server
Ads MCP
MCP server for Google Ads and Meta Ads. Wraps both APIs directly to manage campaigns.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.gudlab/ads-mcp- Version
- 0.1.1
- Status
- Active
- Category
- other
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-09-22
- Updated
- 2026-09-22
- Publisher
- gudlab (GitHub) · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/gudlab) · how
- Repository
- github.com/gudlab/ads-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @gudlab/ads-mcp | 0.1.1 | stdio |
How to connect Ads MCP
Ads MCP runs locally from a Node.js package published to the npm registry: @gudlab/ads-mcp version 0.1.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @gudlab/ads-mcp@0.1.1. It reads these environment variables: GOOGLE_ADS_CLIENT_ID (required, secret), GOOGLE_ADS_CLIENT_SECRET (required, secret), GOOGLE_ADS_DEVELOPER_TOKEN (required, secret), GOOGLE_ADS_REFRESH_TOKEN (required, secret), GOOGLE_ADS_CUSTOMER_ID (required), GOOGLE_ADS_LOGIN_CUSTOMER_ID, META_APP_ID (required), META_APP_SECRET (required, secret), META_ACCESS_TOKEN (required, secret) and META_AD_ACCOUNT_ID (required); set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"ads-mcp": {
"command": "npx",
"args": [
"-y",
"@gudlab/ads-mcp@0.1.1"
],
"env": {
"GOOGLE_ADS_CLIENT_ID": "<secret>",
"GOOGLE_ADS_CLIENT_SECRET": "<secret>",
"GOOGLE_ADS_DEVELOPER_TOKEN": "<secret>",
"GOOGLE_ADS_REFRESH_TOKEN": "<secret>",
"GOOGLE_ADS_CUSTOMER_ID": "<value>",
"GOOGLE_ADS_LOGIN_CUSTOMER_ID": "<value>",
"META_APP_ID": "<value>",
"META_APP_SECRET": "<secret>",
"META_ACCESS_TOKEN": "<secret>",
"META_AD_ACCOUNT_ID": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from gudlab (GitHub)
| Server | Runs |
|---|---|
| Gud Api MCPAI agents create, run, and save API requests as Gud API collections in your project. | Local · stdio |
More other servers
| Server | Runs |
|---|---|
| AdrailsSpecialist AI agents for Meta Ads and Google Ads. Every change waits for your approval. | Remote · HTTPLive check: sign-in required |
| Adrex AIOpen-source MCP server for Google Ads & Meta Ads - manage campaigns from any AI assistant. | Local · stdio |
| AdrMcpMCP server for Architectural Decision Records: navigate, author, validate, link, and analyze them. | Local · stdio |
| AdsBuy Telegram subscribers and website traffic, billed per verified result. | Remote · HTTPLive check: sign-in required |
| Ads UploaderMeta ads bulk launcher: upload creatives, edit builds, preview, and create paused ads. | Remote & Local · HTTP, stdioLive check: sign-in required |
| AdsAgent - Google Ads MCPHosted Google Ads MCP with OAuth, bounded reads, and prepare/confirm writes. | Remote · HTTPLive check: sign-in required |
| AdsAgent - Meta Ads MCPHosted Meta ads MCP with OAuth, bounded reads, and prepare/confirm writes. | Remote · HTTPLive check: sign-in required |
| AdsapLaunch and manage Meta and Google Ads from your AI assistant. You approve every change first. | Remote · HTTPLive check: sign-in required |