API and MCP · uncoverflow

key per user —
sees every assigned client

read-only

over MCP —
actions stay in the backend with approval

destinations behind the ingest API —
one call, every platform

MCP server

Every report as a tool, in every assistant.

MCP is the open protocol Claude, ChatGPT and developer tools use to reach data sources. uncoverflow is one of them — with the same functions the built-in chat uses.

Returns and revenueROAS per channel, ad spend, clicks and CPC, daily series over any date range, previous-period comparison.
Journeys and assistsPurchase paths, channels involved, bridge-page funnels, calls with their source, bookings, lead values with the invoice share.
DiagnosticsSearch terms with negative-keyword candidates, quality scores, device and hour breakdowns, Meta segments, Merchant Center reports, system status.
Evidence includedEvery answer carries the raw data of the tool call. What the assistant says can be expanded and checked.

Access

Three ways in, one way out.

Read through MCP, send through the ingest API, forward through the webhook. All keyed, all separated per client.

Three ways in, one way out — each with a key, each separated per client.

User keys

One key per person, bound to their clients. An agency queries all its clients with it without handing out a single client key. Revocable in seconds.

Ingest API

Server-to-server events without a browser: one call, the same idempotency, the same 18 destinations. For POS systems, apps and anything that isn’t the web.

Webhook destination

Every event, signed, to Zapier, Make, n8n or a CRM — with a field allowlist so nothing leaves that shouldn’t.

What deliberately isn’t possible

Reading, yes. Writing only with approval.

Nothing about campaigns, budgets or audiences can be changed through the API. Every action runs in the backend with a dry run and click approval — not a technical gap but the rule we follow with advertising budgets.

No plaintext personal dataEmail and phone exist only as hashes, in the ad platforms’ format. The API returns nothing else.
Clients strictly separatedEach key sees exactly the clients it is assigned to. A foreign slug doesn’t answer with an error — it doesn’t answer at all.
Actions through our platform appsThird parties triggering actions through our Meta and TikTok integrations is planned. It depends on the platforms’ approval procedures, which is why it sits on the roadmap, not on the price list.

Common questions

Answered briefly.

What does the API cost?

Nothing extra. MCP access, user keys and the ingest API are part of the plan.

Which assistants work?

Anything that speaks MCP over Streamable HTTP: Claude Desktop and Claude Code, ChatGPT with connectors, Cursor, your own agents. Endpoint and key are on the chat page in the backend.

Can I build my own reports with it?

Yes. The tools return structured data; an assistant or a script can turn it into reports, alerts or dashboards. For raw data at scale there is the warehouse export as well.

Related.

Ask your data →

The same toolbox, built into the backend — with expandable evidence.

For agencies →

All clients in one login, user keys, reports in your brand.

Integrations →

Where we send, where orders and calls come from.

Let's talk for 30 minutes.

We look at your store live and show you which orders slip through your current setup — using your real numbers.

Book a demo Or start with the welcome gift: a free keyword analysis →

Reply within 24 hours on business days · conversations in German or English · no lock-in, cancellable monthly