MCP Configuration
Configure your AI client to connect to Synter's MCP server
Copy this page formatted as an executable prompt for your AI coding assistant or subagent.
Prerequisites
- A Synter account; start with read-only access before enabling paid writes
- An AI client that supports hosted MCP and browser OAuth
- No API key copy or secret pasted into chat
One secure endpoint
https://mcp.synterai.com as a Streamable HTTP server and complete browser OAuth. The client stores the resulting token; it does not belong in chat, configuration text, URLs, or logs.If you have an older saved server URL, replace it with this endpoint and sign in with the account for your existing workspace. Updating the URL does not require deleting your workspace or reconnecting its ad accounts.
Root endpoint and /mcp compatibility path
https://mcp.synterai.com. The same service also accepts https://mcp.synterai.com/mcp; it is a compatibility path, not a second server or a separate integration. Use the root URL consistently in a new client configuration. For an account-scoped first read, follow the Google Ads and Meta Ads reporting workflow for Codex.Agent-specific conveniences
These are optional shortcuts. Every supported client connects to the same endpoint and authenticates in the browser.
1. Open Claude Desktop → Settings → Connections
2. Add this server URL and complete browser sign-in:
https://mcp.synterai.comHeadless clients and auth headers
Browser OAuth needs no key. For CI or a client without a browser, send your key as X-Synter-Key on the hosted endpoint, or use the local stdio package with SYNTER_API_KEY. Writes from MCP follow the approval model.
| Surface | Endpoint | Accepted | Use |
|---|---|---|---|
| REST tools endpoint | POST https://synterai.com/api/v1/tools/run | Authorization: Bearer syn_…, X-Synter-Key: syn_…, X-API-Key: syn_… | Authorization: Bearer syn_… |
| REST resource endpoints | https://api.synterai.com/v1/… (campaigns, me, credits, tools/pending) | Authorization: Bearer syn_…, X-Synter-Key: syn_… | Authorization: Bearer syn_… |
| SDKs (Python, TypeScript, Rust, Java, Go) and the synter CLI | POST /api/v1/tools/run | The SDK sets the header for you | Pass the key to the client. Every SDK sends Authorization: Bearer syn_… |
| Local stdio MCP (npm @synterai/mcp-server) | POST https://synterai.com/api/v1/tools/run | Set SYNTER_API_KEY in the server's env block | The package sends Authorization: Bearer syn_… |
| Hosted MCP | https://mcp.synterai.com | Browser OAuth (the client sends Authorization: Bearer <OAuth access token>), or X-Synter-Key: syn_… for headless clients | OAuth. Headless: X-Synter-Key. Do not put an API key in Authorization on this host. |
Keys start with syn_ (sandbox keys with syn_test_). Create one at synterai.com/developer, keep it in SYNTER_API_KEY or a secret store, and send one header per request. On the hosted MCP endpoint, the Authorization header is reserved for the OAuth token the client gets from browser sign-in, so a failed key there shows up as a sign-in prompt rather than a key error. Use X-Synter-Key when you connect a hosted MCP client with a key. Details: Authentication.
Verify connection
After configuring, restart your AI client and ask:
Troubleshooting
Browser sign-in does not open
Confirm the client supports hosted MCP with OAuth. If it does not, use the generic/manual install guide; do not paste credentials into chat.
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.