Taboola MCP and Outbrain MCP: Connect AI to Native Ads Data

A Taboola MCP server lets an AI assistant such as Claude, ChatGPT or Cursor read your Taboola Realize account and answer questions about native campaigns in plain language. Outbrain offers the same idea for Amplify. Both networks now run official MCP servers, and both can change live campaigns, not just report on them. This guide explains what each server does, how to connect it, the permissions to check and when a single connection across all your ad platforms is the better setup.

If MCP itself is new to you, start with our plain-words guide to what an ads MCP server is and how to use one safely. If you are still choosing between the two networks, our Taboola vs Outbrain comparison covers reach, bidding and formats. This article stays on the AI connection.

What does an MCP server do for native ads?

An MCP server for native ads turns your Taboola or Outbrain account into a set of tools that an AI assistant can call. The Model Context Protocol tools specification describes tools as "model-controlled", which means the model picks the tool that fits your prompt and calls it for you.

For a native media buyer, that changes three daily jobs:

• Reporting. Ask "which campaigns spent most yesterday and at what CPA?" instead of exporting a report and building a pivot table.
• Publisher and site analysis. Native performance often hides in a long tail of sites and widgets. A conversational question is a fast way to find the sites dragging a campaign down.
• Routine changes. Pausing a campaign or adjusting a daily budget can happen from the chat, once you approve it.

The data is the same data you see in Realize or Amplify. MCP changes how you ask for it, not what the platform knows.

What Taboola offers: the Realize MCP server

Taboola documents an official Realize MCP server in its Backstage API reference. It is a hosted server at https://mcp.realize.com/mcp, using the streamable HTTP transport, and the page states that "there is no local install". Authentication uses OAuth 2.1, and you sign in through Taboola single sign-on on first use.

Taboola's developer docs say the server works with "any MCP-compatible AI client". Clients with a connector directory, such as Claude, Codex, Cursor and ChatGPT, can add it through the Realize MCP connector, and any other MCP client can connect directly with a little more setup.

What it can do, according to the Realize MCP repository on GitHub, is wider than reporting. The repository describes "read and write access to Taboola's Realize API". Read tools include account search, campaign and item lists, audience and publisher searches and dynamic reports. Write tools include create_campaign, update_campaign and tools to create and update native and display items and conversion rules.

Taboola's help centre article on the Realize MCP server adds two safeguards worth knowing:

• "Each change runs only after you approve it, so nothing is altered without your sign-off."
• "The assistant can only see and act on the accounts and data your Realize credentials are authorized to access."

The same article notes that capabilities are still expanding, so some tasks remain dashboard-only for now. If you are setting up the account itself, our Taboola ads setup guide walks through the Realize dashboard step by step.

The Backstage API underneath

Under the MCP server sits the Backstage API, Taboola's API for campaign management and reporting. Its welcome page says you need a Taboola advertiser or publisher account first, then a client_id and client_secret, and that "existing Taboola customers can generate API credentials on the API Keys page". The MCP server saves you from handling those credentials yourself, because single sign-on replaces them.

What Outbrain offers: the Amplify MCP server

Outbrain, which completed its corporate renaming to Teads Holding Co. on 9 June 2025 according to the company's press release filed with the SEC, still runs Amplify as its advertiser platform. Outbrain announced the Amplify MCP server as a native MCP implementation that lets AI agents "connect directly to the Amplify API and Dashboard".

The Outbrain help page on connecting to the MCP server gives the practical details:

• Endpoint: a remote server at amplifymcp.outbrain.com.
• Authentication: a personal Amplify API token, sent as a bearer token in the Authorization header. You first apply for API access, and generating the token in Amplify asks for your password and a two-factor code.
• Tools: about 50, grouped into marketer, campaign management, content management, reporting, publisher and platform, geographic and targeting, content performance and advanced analytics.
• Write actions: enable or disable campaigns and content, and change a campaign's daily budget.
• Clients: an npm installer for Claude, VS Code and Cursor, manual guides for Claude Desktop, Cursor, VS Code and IntelliJ, and an mcp-remote proxy for clients that cannot send custom headers.

The Amplify API itself is listed on Outbrain's developer site as the API for "campaign management and reporting", with access granted on application. For the account side, our Outbrain ads setup guide covers the Amplify setup from the start.

