# VibeSEO MCP server

> Run keyword research, site audits, Search Console analysis, backlink checks and content workflow from your AI assistant.

- Listing: https://mcp.tc/i/vibeseo
- Connect: use the server's own URL `https://mcp.vibeseo.dev/mcp` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: OAuth sign-in
- Category: [Marketing & SEO](https://mcp.tc/c/marketing-seo)
- Vendor: VibeSEO
- Homepage: <https://vibeseo.dev/mcp>
- Docs: <https://vibeseo.dev/docs/mcp>
- Repository: <https://github.com/sultanlive/vibeseo-mcp>

## About

VibeSEO connects an assistant to the VibeSEO platform for SEO work. It covers keyword research (volumes, difficulty, intent, related and question keywords), domain analysis, site audits, Google Search Console summaries, competitive keyword gaps and location lookups. Backlink data and a content workflow (ideas, drafts, approvals, scheduling) are available on the Pro plan.

It runs as a hosted Streamable HTTP endpoint at https://mcp.vibeseo.dev/mcp. Sign-in uses OAuth 2.1 with PKCE and the mcp:tools scope. A VibeSEO account on a trial or paid plan is required, and credits meter calls that use paid data providers or AI generation.

## What it can do

- Research keywords with volume, CPC, difficulty and intent
- Analyze domains: top keywords, top pages and traffic history
- Start site audits and list prioritized issues
- Read Search Console top queries, pages and trends
- Run competitive overviews and keyword gap analysis
- Inspect backlink profiles and referring domains (Pro)
- Generate, approve and schedule content drafts (Pro)

## Example prompts

- "Find comparison keywords for my invoicing app that are realistic to rank for."
- "Audit my project and tell me what to fix before publishing more articles."
- "Show my top Search Console queries and which ones dropped this month."
- "Show ready posts, generate the next draft, and schedule the strongest one."

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http vibeseo https://mcp.vibeseo.dev/mcp
```

2. Start Claude Code, type `/mcp`, pick **vibeseo** and choose **Authenticate**. A browser window opens for the VibeSEO sign-in.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**.

2. Name it **VibeSEO** and paste this URL:

```url
https://mcp.vibeseo.dev/mcp
```

3. Click **Add**, then **Connect**, and sign in when VibeSEO asks.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=VibeSEO&connectorUrl=https%3A%2F%2Fmcp.vibeseo.dev%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://mcp.vibeseo.dev/mcp` and click **Add**.

3. Click **Connect** and sign in when VibeSEO asks.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, go to **Plugins**, select **+**, then **Add custom MCP server**.

2. Enter a name for the server.

3. Under **Connection**, paste `https://mcp.vibeseo.dev/mcp` as the server URL, then for authentication choose **OAuth**. ChatGPT sends you to VibeSEO to sign in.

4. Check **I understand and want to continue**, then select **Create as a plugin**.

Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=vibeseo&config=eyJ1cmwiOiJodHRwczovL21jcC52aWJlc2VvLmRldi9tY3AifQ%3D%3D>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

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

Cursor shows **Needs authentication** next to the server. Click the button beside it to sign in.

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=vibeseo&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fmcp.vibeseo.dev%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"vibeseo","type":"http","url":"https://mcp.vibeseo.dev/mcp"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "vibeseo": {
      "type": "http",
      "url": "https://mcp.vibeseo.dev/mcp"
    }
  }
}
```

VS Code asks you to sign in the first time the server starts.

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "vibeseo": {
      "serverUrl": "https://mcp.vibeseo.dev/mcp"
    }
  }
}
```

2. Refresh the MCP server list in Cascade and sign in when asked.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add vibeseo --url https://mcp.vibeseo.dev/mcp
codex mcp login vibeseo
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.vibeseo]
url = "https://mcp.vibeseo.dev/mcp"
```

### Gemini CLI

```bash
gemini mcp add --transport http vibeseo https://mcp.vibeseo.dev/mcp
```

Then, inside Gemini CLI, run `/mcp auth vibeseo` to sign in.

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "vibeseo": {
      "type": "http",
      "url": "https://mcp.vibeseo.dev/mcp"
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://mcp.vibeseo.dev/mcp`.

## Details

- Server version: 0.1.4
- Last checked: 2026-11-17 (reachable, asks for credentials)
- Listed: 2026-10-05
- Updated: 2026-10-05

---
Source: https://mcp.tc/i/vibeseo (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report
