ClimbPast is a hosted MCP server giving any AI agent (Claude, Claude Code, ChatGPT, Cursor) read and edit access to Google Analytics 4, Google Search Console, and Google Tag Manager through a single API key, free for 3 days then $10 per month. 29 tools. Unlike the free local MCP servers, which are read-only and require your own Google Cloud project, ClimbPast can register GA4 custom dimensions and key events, submit sitemaps, and edit and publish Tag Manager containers. Access is read-only by default; write is a separate opt-in, and you can disconnect Google or revoke your API key in one click at any time.
The MCP server that writes, not just reads
One API key. Read and edit GA4, Search Console, and Tag Manager.
Free MCP servers can read your analytics. ClimbPast can fix it. 29 tools across GA4, Search Console, and Tag Manager. 3 days free, then $10/mo.
Read-only by default. Write access is a separate opt-in you approve explicitly.
Works with Claude, ChatGPT, Cursor, and any MCP client
Real answers from your GA4 and Search Console data
Connects to
The shortcut that's also safer
Sign in with Google. Your AI is connected.
ClimbPast turns one secure Google sign-in into an MCP connection any AI agent can use. No cloud consoles, no config surgery, no credentials to babysit. Connect once, copy one key, and your agent is answering questions about your traffic in two minutes.
One-click Google OAuth
Connect through Google's own sign-in flow, the same one you use everywhere else. ClimbPast is a verified Google app. The default grant is read-only; edit access is a separate opt-in.
Your AI holds a cp_ key, not your credentials
Your AI tool gets a short, revocable ClimbPast key. Your Google sign-in stays with ClimbPast, encrypted, and never travels to your agent's context.
Revoke in one click
From your dashboard you can disconnect Google or rotate a key instantly. The old key stops working the moment you click.
How it works
Three steps from signup to your first answer.
Connect once, ask anything. No config headaches, no permanent credentials floating around.
Connect Google
Sign in with Google through ClimbPast's verified OAuth app. Read-only to start, so the first consent screen stays minimal. Your credentials stay with ClimbPast, encrypted, and your AI agent gets a short revocable cp_ key instead.
Copy your cp_ key into your AI tool
Your dashboard shows a one-line config snippet. Paste it into Claude Code, claude.ai, Cursor, or any MCP-compatible client. Your AI is now connected to your real data.
{
"mcpServers": {
"climbpast": {
"type": "http",
"url": "https://climbpast.com/api/mcp",
"headers": {
"Authorization": "Bearer cp_live_xxxxxxxxxxxx"
}
}
}
}Ask questions in plain English
Ask which pages rank for your target keyword, what changed in your traffic this week, or where your conversions are actually coming from. Your AI queries ClimbPast, ClimbPast queries Google, and you get an answer.
What you can ask
Real questions. Real Google data. No dashboards.
Register a custom dimension for plan_tier and mark sign_up as a key event.
Add a GTM tag that fires purchase on the thank-you page, then publish it.
Which of my GA4 events look like conversions but are not marked as key events?
Why did signups drop last week?
Which pages get the most organic clicks but the fewest conversions?
How much traffic did ChatGPT and Perplexity send me last month?
Has Google actually indexed my new pricing page yet?
Re-submit my sitemap, I just published 40 new pages.
FAQ
Questions, answered.
What is ClimbPast?
ClimbPast is a hosted MCP server giving any AI agent read and edit access to Google Analytics, Search Console, and Tag Manager through one API key. Your agent can query your traffic and rankings and, with write access enabled, fix your tracking setup instead of just reporting on it.
Is there not a free MCP server for this already?
Yes, and we would rather you hear it from us. Google publishes a free official GA4 MCP server, and there are good community-built ones for Search Console. They run locally, so you set up a Google Cloud project, create your own OAuth credentials, and run a separate server for each source on every machine you work from. ClimbPast is hosted: one Google sign-in covers GA4 and Search Console together, with nothing to install. It also answers two things the free servers do not: how much traffic came from AI assistants like ChatGPT, Perplexity, Claude and Gemini, and whether Google has actually indexed a given URL. If you only need GA4 and you are happy running a local server, use Google's. It is genuinely good.
How does my AI get access without my Google login?
You sign in once with Google OAuth through ClimbPast's verified app, which requests read-only scopes by default. ClimbPast stores your tokens encrypted and gives your AI agent a short cp_ key. The agent uses that key to call Google's APIs through ClimbPast's MCP server. Your agent never sees your Google credentials, and you can revoke access from your dashboard or from Google's security page any time.
Which AI tools does it work with?
Claude Code, claude.ai custom connectors, ChatGPT connectors, Cursor, and any client that supports the Model Context Protocol (MCP). You copy one config snippet with your cp_ key and the MCP server URL.
Can it write to my Google data?
Only if you turn it on. New connections are read-only. Enabling write access in Settings triggers a separate Google consent, after which your agent can create and edit GA4 custom dimensions and key events, submit sitemaps, and edit and publish Tag Manager containers. Two limits worth knowing: nothing can delete a GA4 custom dimension or key event, and Search Console has no write surface beyond sitemaps, so no tool can change rankings or content. Tag Manager edits are versioned, so a bad change is revertible from GTM history.
Do you store my analytics data?
Your OAuth tokens are stored encrypted, along with cached weekly reports and insights for your workspace. Everything else is fetched from Google on demand when your AI asks, not warehoused.
What does it cost?
Ten dollars a month. Cancel any time.
How do I revoke access?
From your ClimbPast dashboard you can disconnect Google or delete an API key in one click. You can also revoke from Google's own security page. Either way, access stops immediately.