# 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](https://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:

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

**One-click install:**

<a href="https://cursor.com/en/install-mcp?name=vibeseo-geo&config=eyJuYW1lIjoidmliZXNlby1nZW8iLCJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vZ2VvLW1jcC52aWJlc2VvLmRldi9tY3AifQ=="><img src="https://vibeseo.dev/icons/cursor.svg" width="36" alt="Cursor"></a>&nbsp;&nbsp;<a href="https://insiders.vscode.dev/redirect/mcp/install?name=vibeseo-geo&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fgeo-mcp.vibeseo.dev%2Fmcp%22%7D"><img src="https://vibeseo.dev/icons/vscode.svg" width="36" alt="VS Code"></a>&nbsp;&nbsp;<a href="https://claude.ai/settings/connectors"><img src="https://vibeseo.dev/icons/claude-desktop.svg" width="36" alt="Claude"></a>&nbsp;&nbsp;<a href="https://chatgpt.com/settings/connectors"><img src="https://vibeseo.dev/icons/chatgpt-icon.svg" width="36" alt="ChatGPT"></a>

CLI clients (Claude Code, Gemini CLI, Codex CLI) and manual snippets: see [Supported clients](#supported-clients).

## Quick start

1. Create a VibeSEO account at [vibeseo.dev](https://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](https://vibeseo.dev/agent/geo) 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

| Area | What it covers |
|---|---|
| 🧭 **Status & setup** | Whether a project is configured for GEO, what the account can run, and the state of daily monitoring. |
| ❓ **Topics & questions** | Topics with their market, tracked questions, and the competitors tracked in answers. |
| ⚡ **Checks** | Estimate the cost, collect fresh answers from ChatGPT, Gemini, Google AI Mode and Google AI Overviews, and follow the batch until it settles. |
| 💬 **Answers** | Every collected answer with the brands it mentions, your brand's position, the full text and the sources it cited. |
| 📈 **Visibility analytics** | Visibility, share of voice and position per brand, engine and topic over 7, 30 or 90 days, with competitor comparison. |
| 🔗 **Sources & gaps** | The sites and pages AI answers cite, which brands each page mentions, and the independent pages that name competitors but not you. |
| 🕵️ **Brand perception** | How answers characterise your brand: tone, recurring associations and objections, and the answers behind each. |
| 🤖 **Crawler access** | Whether OpenAI, Perplexity, Anthropic and Google crawlers can reach and read your pages, with a fix per check. |

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:

| | Free trial preview | GEO Pro | SEO + GEO |
|---|---|---|---|
| **Price** | $0 | $189/mo | $299/mo |
| Answer collection | One collection: up to 30 questions, 120 answers | Daily, on all four engines | Daily, on all four engines |
| Reports (visibility, sources, perception, crawler check) | 7 days | ✅ | ✅ |
| Credits per month | — | 15,000 | 15,000 |
| Sites | 1 | 5 | 20 |
| Classic SEO tools ([VibeSEO MCP](https://github.com/sultanlive/vibeseo-mcp)) | — | — | ✅ |

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](https://vibeseo.dev/pricing?tab=geo). 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** — `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](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:

| | Server | Covers |
|---|---|---|
| **VibeSEO** (`dev.vibeseo/vibeseo`) | `https://mcp.vibeseo.dev/mcp` | Keywords, domains, backlinks, site audits, Search Console, content workflow — [sultanlive/vibeseo-mcp](https://github.com/sultanlive/vibeseo-mcp) |
| **AEO/GEO by VibeSEO** (`dev.vibeseo/geo`) | `https://geo-mcp.vibeseo.dev/mcp` | AI answer engines: tracked questions, answers, visibility, cited sources, perception, monitoring — this repo |

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](https://vibeseo.dev/agent/geo), and disconnecting a client revokes its access immediately.

OAuth flow details: [docs/oauth.md](docs/oauth.md).

## Project links

- Product: [vibeseo.dev](https://vibeseo.dev)
- GEO MCP page: [vibeseo.dev/geo-mcp](https://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](https://github.com/sultanlive/vibeseo-geo-mcp/issues)

## License

MIT — see [LICENSE](LICENSE).

---

Built by [@sultanlive](https://github.com/sultanlive). VibeSEO is a hosted platform; this repo is documentation for its public GEO MCP server. Server source is not open.