Google Ads MCP vs Nashboard Merchants
A side-by-side look at the Google Ads MCP and Nashboard Merchants MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
N
Nashboard MerchantsMarketingMerchant intelligence for AI agents: brand/operator/location hierarchy + industry codes.12EmergingAuth: not declaredVerdict: choose Google Ads MCP for marketing work as a local process; choose Nashboard Merchants for marketing. 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.
NChoose Nashboard Merchants when
- You need dedicated capabilities in the Marketing domain.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | N Nashboard Merchants | |
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 44/100 · Fair | 12/100 · Emerging |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | Not declared |
| 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 | — |
| Directory activity | 3 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Google Ads MCP | View Nashboard Merchants |
Tools & capabilities
Google Ads MCP tools
No tool names declared yet. Check the project README from the listing page.
Nashboard Merchants 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"
}
}
}
}
Nashboard Merchants
No confirmed install command for Nashboard Merchants yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Google Ads MCP is categorized under Marketing and uses a local stdio subprocess. Nashboard Merchants belongs to Marketing and uses an install path we have not confirmed yet. Pick Google Ads MCP for marketing work and Nashboard Merchants 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. Nashboard Merchants has no confirmed install command yet — follow its own setup instructions.
Google Ads MCP has no declared pricing — check the project's own site. Nashboard Merchants has no declared pricing — check the project's own site. 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 nashboard-merchants 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. Nashboard Merchants has 12/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars.