Grona MCP
Related Servers
Alternatives to Grona MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables reporting on and managing Sponsored Products, Sponsored Brands, and Sponsored Display campaigns, keywords, targets, bids, budgets, portfolios, and budget rules through MCP clients, with dry-run, confirmation guards, read-only mode, and an audit log for safer write operations.MIT
- AlicenseAqualityBmaintenanceEnables MCP clients to report on and manage Ads Manager campaigns, creative sets, assets, and MAX ad units, waterfalls, experiments, and revenue data, with dry-run, confirmation, and audit-log safeguards for writes.42MIT
- FlicenseNot gradedqualityCmaintenanceEnables management of Google Ads accounts via MCP, providing read and write tools for campaigns, ad groups, keywords, assets, and more, with support for reporting and mutations.-
- AlicenseBqualityBmaintenanceEnables MCP clients to read and analyze Pinterest advertising data, with optional guarded write tools that preview changes before applying them, all while keeping your token on your own machine and protecting lead records.26374 npmApache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables reading and mutating Google Ads campaigns via MCP tools, and includes structured marketer workflows for search term mining, budget optimization, and weekly reviews.6MIT
- AlicenseNot gradedqualityDmaintenanceEnables MCP-capable agents to create, edit, pause, archive campaigns, and pull advertising reports from the Gravity Ads platform directly, without the API key leaving the local machine.17 npmMIT
TDQS
Scored across 19 tools
Most tools have clearly distinct purposes, and the descriptions do unusually explicit boundary work (e.g. grona_launch_campaign vs grona_set_campaign_status, grona_verify_script vs grona_check_campaign_readiness). There are still overlapping read surfaces (list_campaigns / search_campaigns / get_campaign / campaign_overview) and two create paths, so a few pairs require reading descriptions carefully before selection.
All tools share a grona_ prefix plus snake_case verb_noun naming (create_campaign, set_campaign_status, validate_edit_link, evaluate_page_targeting), which is highly predictable. The only deviations are noun-only names like grona_configuration and grona_campaign_overview, which break the verb pattern slightly but remain readable.
At 19 tools the set sits at the heavy end for a campaign/experiment domain, with several near-siblings (two creates, four read variants, two status paths) that could arguably be consolidated. Each tool does have a defensible role, but the surface feels larger than the core workflow strictly requires.
Core lifecycle is well covered: create/get/update/delete/list/search, status and guarded launch, idempotent create, editor links, snippet generation and verification, A/B split, targeting evaluation, readiness and overview. The notable gap is results/analytics reading (explicitly out of scope) and no direct variation-content or variation-delete operation, though editor links provide a workaround.