Cluster · SEO automation
CLI and MCP for production SEO workflows
gsccli and gacli pull Google Search Console and Google Analytics 4 out of click-heavy UIs and turn them into scriptable infrastructure. Both expose MCP for AI agents, plus traditional CLIs for technical SEO operators who live in the terminal.
Related projects
gsccli
SEO & AnalyticsSenior-grade Google Search Console + Indexing API CLI — real production SEO workflows.
- Stars
- 0
- Forks
- 0
- Version
- v1.2.1
- License
- MIT
npm install -g @nalyk/gsccli
→
gacli
SEO & AnalyticsFull-featured Google Analytics 4 CLI + MCP server — production GA4 automation for humans and agents.
- Stars
- 0
- Forks
- 0
- Version
- v1.1.0
- License
- MIT
npm install -g @nalyk/gacli
→
Why this matters
Production SEO needs what a dashboard does not give you: pagination past the 25 000-row cap, period-over-period comparison, batch URL Inspection, Indexing API auditing, and repeatable automation. Manual GSC or GA4 clicks are fine for a quick look, not for an operation.
gsccli and gacli solve exactly that. Both run on OAuth or Service Account auth, return data in multiple formats (table, JSON, NDJSON, CSV), and expose read-only MCP tools — useful for AI agents that build reports or audit a site without ever needing write access to your Google accounts.
Typical use: bi-monthly SEO audits via script, indexing monitoring after content launches, content-decay reports, period-over-period strategy comparison, private dashboards aggregated from one Google Cloud project. All without touching the UI.
How to start
- 01 Install:
npm install -g @nalyk/gsccliornpm install -g @nalyk/gacli. - 02 Authenticate: OAuth for interactive use, Service Account for CI / scripts.
- 03 Run
gsccli search-analytics query --site ... --date-range last-28dorgacli report --property ... --metric activeUsers. - 04 For Claude / Cursor use: wire the matching MCP server from the install page.
Both tools sit on the official Google APIs with no intermediary. Quota and auth belong to your Google Cloud project.