Skip to main content
Glama
approval-gated-mcp

approval-gated-mcp

by qcwebworks

Related Servers

Alternatives to approval-gated-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      An MCP server that extends the official Google Ads MCP with safe, confirmed campaign administration across manager accounts, featuring immutable mutation plans, multi-step approvals, and post-write verification.
      8
      Apache 2.0
    • A
      license
      C
      quality
      B
      maintenance
      Enables MCP clients to inspect operational status and channels, lint human-reviewed plans, search and query ledger data, and run queue-based writes with dry-run defaults and safeguards against unverified or unapproved campaigns.
      48
      2
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables 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.
      42
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables policy-governed MCP interactions with deterministic authorization, tenant isolation, minimized PII exposure, and human approval gates for sensitive mutations, while producing structured audit events.
      3
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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
    • A
      license
      B
      quality
      B
      maintenance
      Enables MCP clients to read Snapchat Ads campaigns and performance and to prepare preview-first changes for selected ad accounts, with opt-in write tools and explicit confirmation before applying updates.
      21
      131 npm
      Apache 2.0

    TDQS

    A3.8/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct resource or action: listing campaigns vs. plans, proposing budget/status/undo changes, and fetching a single plan. There is no meaningful overlap or confusing boundary between tools.

    Naming Consistency5/5

    All names use snake_case with a small set of predictable verb prefixes (list_, propose_, get_). The pattern is consistent throughout, including propose_budget_change, propose_status_change, and propose_undo.

    Tool Count5/5

    Six tools is well-scoped for an approval-gated campaign change server. Each tool covers a necessary read or propose operation, and none feels redundant or missing at the count level.

    Completeness4/5

    The surface covers listing campaigns, proposing budget/status changes, proposing undos, and inspecting plans. It is strong, but if the server is meant to support broader campaign changes, other proposal types (e.g., creative or targeting) would be needed.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues