synter

Synter is a cross-platform MCP server that lets your AI agent manage ads across multiple platforms (Google, Meta, LinkedIn, Microsoft, Reddit, TikTok, and more) with read and write capabilities. It exposes a suite of tools for campaign creation, budget management, performance analytics, keyword handling, conversion tracking, creative generation, and utility actions. With streamable HTTP transport or direct local startup via npx, you can interact with all connected ad accounts through natural language prompts. Typical workflows include listing campaigns, creating or pausing campaigns, adjusting budgets, generating AI-created creatives, and pulling performance metrics across platforms, all in a unified interface.

To use Synter, configure your MCP client to point at the server and provide an API key for authentication. The provided commands show how to integrate Synter into Claude/Desktop clients, Cursor, Amp, or remote HTTP transport. Once configured, you can issue natural-language commands like creating a Google Search campaign, pausing an underperforming campaign, or generating creatives, and Synter will translate those requests into the appropriate platform actions across all connected accounts.

Prerequisites:

• Node.js (recommended v14 or newer) and npm/yarn installed on your machine
• Access to a Synter API key (from syntermedia.ai > Developer Settings)

Option A: Run with npx (no local install required)

1. Ensure Node.js and npm are installed
2. Ensure you have an API key from Synter
3. Use your MCP client to configure Synter with the following settings:
   • command: npx
   • args: ["-y", "@synterai/mcp-server"]
   • env: { "SYNTER_API_KEY": "syn_your_api_key_here" }
4. Start using Synter via your MCP client (Claude, Cursor, Amp, or Streamable HTTP)

Option B: Local install (npm install -g)

1. Prereqs: Node.js and npm installed
2. Install the package globally: npm install -g @synterai/mcp-server
3. Run locally (example): synter-mcp-server --api-key syn_your_api_key_here
4. Connect your MCP client to the local server endpoint as configured by the server CLI output.

Notes:

• The recommended approach is to use npx for zero-install usage and automatic updates.
• Always protect your API key and limit access to trusted clients.

Tips and common considerations:

• Keep SYNTER_API_KEY secure; rotate keys periodically via the Synter dashboard.
• When using streamable HTTP, ensure your client supports appropriate X-Synter-Key headers and URL endpoints (as documented in the Quick Start section).
• After any changes to connected platforms or permissions, verify that your MCP client can list campaigns across all platforms to confirm connectivity.
• If campaigns or actions seem delayed or missing, check API key permissions and ensure the connected accounts have the necessary access.
• For large campaigns or high-throughput usage, monitor rate limits and implement retry/backoff in your MCP client.