# Install Synter in your AI agent

Connect your agent to Synter for advertising research, campaign execution and measurement. Copy a setup prompt or choose your app. You approve access and live changes.

Canonical guide: https://syntermedia.ai/installation-instructions

## Before you start

- A current AI app with remote MCP and OAuth support, plus permission to add a connector. Managed workspaces may require an administrator.
- A Synter account and access to the intended workspace. Create an account if needed, or ask your workspace administrator for an invitation.
- For the first advertiser read: a connected ad account you are authorized to use. Connecting your agent does not automatically connect an advertiser account.

Account setup: https://syntermedia.ai/get-started
Connections: https://syntermedia.ai/settings/credentials
Pricing: https://syntermedia.ai/pricing

## Install with my agent

Paste this prompt into your agent. You complete browser sign-in; the agent configures and verifies only what it can.

# Install Synter MCP

If you can manage MCP settings, configure Synter as a hosted MCP server using this endpoint. Otherwise, show me the exact steps to complete in my client UI:

https://mcp.syntermedia.ai

- Use Streamable HTTP and complete Synter sign-in in the browser (OAuth). If this client lacks remote MCP or OAuth support, say it is unsupported for secure Synter setup and direct me to https://syntermedia.ai/installation-instructions or the Synter web app.
- Never ask me to paste an API key, token, or other secret into this chat. Never put secrets in a URL or logs.
- Copying configuration or opening an install link is not a verified install. Verify an authenticated MCP tool response; a successful diagnostic is not yet a useful advertiser read.
- After connecting, use this first-read prompt exactly:

Before any Synter tool call, including diagnostics and account discovery, inspect its current runtime pricing and show me the cost; do not guess whether the call is free or how many credits it costs. If the cost is unknown, stop and ask for clarification rather than running the call. Confirm my approval before any metered call. Connect to Synter and confirm which workspace I am using. List the connected advertiser accounts and ask me to choose if there is more than one. For the selected account, summarize the last seven complete days in the account timezone only if the tool supports that exact window. State the exact start date, end date, timezone, account name, and account ID before running the read. If the tool only supports a rolling window or includes today, disclose the actual dates and timezone and ask my permission to use that window instead; never label it seven complete days. Report spend, conversions, and CPA where available, and explain missing or zero-delivery data without fabricating recommendations. MCP OAuth authorizes this coding client to use Synter; advertiser OAuth separately authorizes the platform connection. If no account is connected or authorization has expired, explain the specific connection that needs attention and do not claim success. Do not change campaigns or create new resources.
- Do not request credentials as a workaround.

Before editing settings, detect my client and inspect its existing MCP configuration. Reuse an existing Synter connection; never overwrite other servers or add a duplicate. Preserve existing approval policies. If browser sign-in or an administrator is required, pause for me to complete that step. Do not install unrelated software or enable automatic tool approval.

Full guide: https://syntermedia.ai/installation-instructions.md

## Set it up myself

Server: https://mcp.syntermedia.ai
Transport: Streamable HTTP
Authentication: browser OAuth

Choose one client, not every option.

### Claude Code

One terminal command. No Synter package or API key needed.

1. With the Claude Code CLI installed, run the command below in your terminal. It adds Synter to your user-level settings.
2. Start Claude Code. Open /mcp, select synter-ads, and complete Synter sign-in in the browser.
3. Return to Claude Code and paste the first-read prompt in step 3 below.

```text
claude mcp add --transport http --scope user synter-ads https://mcp.syntermedia.ai
```

