← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionAdsCross-platform ad management MCP server for Google, Meta, TikTok, LinkedIn, Amazon & ChatGPT AdsMartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS57 / 100 · C79 / 100 · B
Reliability8 / 2012 / 20
Security and permissions12 / 2018 / 20
Maintenance9 / 2016 / 20
Documentation14 / 2018 / 20
Setup experience14 / 2015 / 20
Best for
  • Ad marketers
  • Digital marketing agencies
  • Businesses managing multiple ad accounts and platforms
  • Teams using AI assistants for ad optimization
  • Engineering teams scaling AI coding agents while controlling spend
  • Platform teams that need auditable, rollback-aware agent execution records
  • Organizations using multiple agents (Claude, Codex, Gemini) under one governed flow
Not for
  • Users who do not need ad management features
  • Users who want a fully local solution without cloud dependencies
  • Users with a limited budget who only need simple ad tools
  • Developers who just want a simple code-completion helper without run governance
  • Teams unwilling to accept local JSONL run records with HMAC signing
  • Environments without a supported adapter (Claude/Codex/Gemini CLIs, direct provider, or verifier-only)
Required permissions
  • Access your ad platform accounts (via OAuth)
  • Read and modify campaigns, ad groups, ads, etc.
  • May create campaigns (but defaults to paused state)
  • Access account reports and performance data
  • Read/write access to the configured repo root (writable scope restrictable via --allow-path/--deny-path)
  • Ability to invoke the chosen agent CLI (Claude/Codex/Gemini, etc.) and its underlying model account
  • Local disk writes for run records, receipts, and share outputs (share/run-receipt., etc.)
  • Execution of user-configured verifier commands (e.g. npm test)
Risks and side effects
  • Ad data may be sent to Adspirer servers for processing
  • Third-party authorization required, potential credential exposure risk (though OAuth is used and passwords are not stored)
  • Campaigns could be accidentally launched, but default is paused requiring human approval
  • Free tier has monthly call limits
  • Verifier commands are executed; poorly chosen verifier commands carry security risk despite preflight policy checks
  • Cost and token figures may be estimates (labeled with provenance) and should not be treated as settled accounting
  • Receipt integrity must be verified before use as trustworthy evidence; missing rollback evidence is flagged as EVIDENCE_BOUNDARY
  • Policy defaults come from martin.config.yaml and can be overridden by CLI flags; misconfiguration can loosen safety boundaries
Supported clientsClaude Desktop, ChatGPT, Cursor, Codex, Gemini CLI, Claude Code, Windsurf, ClineClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools60