MCP guide

Antebyte exposes your account as an MCP server. Any MCP-compatible AI assistant can connect to it and run your advertising the way you would from the dashboard: reading your current state, building campaigns, steering budgets, and pulling the impression records behind every dollar you spend. This guide covers how to connect one and what it can do.

What the MCP server is

Model Context Protocol (MCP) is an open standard for connecting AI assistants to outside systems. Antebyte implements the server side of it. Once your assistant connects, it gets a set of tools that map to the same operations the dashboard runs, so it acts on your real account instead of guessing.

The endpoint

Your account is served at https://antebyte.com/api/mcp. It speaks the standard MCP transport over HTTP, so any compliant client can reach it. There is nothing to run locally and nothing to host yourself.

Authorization

Access uses OAuth 2.1 with PKCE through your normal Antebyte login. The first time your assistant connects, it opens the Antebyte sign-in page. You approve access, and the assistant receives a token scoped to your account. There are no API keys to copy and paste, and no long-lived secret sits in your assistant's configuration. If you don't have an account yet, create one at /onboarding; if you do, sign in at /login.

Compatibility

The server works with Claude and any MCP-compatible assistant. Any client that implements the protocol connects with the same endpoint and the same login, so you are not tied to one vendor.

What the tools let you do

Once connected, your assistant has tools for the whole account:

• Read your account. Pull your accounts, campaigns, ad groups, inventory, and current performance, so the assistant works from live data rather than a stale export.
• Build from a brief. Describe a campaign in plain language and the assistant creates it, along with the creatives, and splits the budget across the channels you picked.
• Steer what's running. The assistant can pause or activate a campaign and change its daily budget. It can also set a bid cap for each channel.
• Interrogate your spend. Ask for the impressions behind any dollar figure and the assistant returns the underlying records, with the app, show, device, geo, and price for each one.

Launching stays guarded until billing is ready

Launching a campaign is enforced on the server, not in the assistant. When the assistant tries to set a campaign live, Antebyte refuses until billing is set up on your account. The assistant can read whether billing is ready, but it cannot enter payment details or move a campaign into spending before you are. Because the check runs server-side, it holds no matter how the request is phrased.

Connect in three steps

1. Add the server

In your assistant's settings, add a new MCP server and point it at https://antebyte.com/api/mcp.

2. Authorize with your login

On the first request, your assistant opens the Antebyte sign-in page. Approve access, and it stores a token scoped to your account.

3. Put it to work

Ask for real work. For example:

• "Launch a connected-TV campaign from this video with a $50 daily budget."
• "Pause any ad group spending more than $40 that hasn't converted."
• "Show me the impressions behind yesterday's spend, with the app, show, device, and price."

Start here

Create an account and connect it at /onboarding. For how we keep inventory clean, see /brand-safety; for how we handle your data, see /privacy.