Live marketing data for AI agents · MCP

Your marketing data,
docked to your AI agents.

Connect Search Console, GA4 and your ad accounts — Google, Meta, X — once. Dockhouse serves live numbers to claude.ai, Claude Code, Codex, VS Code — anything that speaks MCP — through one URL. Diagnose drops, find wasted spend, draft fixes. Real data, not guesses.

You're in the queue. We onboard in small cohorts — you'll hear from us.

Private beta: 20 seats · read-only scopes · free during beta

claude.ai — with Dockhouse connected
gsc_search_analytics — via mcp.dockhouse.ai/gsc · 28d vs prev
Three pages account for 82% of the drop:
/pricing−41% clickspos 3.2 → 6.8
/blog/seo-audit−27% clickspos 5.1 → 9.4
/templates−14% clickspos 2.8 → 4.1
Want me to pull the queries behind /pricing and draft the fix list?
your connectors
01 mcp.dockhouse.ai/gsc connected
02 mcp.dockhouse.ai/ga4 connected
03 mcp.dockhouse.ai/ads coming soon
04 mcp.dockhouse.ai/meta coming soon
05 mcp.dockhouse.ai/x coming soon
Works with anything that speaks MCP claude.ai Claude Code Codex Cursor VS Code your own agent
Use cases

Ask like you'd ask a senior analyst.

Live context from your accounts — not last month's export, not a hallucination. Your agent answers with numbers, ranks what matters by impact, and drafts the fix.

Why did my leads get more expensive this month, and what should I fix first?

Pulls cost, conversions and search terms; ranks the causes by € impact; returns a prioritized fix list — not a dashboard screenshot.

google ads · soon
Which search terms are burning budget with zero conversions?

Finds loose-match queries eating spend and drafts the negative-keyword list, sorted by monthly waste recovered.

google ads · soon
Why did clicks drop after the core update?

Compares pages, queries and positions across any window; isolates which pages and terms actually moved, and by how much.

search console · live
Where does my traffic actually convert — and where does it bounce?

Crosses sources, landing pages and conversions in GA4; answers with rates and absolute numbers, not vibes.

ga4 · live
Draft my Monday report: traffic, spend, anomalies, one paragraph each.

Pulls every connected account in one conversation and writes the summary you'd otherwise assemble from five tabs.

cross-connector
Pause everything below 1.5 ROAS in the last 14 days.

The end game: your agent proposes the change, you see the exact diff, you approve or deny. Writes only ever ship gated.

writes · roadmap
How it works

Three steps. The third one is just talking.

Dockhouse is the OAuth, the token vault and the MCP endpoint — so your agent can be just an agent, and you never touch a credentials file again.

01 — CONNECT

One OAuth click per account

Sign in with Google, approve read-only access, done. Tokens are encrypted at rest, refreshed automatically, and revocable from both sides at any time.

● google account connected — scopes: read-only
02 — PLUG IN

Copy your connector URL

Every connector is a standard MCP endpoint over HTTPS. In claude.ai: Settings → Connectors → add custom connector. CLI agents get a paste-ready snippet.

https://mcp.dockhouse.ai/gsc
03 — ASK

Real numbers come back

Your agent calls Dockhouse; Dockhouse calls Google with your token. Nothing invented, nothing scraped, nothing cached beyond the conversation.

"which queries lost clicks since the core update?"
Connectors

Every account you run, one URL.

Curated connectors for search, analytics and paid media — each tool designed for agent use, not a raw API dump.

SC
live

Google Search Console

Queries, pages, CTR and position over any window. Indexing status, sitemap health, URL inspection — your organic picture, on demand.

gsc_search_analyticsgsc_inspect_url gsc_list_sitesgsc_sitemaps_list gsc_sitemaps_submit
OAuth only — connects in one click
GA
live

Google Analytics 4

Traffic sources, page metrics, conversions and realtime — plus free-form report queries when the question doesn't fit a preset.

ga4_run_reportga4_traffic_sources ga4_page_metricsga4_conversions ga4_realtimega4_list_properties
OAuth only — connects in one click
AD
coming soon

Google Ads

Campaigns, search terms, keywords and budgets — the wasted-spend goldmine. Read-only first; writes only ever behind explicit approval.

