AEO/GEO by VibeSEO

AEO/GEO by VibeSEO — MCP server

Model Context Protocol server for AI search visibility: see how ChatGPT, Gemini, Google AI Mode and Google AI Overviews answer your questions, and whether they mention your brand.

Connect Claude, ChatGPT, Cursor, VS Code, or a CLI client to the VibeSEO GEO server. Then ask which brands AI answers name for the questions you track, how you compare with competitors, which pages those answers cite, and run fresh checks when you need them.

• Server URL: https://geo-mcp.vibeseo.dev/mcp
• Transport: Streamable HTTP
• Auth: OAuth 2.1 with PKCE, scope mcp:tools
• Landing & setup: vibeseo.dev/geo-mcp
• Registry name: dev.vibeseo/geo

Install

The GEO server is a remote, OAuth-secured server. Add this to your client's MCP config:

{

"mcpServers": { "vibeseo-geo": { "url": "https://geo-mcp.vibeseo.dev/mcp" } } }

One-click install:

CLI clients (Claude Code, Gemini CLI, Codex CLI) and manual snippets: see Supported clients.

Quick start

1. Create a VibeSEO account at vibeseo.dev and set up GEO for a project in the web onboarding (brand, competitors, topics and the first questions).
2. Open the GEO setup page and follow the link for your client.
3. Authorize with OAuth when your client opens the consent screen.
4. Ask your assistant about your brand in AI answers, in natural language.

A project is configured once in the web app. If it is not set up yet, the server says so and returns the setup link instead of guessing. After that, everything — including new topics and questions — works from chat.

What you can do from chat

The live tool set evolves. For the exact, up-to-date list, run tools/list against https://geo-mcp.vibeseo.dev/mcp.

How checks work

• Status first. The assistant reads the project status before anything else.
• Estimate, then start. A check is previewed for cost and eligibility before it runs. Each question on each engine costs one credit.
• Answers arrive in minutes. Collection is asynchronous: a check returns a batch id, and answers usually arrive within one to ten minutes. The assistant polls the batch until no run is pending.
• Read, compare, act. Answers, the overview, competitor comparison, cited sources and gaps come from the same data the VibeSEO app shows.

Plans & access

The tools collect answers from AI engines on your behalf, so they need a VibeSEO account with GEO access:

One credit is one question, on one AI engine, for one day — for example, 25 questions × 4 engines × 30 days = 3,000 credits. Current plans: vibeseo.dev/pricing. If a request needs something your plan does not include, the tool result explains what is missing and links to the pricing page.

Supported clients

• Claude (web & desktop) — Connectors page or claude_desktop_config.json
• ChatGPT — custom MCP connector with OAuth
• Cursor — one-click install via deeplink, or ~/.cursor/mcp.json
• VS Code — one-click install via deeplink, or .vscode/mcp.json
• Claude Code (CLI) — claude mcp add --transport http vibeseo-geo https://geo-mcp.vibeseo.dev/mcp
• Gemini CLI — extension: gemini extensions install https://github.com/sultanlive/vibeseo-geo-mcp, or server only: gemini mcp add --transport http vibeseo-geo https://geo-mcp.vibeseo.dev/mcp
• Codex CLI — codex mcp add vibeseo-geo --url https://geo-mcp.vibeseo.dev/mcp
• Generic HTTP MCP client — point at the URL, let it complete OAuth discovery

Full per-client install instructions: docs/setup.md.

Example prompts

Visibility check

"How visible is my brand in ChatGPT answers this month, and where did we lose ground?"

→ The assistant reads the 30-day overview and the competitor deltas: mention rate, average position, and the topics that carry the change.

Source gaps

"Which pages do AI answers cite for my topic that mention competitors but not us?"

→ The assistant lists the cited pages with the brands each one mentions and how many answers cite it.

Fresh answers

"Re-check my five comparison questions on ChatGPT and Gemini and tell me when the answers are in."

→ The assistant previews the cost, starts the batch, follows it until it settles, and summarises which answers mention you.

Relationship to the VibeSEO MCP server

VibeSEO runs two MCP servers on the same account and the same OAuth sign-in:

Connect one or both. The GEO server keeps a focused catalogue so an assistant that only needs AI-search tracking is not handed SEO tools.

Authorization

Auth is OAuth 2.1 with PKCE. Your assistant gets a token scoped to mcp:tools, tied to your VibeSEO account. Authorized clients are listed under "Connected clients" on the GEO setup page, and disconnecting a client revokes its access immediately.

OAuth flow details: docs/oauth.md.

Project links

• Product: vibeseo.dev
• GEO MCP page: vibeseo.dev/geo-mcp
• MCP server: https://geo-mcp.vibeseo.dev/mcp
• OAuth issuer: https://api.vibeseo.dev
• Issues: github.com/sultanlive/vibeseo-geo-mcp/issues

License

MIT — see LICENSE.

---

Built by @sultanlive. VibeSEO is a hosted platform; this repo is documentation for its public GEO MCP server. Server source is not open.