Skip to main content

DatAds MCP and Public API: what they are and what they can access

Understand what the DatAds MCP and Public API are, how they differ from Blink, what data you can access, and how to set up a connection.

Written by Kerim Ay

👉 For the full technical reference, read our documentation.

The DatAds MCP (Model Context Protocol) server connects your AI provider or your own system to DatAds so you can query your ad data in real time. Once connected, you can ask questions in natural language and get answers drawn from your actual account, without opening a report or exporting anything.

The Public API serves the same data in standard REST format, for use from your own code.

How the MCP differs from Blink

Blink is DatAds' AI Agent inside the dashboard. It includes an analytical layer: built-in comparisons, context about what the numbers mean, and knowledge of which conclusions to draw.

The MCP does not include that layer. It exposes the data in a format optimised for AI consumption and leaves the analysis to the system you have connected. This is intentional:

if you are embedding DatAds in your own pipeline, you already have your own prompts and models, and a built-in analytical layer would conflict with them.

MCP

Blink

Public API

What it is

Data access for AI providers and external systems

DatAds' AI analyst inside the dashboard

REST access for code-based integrations

Runs inside

Your AI provider or system

The DatAds dashboard

Your code

Authentication

Your DatAds user login

Dashboard session

API key, per client

Credits

No

Yes

No

What you can access

Both the MCP and the Public API expose the following:

  • Clients and workspaces — list the clients your user can see and scope every query to one.

  • Ads and campaign hierarchy — ad accounts, campaigns, ad groups and individual ads, with names, status, platform and format. Search by keyword or filter on any structured field.

  • AI tags, visual descriptions and transcriptions — the enrichment DatAds adds to every creative: what it shows, what it says, and how it is tagged. Combined with performance data, this lets a connected AI reason about why an ad works, not just what the numbers are.

  • Live insights — metrics for any time range, as totals, daily trends, or broken down by ad, campaign, landing page, creative, audience or placement.

  • Reports — read your saved Comparative Analysis, Top Performing, Recently Launched and Testing Log reports and combine their results with metadata and insights.

  • Benchmarks — your historical performance range and the industry benchmark per metric, so a connected AI can tell you whether a number is good.

  • Discovery (coming soon) — search competitor ads, follow brands and read saved inspiration boards.

👉 For the full list of available endpoints and parameters, see the API documentation.

Use cases

  • Querying your data in natural language. Connect your existing AI provider and ask directly: which ads are running, what your ROAS was last month, what your top performers have in common. No setup beyond the connection itself.

  • Embedding DatAds in your own pipeline. If you already run your own AI system, the MCP becomes one data source inside it. Your system handles the reasoning; DatAds supplies enriched creative and performance data.

  • Using a different AI provider. If you prefer not to use Blink inside the dashboard, the MCP gives you access to the same underlying data through whichever provider or model you choose.

How to connect via MCP

The MCP endpoint is https://mcp.datads.io/mcp.

Your credentials (client ID and password) are in the dashboard under the MCP tab, at the bottom left of the sidebar, or directly at app.datads.io/mcp.

Authentication uses your DatAds user login. The connection has access to every client your user can see in the dashboard. Which client a specific request touches is set per call, not per connection.

The exact setup steps depend on your AI provider. Refer to your provider's documentation for the specifics. If your provider asks for token or authorization URLs during setup, contact our support through the chat bubble in the bottom right of your dashboard inside DatAds, and we will provide them.

💡 If your provider is not listed yet. The MCP accepts connections from a whitelist of approved providers and systems. If yours is not on it, contact support. We may enable new providers and custom system connections on request.

Rendering image previews in Claude

Claude can render the actual creatives from your ads. To enable this, a Claude admin needs to go to Settings → Capabilities (claude.ai/admin-settings/capabilities) and add our CDN to the allowlist:

*.z03.azurefd.net

A new chat has to be opened for the change to take effect. Then ask Claude something like:

Pull top ads by spend from DatAds MCP and render the assets in a creative analytics dashboard

How to connect via Public API

Base URL: https://public.api.datads.io/

Authentication: an API key sent as the x-api-key header. Keys are created in the dashboard and are scoped per client. To access multiple clients, use a separate key for each.

Full documentation: public.api.datads.io/docs

To find your API Key, go to:

  • settings -> clients -> "manage"

In your client Settings, look for "API Key"

If you have any questions or would like to share feedback, feel free to reach out to us anytime via the chat widget in the bottom right corner of your dashboard. 💬

Did this answer your question?