ads_list_campaignsads_search_terms ads_keywordsads_account_summary
after Google's API access review — beta members first
M
coming soon

Meta Ads

Campaigns, ad sets, spend and insights across Facebook and Instagram — the other half of most paid budgets.

meta_list_campaignsmeta_adsets meta_insightsmeta_account_summary
after Meta App Review
X
coming soon

X Ads

Campaigns, promoted posts and spend analytics — for the budgets still riding the timeline.

x_list_campaignsx_analytics x_account_summary
after X Ads API access
?
your call

Something missing?

Bing, LinkedIn, TikTok, GoHighLevel — tell us what you run. Beta members set the order of arrivals.

request_a_connector
On the roadmap

Reads today. Writes behind a gate.

Dockhouse ships read-only — your agent can see everything and change nothing. That's not a limitation — it's the right order of operations for anything touching live ad accounts.

When write actions arrive, they arrive like this: your agent proposes, you see the exact before/after, you approve or deny. Every write logged. Every write reversible. Nothing executes silently — not once, not ever.

proposed change — google ads concept preview
Add 3 negative keywords
est. waste recovered: €212/mo
"free seo tools" · 1.2k impr · 0 conv · €118/mo
"seo jobs remote" · 840 impr · 0 conv · €61/mo
"what is serp" · 512 impr · 0 conv · €33/mo
every write logged · one-click rollback
Security

Your accounts stay yours.

Read-only by design, encrypted by default, revocable in one click. These are commitments, not features:

Read-only

Minimum scopes, requested per connector. Write access doesn't exist today — and will only ever ship approval-gated.

Encrypted

Refresh tokens are envelope-encrypted at rest. Access tokens live only in your session's isolated runtime.

Never warehoused

Your data passes through to your agent. We don't store it, resell it, or train on it. Ever.

Revocable

Disconnect deletes the token here and revokes it at Google. Built in the EU, hosted on Cloudflare's edge.

FAQ

Fair questions.

What's an MCP connector?
MCP (Model Context Protocol) is the open standard AI agents use to call external tools. A Dockhouse endpoint is a standard MCP server over HTTPS — claude.ai, Claude Code, Codex, Cursor and VS Code all speak it natively. To your agent, your Search Console account becomes a set of tools it can call mid-conversation, with live numbers coming back.
Do I need Claude Code or anything technical?
No. In claude.ai it's Settings → Connectors → Add custom connector → paste your Dockhouse URL — that works on every claude.ai plan, including free. If you do live in a terminal, there's a paste-ready snippet for Claude Code, Codex and VS Code instead.
Can it change my campaigns?
Not today — every scope is read-only, on purpose. Write actions (adding negatives, pausing keywords, shifting budgets) are on the roadmap, and they will only ever ship diff-gated: your agent proposes, you see the exact before/after, you approve or deny, everything is logged and reversible. A service holding your ad accounts doesn't get to move fast and break things.
Where do my tokens live? Do you see my data?
Your OAuth tokens are stored encrypted and used for exactly one thing: calling Google on your behalf when your agent asks. Query results stream through to your agent — we don't warehouse your analytics, don't resell anything, and don't train on your data. Disconnecting revokes the token at Google, not just here.
What does it cost?
Nothing while in beta. Paid plans will come later, priced for individuals and small teams — honest, and nowhere near the $79/month the incumbents charge for read-only data.
Why hosted? Couldn't I run something like this myself?
You could — Dockhouse grew out of a self-hosted gateway. The hosted version exists so your connectors work from claude.ai on any device (including your phone), survive laptop reboots, need zero setup, and are one URL to share across a team. You bring the agent; Dockhouse brings everything else.
When do the ads connectors arrive?
In review order: Google Ads first (Google's API access ladder), then Meta Ads (Meta App Review) and X Ads (X Ads API access) — every ad platform makes serious tools climb an approval ladder, and we climb them rather than shipping around them. Beta members get each connector first.
Private beta

Get early access.

We onboard in small cohorts so early feedback actually shapes the product. Twenty seats in the first cohort — free, read-only, and yours to keep if it earns a place in your workflow.

You're in the queue. We onboard in small cohorts — you'll hear from us.

beta status: open · first cohort: 20 seats