MCPs / DataLink MCP

Read onlyAccount scopedDisconnect any time

One question.
Every account.

Answering how the month went usually takes a login, an export and a tab for every platform you run — and the totals still disagree. DataLink MCP gives a Busy teammate one read-only path into the advertising, commerce and analytics accounts you choose. Connect a source once, then ask the question in plain English and get the answer from the accounts themselves.

See the sources Schedule an intro

From account to answer

Connect once.
Then brief the teammate.

Choose the sources

You pick the advertising, commerce and analytics accounts she can read. Anything you leave out stays invisible to her.

Add one endpoint

One MCP URL carries every source you connected. There is no second integration to maintain when you add the next platform.

Ask for the work

She reads across the whole connected set at once and answers in plain English, with the numbers coming from the accounts rather than from a spreadsheet somebody kept up.

Sources

Advertising. Commerce.
Analytics.

The catalog carries 12 source types today. Each row says exactly what she can read, in writing, before you grant access — so the decision to connect a source is made with the answer already in front of you.

DataLink MCP / source catalogWhat the teammate can read

Google Ads

Advertising

Spend, impressions, clicks and conversions by campaign

Read only,
on the accounts you picked.

Permission

It reads, and that is all

Every tool in the source catalog is a read. Nothing here can change a bid, spend a dollar, edit a listing or send anything — so the worst case is an answer you disagree with.

Scope

Bound to the signed-in account

The endpoint is the same URL for everyone. What comes back through it depends on who signed in and which sources that account connected, so nobody inherits access by knowing the address.

Revocation

Disconnect any source

Each source keeps its own connection state and can be cut on its own. You can pull one platform back today and leave the rest working.

One endpoint

Put the data where
the work already happens.

Add one endpoint to ChatGPT, Claude or Claude Code — paste, sign in, approve. The data shows up inside the AI subscription your team already pays for, so nobody has to learn another console to ask a question.

ChatGPT

Add a custom connector, paste the endpoint, then approve access.

Claude

Add a custom connector in Settings, then sign in and approve access.

Claude Code

Add the endpoint from the terminal, finish sign-in, then confirm with /mcp.

What the teammate can ask

Questions that cross systems,
answered in one pass.

01
How are my ads performing this month, and where is the waste?
02
What is my blended ROAS across every channel against total sales?
03
Is my traffic converting, and which products are winning?
04
Which channel actually paid for itself last month?

Agent first

DataLink MCP is the equipment.
The Busy teammate is the operator.

Your side of it stays small: connect the sources, hold the endpoint, pay the bill. The teammate uses that access to do the work — the weekly read, the channel comparison, the question somebody asks on Thursday — and brings the answer back.

Schedule an intro