Server data from the Official MCP Registry
Remote SEO/GEO MCP: Search Console, keyword research, backlinks, competitor & on-page audits.
About
Remote SEO/GEO MCP: Search Console, keyword research, backlinks, competitor & on-page audits.
Remote endpoints: streamable-http: https://mcp.visibly-ai.com/mcp
Security Report
Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry. 1 finding(s) downgraded by scanner intelligence.
6 tools verified · Open access · 1 issue found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
Permissions Required
This plugin requests these system permissions. Most are normal for its category.
How to Connect
Remote Plugin
No local installation needed. Your AI client connects to the remote endpoint directly.
Add this to your MCP configuration to connect:
{
"mcpServers": {
"io-github-antonioblago-visibly-ai": {
"url": "https://mcp.visibly-ai.com/mcp"
}
}
}Documentation
View on GitHubFrom the project's GitHub README.
Claude Code — SEO Agency & Freelancer Starter
A batteries-included Claude Code blueprint for SEO freelancers and agencies. Wire up the Visibly AI MCP, get ready-made slash commands for the full client workflow — Status-Quo → Potential Analysis → Offer → CI-compliant PDF — and a smart hook that nudges Claude toward real SEO data instead of guessing.
Built and battle-tested by Antonio Blago — SEO Freelancer & creator of the Neuro-SEO System®.
Why this exists
SEO consulting is the same five jobs over and over: pull the real ranking data, map it against the client's keyword set, quantify the opportunity, turn that into an offer, and ship a presentable PDF. Claude Code can do all of it — if you give it the data sources, the methodology, and the guardrails.
This repo packages exactly that — and it runs without any API key. Install it and the bundled .mcp.json connects to the Visibly AI MCP keyless, giving you 8 free tools (keyword classification, SEO checklists, URL-structure analysis) plus the full local methodology; bring your own Search Console export and the entire Status-Quo → Potential → Offer → PDF chain runs offline. Add a Visibly AI key when you want the data engine on tap — live GSC/GA at 0 credits, keywords, backlinks, competitors and on-page audits through one MCP. Free by default, pro when you need it.
✨ What's inside
| Piece | What it does |
|---|---|
.mcp.json | Pre-wired Visibly AI MCP connection — keyless by default (8 free tools); add a key to unlock live GSC, keywords, backlinks, competitors, on-page audits, crawling. |
/visibly-seo-status-quo | Maps a client's live organic visibility: GSC × target keywords, classification, quick wins. |
/visibly-seo-potential | Potential analysis: empirical CTR model → realistic 12-month targets → traffic, lead & ROI math. |
/visibly-seo-offer | Drafts a tailored, phased SEO consulting offer from your analysis + client context. |
/visibly-seo-pdf-build | Turns any analysis script into a clean, brand-compliant PDF. |
| SEO hook | A UserPromptSubmit hook that detects SEO intent and steers Claude to Visibly AI MCP tools instead of generic scraping. |
CLAUDE.md | A project-instruction template encoding the whole workflow + folder conventions. |
docs/ | The methodology written out: workflows, the CTR model, and best practices. |
🚀 Quickstart
There are two ways to use this — pick one.
Option A — Install as a plugin (fastest)
/plugin marketplace add AntonioBlago/claude-code-seo-starter
/plugin install seo-starter@antonioblago
You get the /visibly-seo-status-quo, /visibly-seo-potential, /visibly-seo-offer, /visibly-seo-pdf-build commands, the
auto-invoked SEO skills, the SEO-intent hook, and the keyless Visibly AI MCP — wired in.
No key needed to start — approve the MCP server and you have the 8 free tools plus
the full local workflow.
Want the full data engine (live GSC, keywords, backlinks, on-page)? Add a Visibly AI key — grab one at visibly-ai.com (~30s, no card), then connect it once (resolves at write time, stays out of git):
claude mcp add --transport http visiblyai https://mcp.visibly-ai.com/mcp --header "Authorization: Bearer lc_xxxxxxxxxxxxxxxx"
Restart with /reload-plugins if needed. See docs/setup.md for the
pro tier, Google-OAuth (0 credits) and optional DataForSEO wiring.
Option B — Clone the template
Use the full repo (docs, PDF template, setup script) as a project scaffold.
1. Prerequisites
- Claude Code installed (
npm install -g @anthropic-ai/claude-code) - (Optional) a Visibly AI account for the pro tier — sign up free. Not required: the starter runs keyless.
- Python 3.11+ (only needed for the PDF / data-crunching helpers)
2. Get the blueprint
# Use it as a GitHub template, or just clone:
git clone https://github.com/AntonioBlago/claude-code-seo-starter.git
cd claude-code-seo-starter
3. (Optional) add your Visibly AI key
Skip this for the free tier — the keyless .mcp.json already works. To unlock the
full data engine, create a free account at visibly-ai.com,
copy your lc_... key, and connect it once (resolves at write time, stays out of git):
claude mcp add --transport http visiblyai https://mcp.visibly-ai.com/mcp --header "Authorization: Bearer lc_xxxxxxxxxxxxxxxx"
Full tier breakdown, Google-OAuth (live GSC/GA at 0 credits) and optional DataForSEO
wiring: docs/setup.md.
4. Launch
claude
On first run, Claude Code will ask you to approve the Visibly AI MCP server. Approve it, then try:
/visibly-seo-status-quo example.com
That's it. On the free tier, feed a GSC export to the Python templates; with a key, data is pulled live. Either way you're running the full SEO workflow.
🔁 The workflows
Each slash command corresponds to one phase of a real client engagement. They chain:
/visibly-seo-status-quo <domain> → /visibly-seo-potential <domain> → /visibly-seo-offer <domain> → /visibly-seo-pdf-build <script.py>
(where do we (what's the upside, (what should the (hand the client a
rank today?) in clicks & €?) client buy?) polished PDF)
Full methodology is documented in docs/workflows.md.
📈 The CTR model
The potential analysis is only as good as its click-through-rate curve. This repo ships the Keyword Study 2026 — CTR by position from first-party Google Search Console data (1.3M keywords, 94 domains) — instead of the inflated textbook numbers most templates still use.
The differentiator: the curve is intent-aware. A navigational keyword at position 1 earns ~8.9% CTR; an informational one ~3.2%. Forecasting with one blended number quietly mis-states the upside. See docs/ctr-model.md for the full intent-by-position table and the Python to apply it. Honest inputs → defensible forecasts → offers that survive scrutiny.
🎨 Customise it
Everything is plain Markdown and shell — fork and adapt:
- Branding — edit
CLAUDE.mdandtemplates/pdf_example.pywith your colours, fonts, contact block. - Data source — keyless by default; add a Visibly key for the full engine, or wire your own (GSC export → Python templates, DataForSEO, GA4, Ahrefs…) in
.mcp.json. Seedocs/setup.md. - Workflows — the
.claude/commands/*.mdfiles are the workflows. Rewrite them in your own words. - Guardrails — extend
.claude/hooks/seo-check.shwith your own keyword triggers.
See docs/setup.md for a deeper walkthrough and docs/best-practices.md for the hard-won lessons.
📂 Repo layout
claude-code-seo-starter/
├── .claude-plugin/ # makes this repo an installable plugin + marketplace
│ ├── plugin.json # plugin manifest
│ └── marketplace.json # marketplace catalog (one repo = both)
├── .mcp.json # Visibly AI MCP connection — keyless (free tools); add key for pro
├── server.json # MCP-registry manifest (publish via mcp-publisher)
├── .env.example # copy → .env — optional key + separate data sources
├── CLAUDE.md # project instructions Claude reads on every run
├── .claude/
│ ├── commands/ # /visibly-seo-status-quo /visibly-seo-potential /visibly-seo-offer /visibly-seo-pdf-build
│ ├── skills/ # auto-invoked SEO skills (status-quo, potential, offer, pdf)
│ ├── hooks/ # seo-check.sh + hooks.json — SEO-intent nudge
│ └── settings.json # hook registration + sane permissions (clone mode)
├── docs/
│ ├── setup.md # detailed setup
│ ├── workflows.md # the 4-phase methodology
│ ├── ctr-model.md # empirical CTR curve
│ ├── folder-structure.md # client knowledge base + CI base conventions
│ ├── best-practices.md # lessons learned
│ └── promote.md # discoverability checklist (registry, awesome lists)
├── templates/
│ ├── ci/ # CI base — brand.py (constants) + CI.md (reference)
│ ├── client-template/ # copy → clients/<domain>/ (CLAUDE.md + _knowledge/)
│ ├── status-quo-template.md # fill-in status-quo skeleton (classification, quick wins)
│ ├── potential-template.md # fill-in potential skeleton (deltas, clusters, ROI scenarios)
│ ├── offer-template.md # fill-in offer skeleton (phases, pricing, ROI, terms, CTA)
│ └── pdf_example.py # minimal CI-PDF starter (fpdf2)
└── scripts/
└── check-setup.sh # verify your env is wired correctly
🤝 Contributing
PRs welcome — see CONTRIBUTING.md. Found this useful? A ⭐ helps others find it.
📜 License
MIT — see LICENSE. Use it commercially, fork it, ship it for your own clients.
💬 Want help setting it up?
If you'd rather have this dialled in to your agency's workflow — or want to talk SEO, Claude Code, or vibe coding — book a consultation.
Reviews
No reviews yet
Be the first to review this server!
More Developer Tools MCP Servers
Git
Freeby Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
Fetch
Freeby Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
Toleno
Freeby Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
mcp-creator-python
Freeby mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.
MCP Marketplace
Freeby mcp-marketplace · Developer Tools
Search and install MCP servers from inside your AI client.
MarkItDown
Freeby Microsoft · Content & Media
Convert files (PDF, Word, Excel, images, audio) to Markdown for LLM consumption
