Developers

How do I connect ChatSEO to Claude Code via MCP?

Set up the ChatSEO MCP server in Claude Code, Cursor, Windsurf, VS Code or Claude Desktop, and fix the common errors.

The ChatSEO MCP server lets you drive your sites, todos and SEO projects from your editor.

Who has access?

MCP and API access is included in the Pro and Ranker plans, as well as custom plans.

If you have no subscription at all, you can try it while you still have credits. The Starter plan is the only tier without access: you need Pro.

Supported clients: Claude Code, Cursor, Windsurf, VS Code and Claude Desktop.

Where to find your MCP settings

  1. Click your profile in the bottom left corner, then Settings.
  2. Under Workspace, open Developer.

You will find your server URL, per-client instructions, the tool list and the documentation. A separate tab covers the REST API.

Connecting Claude Code

The server URL is https://api.chatseo.app/mcp. In your terminal:

claude mcp add --transport http chatseo https://api.chatseo.app/mcp

On first connection you authenticate with your ChatSEO account. There is no API key to copy and paste.

For other clients, use the matching option in the Developer section, or the manual configuration.

What you can do

The server exposes around thirty tools covering sites, projects, todos, artifacts, integrations and conversations, plus WordPress publishing. The up-to-date list lives in the Developer settings.

The "No active organization" error

It usually shows on your first request: your call is not attached to an organization yet.

  1. List your organizations through MCP to get your organizationId.
  2. Select the organization you want to work with.

Later requests then work normally. That ID is not visible in the interface, only through MCP or the API.

Transport drops and timeouts

The MCP protocol does not stream responses. On a long job (keyword analysis, full audit), the client may give up before the end.

  • Tell your assistant: "MCP has no streaming, the timeout is on my side, wait and then fetch the conversation once it is done";
  • narrow the request (shorter period, fewer keywords);
  • the answer is still available in your conversation history on the dashboard.

A client that keeps returning 401

Some MCP clients do not implement the OAuth resource parameter (RFC 8707) that tells the server which resource the token is for. The connection completes, then every call comes back as 401 invalid_token.

ChatSEO now applies https://api.chatseo.app/mcp as the default resource, so these clients work over the direct HTTP URL. If your client still fails, route it through mcp-remote, which handles the full OAuth flow:

npx -y mcp-remote https://api.chatseo.app/mcp

This is the configuration already used for Claude Desktop, and the fallback shown in the Developer settings for Claude Code.

Unsupported clients and tools

Automation tools such as N8N are not officially supported. ChatSEO also has no direct integration with Ahrefs, SEMrush or Screaming Frog.

If you have a specific use case, message us in the chat.