[Official client instructions](https://code.claude.com/docs/en/mcp)

### Claude Desktop / Cowork

Add a hosted connector. No terminal or local JSON file needed.

1. Open Customize → Connectors in Claude. Choose + → Add custom connector (some versions show Settings → Connectors). For a managed workspace, an owner must first add the connector in organization settings.
2. Name it Synter and enter https://mcp.syntermedia.ai as the remote server URL. Add the connector, then select Connect and complete browser sign-in. Do not enter an API key or invent OAuth client credentials.
3. Enable Synter for the conversation from the + menu → Connectors. Paste the first-read prompt below. Connector availability and menu labels depend on your app version and administrator settings.

[Official client instructions](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp)

### Codex

Use the CLI to add Synter, then authorize it in your browser.

1. With the Codex CLI installed, run the add command below. If it already completes OAuth, you can skip the second command; otherwise run the login command.
2. Complete Synter sign-in in the browser. The CLI and IDE extension share ~/.codex/config.toml on the same host. A cloud or remote host may need its own configuration.
3. Open a new Codex session, check /mcp, and paste the first-read prompt below.

```text
codex mcp add synter-ads --url https://mcp.syntermedia.ai
codex mcp login synter-ads
```

[Official client instructions](https://developers.openai.com/codex/mcp)

### Cursor

Open the install link, review the server, then sign in.

1. Select Add to Cursor on the device where Cursor is installed. Approve the server named synter-ads.
2. In Cursor Settings → Tools & MCP, complete the Synter sign-in action for that server and enable it.
3. Paste the first-read prompt in an agent chat. If the install link does not open, merge the JSON below into ~/.cursor/mcp.json. Preserve other server entries, then reload Cursor.

```text
{
  "mcpServers": {
    "synter-ads": {
      "url": "https://mcp.syntermedia.ai"
    }
  }
}
```

[Add to Cursor](cursor://anysphere.cursor-deeplink/mcp/install?name=synter-ads&config=eyJ1cmwiOiJodHRwczovL21jcC5zeW50ZXJtZWRpYS5haSJ9)

[Official client instructions](https://cursor.com/docs/context/mcp/install-links)

### VS Code / Copilot

Add the HTTP server to your user profile or workspace.

1. Select Add to VS Code. Alternatively, open the Command Palette → MCP: Add Server → HTTP and enter the server URL shown above, named synter-ads.
2. Choose your user profile or workspace. Review the trust prompt, start the server, and complete Synter browser sign-in. Keep tool approvals enabled.
3. Open Copilot agent chat, enable the Synter tools, and paste the first-read prompt. For manual JSON setup, use MCP: Open User Configuration or merge the JSON below into .vscode/mcp.json; preserve other servers.

```text
{
  "servers": {
    "synter-ads": {
      "type": "http",
      "url": "https://mcp.syntermedia.ai"
    }
  }
}
```

[Add to VS Code](vscode:mcp/install?%7B%22name%22%3A%22synter-ads%22%2C%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fmcp.syntermedia.ai%22%7D)

[Official client instructions](https://code.visualstudio.com/docs/copilot/customization/mcp-servers)

### Amp

Add the hosted server from the terminal and authorize it.

1. With Amp installed, run the add command below. By default it changes your user settings; add --workspace to the add command only if you intend to configure the project.
2. Run the login command and finish Synter sign-in in the browser. Never pass a secret through chat or a URL.
3. Start a new Amp thread and paste the first-read prompt below. Reuse an existing Synter connection instead of adding a second one.

```text
amp mcp add synter-ads https://mcp.syntermedia.ai
amp mcp oauth login synter-ads
```

[Official client instructions](https://ampcode.com/manual#mcp)

### ChatGPT

Use a custom remote MCP app where your account and workspace permit it.

1. On ChatGPT web, enable Developer mode in Settings. The location varies by rollout (Security and login, or Apps → Advanced settings). An administrator may need to grant access.
2. Create a developer-mode app from Plugins or Apps → Create. Name it Synter, set the remote MCP server URL to https://mcp.syntermedia.ai, choose OAuth, and finish browser sign-in and tool discovery. Keep confirmations enabled.
3. Select Synter from the conversation's developer-mode/app picker and paste the first-read prompt. If Create or Developer mode is unavailable, ask your administrator or use another supported client; do not bypass workspace restrictions.

[Official client instructions](https://platform.openai.com/docs/guides/developer-mode)

### Another agent / custom runtime

Use a native remote MCP client with Streamable HTTP and OAuth support.

1. Register a remote server named synter-ads at https://mcp.syntermedia.ai. Use Streamable HTTP, not the documentation URL or an invented /sse path.
2. Use the client's OAuth discovery and browser authorization flow. Store credentials only in its secure credential store. Do not copy another user's token or browser session.
3. Reload tool discovery and run the first-read prompt. If the runtime cannot configure itself, follow its documented setup. For a headless service without interactive OAuth, use the scoped API-key/SDK path under Advanced below, with an explicitly provisioned credential.

## Verify before making changes

Paste this first-read prompt into your connected agent:

Before any Synter tool call, including diagnostics and account discovery, inspect its current runtime pricing and show me the cost; do not guess whether the call is free or how many credits it costs. If the cost is unknown, stop and ask for clarification rather than running the call. Confirm my approval before any metered call. Connect to Synter and confirm which workspace I am using. List the connected advertiser accounts and ask me to choose if there is more than one. For the selected account, summarize the last seven complete days in the account timezone only if the tool supports that exact window. State the exact start date, end date, timezone, account name, and account ID before running the read. If the tool only supports a rolling window or includes today, disclose the actual dates and timezone and ask my permission to use that window instead; never label it seven complete days. Report spend, conversions, and CPA where available, and explain missing or zero-delivery data without fabricating recommendations. MCP OAuth authorizes this coding client to use Synter; advertiser OAuth separately authorizes the platform connection. If no account is connected or authorization has expired, explain the specific connection that needs attention and do not claim success. Do not change campaigns or create new resources.

Success means an authenticated tool response for the intended workspace and account, with an exact reporting window or an explicit no-data explanation. A config file or tool list alone is not success. Installation does not launch campaigns. Reads may cost credits; review current pricing and approve metered calls first.

## Troubleshooting

### Command not found

Install or update your chosen client's official CLI first, then reopen your terminal. Hosted Synter setup itself does not require Node.js, Python, Docker or a local Synter server.

### Sign-in did not open or expired

Check the client's MCP settings for synter-ads and use its sign-in action. In Claude Code use /mcp; in Codex run codex mcp login synter-ads; in Amp run amp mcp oauth login synter-ads. If a callback fails, retain the error and check the client's supported browser/remote-host flow. Never paste an authorization code into chat.

### Connected, but no tools appear

Enable Synter for the current conversation, refresh tool discovery or start a new session. Confirm the URL is https://mcp.syntermedia.ai and the transport is Streamable HTTP. Check workspace policies before changing settings; a copied config is not evidence of a working connection.

### Wrong workspace or missing ad account

Check the active Synter workspace and the advertiser account selector first. Confirm membership and that the intended account is connected in Settings → Credentials. Agent OAuth and advertiser authorization are separate. Reauthorize only the connection whose failure is confirmed; never reconnect unrelated client accounts.

### Insufficient credits, forbidden, or unavailable

Stop and inspect the exact error. A credit, permission, unsupported-operation or rate-limit error is not proof that OAuth is broken. Review billing or ask the workspace owner for the specific permission. Do not buy credits, broaden scopes or retry writes automatically. Share the client/version and a redacted error with support, never credentials.

Support: https://syntermedia.ai/contact

## Advanced

### Optional Claude Code playbooks

The hosted connection is enough to begin. To add Synter's packaged playbooks, run these commands inside Claude Code, not your terminal. Inspect existing connections before installing; the plugin may also provide MCP configuration. Restart your session and complete browser sign-in.

```text
/plugin marketplace add Synter-Media-AI/plugin
/plugin install synter@synter
```

[Plugin source](https://github.com/Synter-Media-AI/plugin)

### Headless services, SDKs and local MCP

For application code, use a scoped Synter API key provisioned in the developer portal and injected from your secret manager. Never put it in chat, committed JSON or shell history. SDK and local MCP packages are separate from the hosted OAuth setup and have their own runtime requirements. Follow the SDK guide for published versions and environment-variable configuration.

[SDK and local MCP setup](https://docs.syntermedia.ai/sdk)

### Teams and technical agencies

Start with one authorized client workspace and a read-only evaluation. Record the marketer/operator, technical owner and executive sponsor. Each person authorizes their own access; never share tokens across clients. Confirm workspace, account, cost, budget, geography and approval owner before authorizing campaign changes. Installing Synter does not authorize autonomous spending.

[Read the operating manual](https://syntermedia.ai/manual)

## Resources

- [Manual](https://syntermedia.ai/manual): Operating model, approvals and workflows.
- [API docs](https://syntermedia.ai/docs): Tool contracts, platform limits and SDKs.
- [Sample audience data](https://syntermedia.ai/samples/b2b-agent-audience-synthetic.csv): Six synthetic B2B scenarios, including internal-agent teams and technical agencies. Not customer data or an activation list.