mcp server
io.github.archievi/climbpast
Read and edit GA4, Search Console and Google Tag Manager from any MCP client. 29 tools.
Description as published by the maintainer. Source
- version 1.0.0
- active
- retrieval
active — Most recent push to the repository was 2026-08-05. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| GitHub stars | 0 | Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. | cumulative, all time | GitHub | |
| Last commit | 2026-08-05 | Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. | point in time | GitHub | |
| Open issues | 0 | Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. | as of fetch | GitHub | |
| Latest published version | 1.0.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-08-05 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-08-05 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| repository status | active | The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. | as of fetch | GitHub |
Where to get it
Related, by what their authors tagged them
-
SEO Performance MCP
— last commit 2026-06-08, shares ga4, google-search-console
Per-URL SEO verdicts from GSC, GA4, Matomo, Clarity, AI citations: refresh/expand/merge/kill.
-
Markifact: AI Performance Marketing
— last commit 2026-08-05, shares google-analytics
AI marketing agent for Google Ads, Meta, GA4, TikTok, LinkedIn, Shopify, HubSpot and more.
-
io.github.AINative-Studio/ainative-gtm-mcp
— last commit 2026-08-01, shares google-analytics
Full Google Ads, Analytics & Tag Manager lifecycle MCP for AI agents — 57 tools.
-
io.github.avansaber/seo-monster
— last commit 2026-06-20, shares ga4
SEO MCP over Search Console, GA4, PageSpeed Insights, Cloudflare, IndexNow, CrUX, technical-SEO.
-
com.cituna/cituna-mcp
— last commit 2026-08-04, shares google-search-console
Track how 6 AI engines cite your brand, daily, with live Google Search Console.
-
Rampify
— last commit 2026-06-23, shares google-search-console
SEO MCP server: crawl your site, find AI-visibility gaps, and ship the fix from your coding agent.
-
Google Search Console
— last commit 2026-04-23, shares google-search-console
Google Search Console MCP server: SEO audits, performance queries, URL inspection, indexing checks.
-
Librecrawl — Technical SEO Audit MCP Server
— last commit 2026-07-28, shares google-search-console
Self-hosted technical SEO audit MCP. 50+ checks, WAF detection, ephemeral. Built on LibreCrawl.
-
Google Search Console MCP Server
— last commit 2026-08-02, shares google-search-console
Google Search Console for AI agents: search analytics, sitemaps, URL inspection.
These share tags the maintainers applied themselves, such as ga4, google-search-console, google-analytics. Common tags like "mcp" or "ai" are ignored for this: agreeing with six hundred other projects is not a similarity.
This is not a recommendation and not a test result. It is a map of what the authors said their work is about.
How the author describes it
Topics the maintainer set on GitHub: ai, claude, ga4, google-analytics, google-search-console, google-tag-manager, mcp, mcp-server, model-context-protocol.
Bring your own setup
We take apart real AI setups every week and show what broke, what cost too much, and what the trace actually said. If you run agents on real work, that is where the useful conversation is.
Join ZBS AI Practice Lab