MCP Server Documentation

The Better Search Console MCP server exposes 27 tools that give AI assistants full access to your SEO data and operations:

• List and manage your websites
• Browse, filter, and delete URLs
• Add, process, and delete sitemaps
• Queue URLs for Google/Bing indexation
• Check indexation status
• Create AI prompt analyses
• Configure website settings
• Manage custom dashboards
• Generate sitemaps and robots.txt files

MCP Endpoint

https://www.better-search-console.com/_mcp

Connect Better Search Console to Claude.ai in 4 steps:

1Generate an API token

Go to Settings in Better Search Console and click Generate API Token. Copy the 64-character token.

2Add the connector

On Claude.ai, go to Settings > Connectors > Add custom connector

• Name: Better Search Console
• URL: https://www.better-search-console.com/_mcp
• Leave OAuth fields empty

3Connect

Click Connect. You'll see an authorization page — paste your API token and click Authorize.

4Start using

In any Claude conversation, the BSC tools are now available. Just ask Claude to manage your SEO:

"List all my websites and show me which URLs are not indexed"
"Submit my 5 newest blog posts to Google for indexation"
"Check the indexation status of all pages on example.com"

If you have the project running locally, you can use the STDIO transport for Claude Desktop.

Edit your Claude Desktop config

Open ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows) and add:

{
  "mcpServers": {
    "better-search-console": {
      "command": "php",
      "args": ["/path/to/BetterSearchConsole/bin/console", "app:mcp:serve"],
      "env": {
        "BSC_API_TOKEN": "YOUR_API_TOKEN_HERE"
      }
    }
  }
}

Replace /path/to/BetterSearchConsole with the actual path and YOUR_API_TOKEN_HERE with your token.

Alternative: pass token as option

php bin/console app:mcp:serve --token=YOUR_API_TOKEN_HERE

Any MCP-compatible client can connect. Use the HTTP transport:

The server accepts authentication via:

• Authorization: Bearer YOUR_TOKEN header
• X-API-TOKEN: YOUR_TOKEN header
• ?token=YOUR_TOKEN query parameter

The MCP server uses the same API token as the REST API. Generate it from Settings.

OAuth Flow (Claude.ai)

When connecting from Claude.ai, you'll be redirected to an authorization page where you paste your API token. This only happens once — Claude stores the token for future sessions.

Direct Token (Desktop/Cursor)

For desktop clients, pass the token via environment variable or header. The server validates it against your account on every request.

Here are example prompts you can use with Claude once connected:

Check SEO status

"Show me all my websites and their indexation stats for today"

Find non-indexed pages

"List all URLs on my website that are not indexed by Google"

Submit new content

"Submit these URLs to Google for indexation: https://example.com/blog/post-1, https://example.com/blog/post-2"

Bulk indexation

"Queue all pages containing '/blog/' for Google and Bing indexation"

Sitemap management

"Add the sitemap https://example.com/sitemap-news.xml to my website and process it"

Status check

"Check the indexation status of my 10 most recently added URLs"

Clean up

"Find all URLs returning 404 and remove them from indexation"

Generate SEO files

"Generate a robots.txt that blocks /admin and /private, allows everything else, and includes my sitemap"

Prompt analysis

"Create a prompt analysis for 'best project management tools' targeting keywords 'project management' and 'productivity' using GPT-4 and Claude"

Indexation and verification tools share the same daily limits as the web interface and REST API:

When a limit is reached, the tool returns an error with "limit_reached": true. Limits reset daily at midnight UTC.

You can check current usage via the list-websites tool (see indexationRequestToday and checkStatusRequestToday fields).

"This connector has no tools available"

This usually means the authentication failed or the server couldn't load tools. Try:

• Disconnect and reconnect the connector
• Re-enter your API token when prompted
• Verify your token is valid by testing the REST API: curl -H "X-API-TOKEN: YOUR_TOKEN" https://www.better-search-console.com/api/websites

"Connection to server failed"

• Check that https://www.better-search-console.com/_mcp is accessible
• Ensure you're not behind a firewall blocking the connection

"Daily limit reached"

You've used all your daily indexation or verification requests. Upgrade your plan or wait until midnight UTC for the reset.

"URL not found or access denied"

The URL you're trying to operate on either doesn't exist in your database or belongs to a website you don't own. Make sure the URL has been imported via a sitemap first.

Token issues

• Tokens are 64 characters long (hexadecimal)
• You can regenerate your token at any time from Settings
• After regenerating, you'll need to reconnect any MCP clients