Google Ads MCP vs NotFair
A side-by-side look at the Google Ads MCP and NotFair MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Google Ads MCP for marketing work as a local process; choose NotFair for marketing over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Google Ads MCP when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
GOOGLE_ADS_DEVELOPER_TOKEN, GOOGLE_ADS_CLIENT_ID, GOOGLE_ADS_CLIENT_SECRET, GOOGLE_ADS_LOGIN_CUSTOMER_ID, GOOGLE_ADS_REDIRECT_URI, GOOGLE_ADS_PRIVACY_MODE, GOOGLE_ADS_ALLOW_MUTATIONS, GOOGLE_ADS_TOKEN_PATH.
Choose NotFair when
- You need dedicated capabilities in the Marketing domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 44/100 · Fair | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | OAuth 2.0 |
| Pricing | Not declared | Not declared |
| Required env vars | GOOGLE_ADS_DEVELOPER_TOKENGOOGLE_ADS_CLIENT_IDGOOGLE_ADS_CLIENT_SECRETGOOGLE_ADS_LOGIN_CUSTOMER_IDGOOGLE_ADS_REDIRECT_URIGOOGLE_ADS_PRIVACY_MODEGOOGLE_ADS_ALLOW_MUTATIONSGOOGLE_ADS_TOKEN_PATH | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 4 | 4,055 |
| Directory activity | 3 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Google Ads MCP | View NotFair |
Tools & capabilities
Google Ads MCP tools
No tool names declared yet. Check the project README from the listing page.
NotFair tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Google Ads MCP
{
"mcpServers": {
"google-ads-mcp": {
"command": "npx",
"args": [
"-y",
"google-ads-mcp-unofficial"
],
"env": {
"GOOGLE_ADS_DEVELOPER_TOKEN": "YOUR_GOOGLE_ADS_DEVELOPER_TOKEN_HERE",
"GOOGLE_ADS_CLIENT_ID": "YOUR_GOOGLE_ADS_CLIENT_ID_HERE",
"GOOGLE_ADS_CLIENT_SECRET": "YOUR_GOOGLE_ADS_CLIENT_SECRET_HERE",
"GOOGLE_ADS_LOGIN_CUSTOMER_ID": "YOUR_GOOGLE_ADS_LOGIN_CUSTOMER_ID_HERE",
"GOOGLE_ADS_REDIRECT_URI": "YOUR_GOOGLE_ADS_REDIRECT_URI_HERE",
"GOOGLE_ADS_PRIVACY_MODE": "YOUR_GOOGLE_ADS_PRIVACY_MODE_HERE",
"GOOGLE_ADS_ALLOW_MUTATIONS": "YOUR_GOOGLE_ADS_ALLOW_MUTATIONS_HERE",
"GOOGLE_ADS_TOKEN_PATH": "YOUR_GOOGLE_ADS_TOKEN_PATH_HERE"
}
}
}
}
NotFair
{
"mcpServers": {
"notfair": {
"url": "https://notfair.co/api/mcp/notfair"
}
}
}
Frequently asked questions
Google Ads MCP is categorized under Marketing and uses a local stdio subprocess. NotFair belongs to Marketing and uses a remote HTTP/SSE transport. Pick Google Ads MCP for marketing work and NotFair for marketing.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Google Ads MCP has no declared pricing — check the project's own site. NotFair has no declared pricing — check the project's own site. Auth: oauth 2.0. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add google-ads-mcp and notfair as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Google Ads MCP has a quality signal of 44/100 (Fair) with 3 views, 0 installs and 4 GitHub stars. NotFair has 49/100 (Fair) with 2 views, 0 installs and 4,055 GitHub stars.