Skip to main content
Glama
logly

mureo

by logly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to mureo

  • GA4 MCP Server

    Shin-sibainu
    A
    license
    A
    quality
    D
    maintenance
    Enables Claude to retrieve and analyze Google Analytics 4 data through 20+ analysis tools, providing insights on traffic, user behavior, conversions, and engagement metrics in Japanese-formatted output.
    20
    2
    MIT

Related Servers

  • NotFair

    Swastik023
    A
    license
    Not graded
    quality
    B
    maintenance
    Provides AI agents with unified marketing toolkits for SEO, GEO, paid media, and analytics, enabling audits, analysis, and approved changes across GA4, Search Console, Google Ads, Meta, X, LinkedIn, Reddit, TikTok, WordPress, and GoHighLevel.
    MIT

  • gamm

    asphaltanchors
    A
    license
    Not graded
    quality
    B
    maintenance
    Lets AI agents query Google Ads freely while routing every write through a passkey-approved, rule-checked, audited change workflow. It issues per-agent keys, validates proposals against configurable guardrails, and applies approved changes atomically.
    Apache 2.0

  • safent-ads

    devwspito
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables self-hosted Google Ads and Meta Ads management through MCP, with human approval, hard spending limits, and audited writes; agents like Claude Code or Codex can connect to ad accounts while the server controls all credential access and platform writes.
    Apache 2.0
  • Marvento Ads MCP by MarventoCapital

    Marvento Ads MCPofficial

    MarventoCapital
    A
    license
    B
    quality
    B
    maintenance
    Enables AI agents to build and run Google Ads campaigns with write tools for campaigns, ad groups, ads, and assets, plus one-command VPS deployment for remote access.
    23
    Apache 2.0
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.8/5.0

Scored across 228 tools

Disambiguation3/5

The set is organized into clear platform namespaces and most tools target a distinct entity/action, but there are large overlapping analytical clusters (e.g., google_ads_performance_analyze vs cost_increase_investigate vs monitoring_cpa_goal; six meta_ads_analysis_* tools) where an agent could easily pick the wrong one. Several paired variants (meta_ads_creatives_upload_image vs meta_ads_images_upload_file) are distinguishable only by careful reading of source-vs-local-file semantics.

Naming Consistency4/5

The dominant domain_entity_action pattern (google_ads_campaigns_list, meta_ads_ad_sets_update, search_console_sitemaps_submit) is extremely consistent across ~200 tools. Minor deviations exist: google_ads_assets_upload_image vs google_ads_image_assets_list swaps noun order, rollback_apply and analysis_* lack the mureo_ prefix, and the meta_ads_creatives_create_* subtype variants stretch the pattern.

Tool Count1/5

228 tools is far beyond any reasonable MCP surface, even for a multi-platform ads platform; it violates the calibration's 50+ extreme-mismatch threshold. The tools are organized well, but the sheer count overwhelms context and makes correct selection much harder.

Completeness4/5

For its stated scope (Google Ads, Meta Ads, Search Console, state/strategy, creative studio, analytics), coverage is unusually thorough: CRUD lifecycles exist for campaigns, ad groups, ads, budgets, keywords, conversions, audiences, catalogs, products, lead forms, and rules. Minor gaps remain, e.g., no removal for ad group-level negative keywords, no delete for uploaded Google Ads image assets, and no Search Console sitemap removal.

Maintenance

ActivityActive
ResponsivenessResponsive

Resources