Google Ads vs PlainRouter
A side-by-side look at the Google Ads and PlainRouter MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
G
Google AdsMarketingRead and manage your Google Ads account in chat.36FairAuth: not declaredP
PlainRouterMarketing · Local subprocess (stdio)Inspect an approved ad account and first-party signal health, then propose policy-gated actions.55GoodAuth: not declaredVerdict: choose Google Ads for marketing work; choose PlainRouter for marketing as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
PChoose PlainRouter when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
PLAINROUTER_WORKSPACE_TOKEN. - You want tools like
get_account_state, get_account_inventory, get_inventory_metrics.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | G Google Ads | P PlainRouter |
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 36/100 · Fair | 55/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | PLAINROUTER_WORKSPACE_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 34 |
| Full listing | View Google Ads | View PlainRouter |
Tools & capabilities
Google Ads tools
No tool names declared yet. Check the project README from the listing page.
PlainRouter tools 34
get_account_stateReturn the authorized advertising account, workspace, connection, Signal destination, and currently available account capabilities.get_account_inventoryRead the authorized workspace account inventory from the Meta mirror, with optional level, status, parent, and ID cursor filters.get_inventory_metricsRead daily Meta metrics beside counted Plainrouter arrivals for mirrored campaigns, ad sets and ads.get_performanceCompare Meta-reported conversions with the conversions Plainrouter accepted and verified for the selected account.get_arrivals_comparisonReturn counted arrivals beside Meta outbound clicks for the authorized workspace and selected trailing window.get-creative-libraryReturn Meta image and video assets with the ads and last-30-day performance historically associated with each asset.get_signal_healthDiagnostic view of first-party event flow, Meta delivery outcomes, match quality, and reconciliation gaps from Plainrouter stored measurements.get_install_instructionsReturn managed-hostname Path A installation material and first-arrival state for the authorized workspace.verify_signal_ingestionVerify server-side Signal ingestion by writing one idempotent, identity-free modeled event for the authorized workspace.dry_run_actionsPreview policy decisions and execution diffs for a proposed Action batch without writing it.propose-actionsPropose a batch of budget, status, upload, or creative-duplication actions for the approved ad account.upload-assetStage a JPEG/PNG image and submit a canonical upload action through workspace policy.- +22 more on 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
No confirmed install command for Google Ads yet — follow the setup steps linked from its listing page rather than a guessed package name.
PlainRouter
{
"mcpServers": {
"plainrouter-2": {
"command": "npx",
"args": [
"-y",
"@plainrouter/cli"
],
"env": {
"PLAINROUTER_WORKSPACE_TOKEN": "YOUR_PLAINROUTER_WORKSPACE_TOKEN_HERE"
}
}
}
}
Frequently asked questions
Google Ads is categorized under Marketing and uses an install path we have not confirmed yet. PlainRouter belongs to Marketing and uses a local stdio subprocess. Pick Google Ads for marketing work and PlainRouter 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 has no confirmed install command yet — follow its own setup instructions.
Google Ads has no declared pricing — check the project's own site. PlainRouter 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-5 and plainrouter-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Google Ads has a quality signal of 36/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. PlainRouter has 55/100 (Good) with 0 views, 0 installs and 0 GitHub stars.