Skip to main content
Glama
wvuhskr

mcp-microsoft-ads

by wvuhskr

Related Servers

Alternatives to mcp-microsoft-ads

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables managing and analyzing ad accounts in plain language from AI assistants, including cross-account performance reports, keyword research, GAQL queries, and safe previewed changes.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to manage, report, and analyze Google Ads campaigns securely with encrypted multi-client support, real-time API integrations, and audit trail logging.
      30 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables managing Google Ads campaigns through an AI assistant with read-only reporting, recommendations, and gated write operations for bids, budgets, and statuses, all backed by preview and audit logging.
      31
      1
      MIT
    • 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
    • A
      license
      B
      quality
      C
      maintenance
      Enables AI assistants to read a ChatGPT Ads account — account summaries, performance insights, campaigns, ad groups, ads, product feeds and conversion setup — and, when writes are explicitly enabled, create or update campaigns, budgets and creatives with dry-run previews and before/after diffs.
      15
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      MCP server enabling AI assistants to manage Microsoft Advertising (Bing Ads) campaigns, including campaigns, ad groups, keywords, and ad extensions via a clean set of tools.
      -

    TDQS

    C2.4/5.0

    Scored across 47 tools

    Disambiguation2/5

    Several tools have overlapping purposes: create_pmax_campaign and draft_campaign both create campaigns, remove_entity and remove_keywords both delete keywords, and update_campaign overlaps with pause_entity/enable_entity for campaign status changes. The detailed descriptions help, but an agent could easily select the wrong tool for the same underlying operation.

    Naming Consistency2/5

    The names are all snake_case but the verb conventions are inconsistent: create_ and draft_ are used interchangeably for the same 'draft a write' pattern, get_ and list_ both appear for read operations, and generic tools like remove_entity sit alongside specific remove_keywords/remove_geo_target. This makes the tool surface less predictable than it could be.

    Tool Count2/5

    With 47 tools, this is far beyond the 25-tool threshold the rubric treats as too many. The server covers a broad domain, but many tools are convenience wrappers (e.g., get_campaign_performance, get_ad_performance, run_report) and the set would benefit from consolidation.

    Completeness2/5

    There is no tool to create an ad group, which is a core requirement for building out a Search campaign: draft_campaign creates campaigns and draft_keywords/draft_responsive_search_ad need ad groups, so the lifecycle has a critical dead end. Other gaps include no ad-copy update path and no way to create shared negative keyword lists.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues