Hosted MCP and API for advertising agents

Synter connects Claude Code, Codex, Cursor, and other MCP clients to cross-platform ad reporting and campaign management.

43 advertising platforms, the only Agentic DSP

All own-account read, reporting, budget pacing, conversion audit, and GAQL diagnostic tools across all 43 ad platforms operate with zero connector fees and 0% ad spend markup. When you are ready to run live campaign writes, budget mutations, or creative generation, one developer can start on SOLO at $20.00 per month ($200.00 per year). Light writes like pausing a campaign cost $0.05, and ad spend is billed directly by the ad platforms.

A workspace for five team members uses SCALE at $500.00 per month ($5,000.00 per year). Check account limits and current usage rates on pricing before choosing a plan.

When to use Synter

Use Synter when your team wants a hosted advertising integration for an existing agent or application. Connect through Model Context Protocol (MCP), call the REST API from your own code, or use an SDK. You can keep your current agent and orchestration; the Synter plugin is optional.

Synter runs ads across 43 ad platforms, including Google Ads, Meta, LinkedIn, Microsoft Ads, TikTok, Reddit, and Amazon. Reporting, creative, and write operations differ by platform API, account permissions, and connection. Check the tool reference for your exact operation before choosing an integration.

Evaluate the integration

Start with a read-only workflow on one connected account and compare its metrics with the ad platform. Check the required scopes, rate limits, and per-tool costs before adding writes. The hosted service depends on Synter and upstream platform availability; support for 43 ad platforms does not imply identical capabilities on every network.

See current pricing, usage limits, and security documentation for evaluation. The SDK guide and REST reference cover integrations that run outside an MCP client. Before you enable writes, read how approvals work: which writes run immediately, which wait for a person, and who approves them on each surface.

How it works

Quick setup (Claude Code)

Run this in your terminal:

claude mcp add synter-ads \
  --transport http \
  https://mcp.synterai.com

Complete browser sign-in when prompted. For Codex, Cursor, and other clients, use the configuration guide. For unattended REST integrations, create a scoped key in the Developer Portal and load it from your environment or secret manager. See API authentication.

Google Ads and Meta Ads reporting in Codex

Synter provides hosted MCP reporting tools for both Google Ads and Meta Ads. Connect Codex using the configuration guide, complete browser sign-in, and connect the accounts you are authorized to read. A successful MCP login alone does not grant access to an ad account.

First call get_workspaces and verify that current_workspace matches the intended workspace. If it differs, obtain authorization to switch workspace or reconnect before reading. Then call list_connected_accounts to choose the Google Ads customer and Meta ad account. If more than one account matches, ask the user to choose; do not use a default workspace or combine different clients. Confirm that the connection is active and the granted permissions allow reporting.

Call pull_google_ads_performance with level="campaigns" and pull_meta_ads_performance with level="campaign". Pass the selected account_id and the same explicit start_date and end_date (YYYY-MM-DD) to each tool. Inspect the current tool schema before calling; no separate Google or Meta MCP installation is required for these Synter tools.

In the workspace I choose, use Synter to report on my selected Google Ads and Meta Ads accounts for the same date range. Use read-only reporting tools. Show account IDs, reporting dates, currency, spend, clicks, conversions and CPA separately by platform. Preserve each platform's conversion definitions and attribution window; do not sum conversions as unique customers. Cite the returned source and freshness, and show errors or missing data instead of replacing them with zero. Do not create, pause, publish, or change campaigns or budgets.

Read-only instructions describe this workflow; they do not reduce an OAuth token's permissions. Review the actual grant and use least-privilege credentials available to your workspace. A copied configuration is not an install check: verify a successful, account-scoped report before relying on the connection. Reconcile one campaign against its native Ads Manager.

Example prompts

Supported AI clients

Every client below connects to the same https://mcp.synterai.com endpoint using browser OAuth in compatible clients. See Configuration for the exact snippet per client.