VibeSEO MCP Server

SEO research, audits, backlinks, GSC, and content workflow tools for AI agents. The vibeseo mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 8 defined tools rather than through you.

What it actually does

VibeSEO MCP brings live SEO work into your AI assistant. Connect Claude, ChatGPT, Cursor, VS Code, or a CLI client to VibeSEO. Then ask for keyword research, audits, backlinks, Search Console trends, and content workflow actions in natural language.

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Its toolset

Everything the assistant can do here goes through one of these:

• Transport — ** Streamable HTTP
• Auth — ** OAuth 2.1 with PKCE, scope mcp:tools
• ChatGPT — custom MCP connector with OAuth
• Cursor — one-click install via deeplink, or ~/.cursor/mcp.json
• Product — vibeseo.dev
• Issues — github.com/sultanlive/vibeseo-mcp/issues
• Category — What it covers
• Price — $0 today, card required

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the vibeseo mcp server does with a few real requests.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. VibeSEO's toolset — Transport, Auth, ChatGPT and 5 more — is a fair guide to whether it matches your workflow. It is maintained by dev.vibeseo; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against VibeSEO's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.