The read half is ordinary enough: campaigns, performance and daily spend across whatever is connected. The write half is what separates it from most ad integrations, which are read-only by design. Campaigns get created and start spending, budgets change, keywords go live, and generated creative can be uploaded straight into an account. Audience sync stages hashed identifiers separately and carries a consent flag, which is the right shape for that data. Confirmations sit in front of destructive actions; how much authority to hand over is still a decision you make.
A server over Synter reaching the ad accounts connected to it across platforms: list and create campaigns, change budgets, pause them, manage keywords, set up conversion tracking, generate image and video creative, and sync first-party audiences.
- create_search_campaign builds a Google Ads Search campaign with its ad group, a responsive search ad and keywords in one atomic request; create_display_campaign and create_pmax_campaign cover the other Google formats, taking images from URLs
- create_meta_campaign for Facebook and Instagram, create_linkedin_campaign with industry, company-size and job-function targeting, and create_reddit_campaign with subreddit and interest targeting
- list_campaigns spans the connected platforms with status, budget and performance; get_performance returns impressions, clicks, spend, conversions and ROAS for a date range; get_daily_spend breaks spend down day by day across accounts
- pause_campaign and update_campaign_budget act by campaign ID across whichever platform it belongs to
- add_keywords with a match type, and add_negative_keywords at campaign or ad-group level to block search terms you do not want
- create_conversion returns the conversion ID and label needed for GTM setup, list_conversions shows what already exists, and diagnose_tracking checks a URL for gtag.js, GTM and pixel installation
- generate_image produces ad creative through Imagen 4, Flux or Stable Diffusion and generate_video through Veo, Runway or Luma, with upload_image putting an asset into the platform
- Audience work: manage_audience builds Customer Match lists in Google Ads from emails, phones or company domains, sync_audience uploads to Google, Meta, LinkedIn, Microsoft, Reddit, TikTok or X, and stage_audience_artifact holds hashed identifiers in a private store first — both carry an explicit consent flag
- run_tool reaches the rest of the Synter catalogue by name for operations the typed tools do not cover
A Synter API key, with the ad accounts connected on the Synter side. Locally, @synterai/mcp-server over stdio with SYNTER_API_KEY set; remotely, Streamable HTTP at https://mcp.syntermedia.ai/mcp/ with the key sent as an X-Synter-Key header, which is where the full hosted tool set lives. The project is direct about the consequence: an agent with this connected can create campaigns that begin spending immediately, and it ships confirmations in front of destructive actions.
One command plus a key — npx @synterai/mcp-server, then supply credentials