Taboola MCP vs Outbrain MCP at a glance

Taboola MCP and Outbrain MCP solve the same problem in two different ways, mainly in how you authenticate and what the server can change. The table sums up what each official page states as of October 2026.

The last row is the limit both share. Each server covers a single network, so a team buying on Taboola, Outbrain and Meta needs three connections and still compares the numbers by hand.

How to connect Claude, ChatGPT or Cursor to native ads data

Connecting an AI assistant to Taboola or Outbrain data comes down to four routes, each with a different trade-off between setup effort and coverage.

1. The official Taboola MCP server. Add the Realize MCP connector from your client's directory, or add https://mcp.realize.com/mcp as a remote server, then sign in with Taboola. This is the shortest path for Taboola-only questions.
2. The official Outbrain MCP server. Request Amplify API access, generate a token, then add the Amplify endpoint with the token in the Authorization header. Use the proxy route if your client cannot send headers.
3. Community MCP servers. Directories list unofficial Taboola and Outbrain servers. Check who maintains them, how they store your credentials and whether they call the official API before connecting a live account.
4. A multi-platform MCP server. One connection reads every network you buy on, so a question such as "compare Taboola and Meta CPA this week" gets one answer.

A fifth option, exporting to a reporting tool and asking the assistant about the export, avoids write access entirely. Our guide to connecting Taboola and Outbrain to Looker Studio covers that route.

Risks and permissions to check

Connecting AI to native ad accounts is safe when you control what the assistant can see and change. The risks come from credentials and unconfirmed actions, not from the AI itself, as our ranking of AI connection methods by risk explains in detail.

The MCP specification sets the baseline: "there SHOULD always be a human in the loop with the ability to deny tool invocations", and clients should prompt for confirmation on sensitive operations and log tool usage for audit. In practice:

• Keep confirmation prompts on. Both official servers can change live spend. Never auto-approve tool calls on an account with budget behind it.
• Treat the Amplify token like a password. Outbrain's setup examples store it in configuration files. Keep those files out of shared folders and version control, and regenerate the token if it leaks.
• Use the narrowest account access. Taboola's server sees what your Realize login sees. A login limited to the accounts you manage limits what the assistant can touch.
• Start with reporting questions. Ask for spend and CPA first and check the answer against the dashboard before you ask for any change.
• Name the account and date range. Taboola's help centre notes that requests usually start by identifying the account, and reports need an explicit date range. Vague prompts get vague answers.

Where Wevion fits

Native buyers rarely run Taboola or Outbrain alone, so the single-network limit shows up quickly. Wevion connects Meta, Google, TikTok, Taboola, Snapchat and Outbrain through one MCP connection, so your AI client can compare native and social spend, ROAS and conversions in the same chat, and the available tools always reflect the permissions of the credentials you connect with.

According to the Wevion MCP and CLI page, the server exposes campaigns, ad accounts and insights as tools. It works with MCP clients that support a remote server over Streamable HTTP (POST) with custom headers, such as Claude Desktop, Cursor, Cline and VS Code. You create an API key in the API keys section and send it in the x-api-key header. Each key is scoped to specific areas and actions, can be read-only or read plus write, and can be revoked at any time. Your MCP client asks before every action. The MCP server and CLI are available from the Pro plan.

Inside Wevion itself, Wavo, the AI copilot, already works across these platforms, proposing changes for you to approve.

Key takeaways

• Taboola and Outbrain both run official MCP servers: Realize MCP and Amplify MCP.
• Realize MCP is hosted and uses Taboola single sign-on; Amplify MCP uses a personal API token in a header.
• Both servers can change live campaigns, so keep confirmation prompts on and start with reporting questions.
• Each official server covers one network only.
• A multi-platform MCP server answers questions across native and social from one connection.

Want to ask one assistant about Taboola, Outbrain and your social campaigns together? Start a 14-day free trial of Wevion on the Pro plan, no card needed, and connect the Wevion MCP server to your AI client.

Sources (checked 29 October 2026): Taboola Backstage API: Realize MCP, Realize MCP on GitHub, Realize help centre: Realize MCP server, Taboola Backstage API welcome, Outbrain: how to connect to the MCP server, Outbrain: introducing the Amplify MCP server, Outbrain developers: Amplify API, Teads press release on the name change, MCP specification: tools.