MCP

MCP Configuration

Configure your AI client to connect to Synter's MCP server

AI-ready docs| Ready for Claude, Cursor, ChatGPT

Copy this page formatted as an executable prompt for your AI coding assistant or subagent.

Prerequisites

A Synter account with connected ad platforms
An API key from the Developer Portal
One of the clients below installed

One auth method

The Synter MCP server (mcp.syntermedia.ai) is API-key-only today — an X-Synter-Key header, or a bearer token for clients that only support that shape. There is no browser sign-in / OAuth flow for this server; every client below uses the same key.

No account yet? Onboard from your MCP client

You can create a Synter account without leaving your AI client. The MCP server exposes two onboarding tools that work before you have an API key, and neither costs credits:

Start onboarding

Ask your AI client to call the tool with your work email. This creates an account, emails you a magic link, and returns a session token.

text

synter_onboarding_start(email="you@company.com")

Verify your email

Open the magic link from the email to verify your address.

Check onboarding status

Poll with the session token returned by the first call until it reports your account is ready.

text

synter_onboarding_status(session_token="...")

Add your API key

Once ready, copy your API key from the Developer Portal and add it to your client configuration below, then restart the client.

Client configuration

1. Open Claude Desktop → Settings → Connections
2. Paste this server URL and authenticate with your API key when prompted:

https://mcp.syntermedia.ai

Using environment variables

Instead of hardcoding your API key, use an environment variable:

bash

# Add to your shell profile (~/.zshrc or ~/.bashrc)
export SYNTER_API_KEY="syn_your_api_key_here"

Verify connection

After configuring, restart your AI client and ask:

"What ad platforms are connected to my Synter account?"

Troubleshooting

"Invalid API key" error

Verify your API key is correct and hasn't been revoked

Connection timeout

Check your internet connection and verify the endpoint is reachable

Tools not appearing

Restart your AI client completely after saving the config file

429 / RATE_LIMIT_EXCEEDED

Your client is calling tools faster than the courtesy rate limiter allows. Slow down — see Rate Limits & Credits for details.

Was this page helpful?

PreviousOverview Next Available Tools