xSeek AEO MCP

The xSeek MCP server lets MCP-compatible clients (like Cursor) call xSeek tools using your API key.

What is MCP?

MCP (Model Context Protocol) is a standard that lets AI assistants securely connect to external tools. xSeek exposes a set of tools (robots checks, LLMs.txt generation, website/prompt management, reporting) through its MCP server so you can run them from your AI client.

Endpoint
https://www.xseek.io/api/mcp
Authentication
Uses your xSeek API key as a Bearer token. Treat it like a password.

Setup

1) Get your API key
Log in to xSeek and generate an API key from your dashboard settings.
2) Configure Cursor

~/.cursor/mcp.json

{
  "mcpServers": {
    "xSeek": {
      "url": "https://www.xseek.io/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY_HERE"
      }
    }
  }
}

Important: Replace YOUR_API_KEY_HERE with your real API key.

3) Restart Cursor
Restart your MCP client so it loads the configuration and discovers the xSeek tools.
Video walkthrough

Available tools

Tool names appear in your MCP client. Here are the most common ones and what they do.

robots_txt_scan

Scan and analyze a website's robots.txt.

Parameters: url (string, required)
generate_llms_txt

Generate an LLMs.txt for a URL.

Parameters: url (string, required)
Website management

get_websites, create_website, update_website

Manage your websites, competitors, robots/sitemap URLs, and metadata.

Prompt management

get_prompts, create_prompt, update_prompt

Create and manage the prompts that power your AI visibility tracking.

Reporting

get_latest_prompt_runs, get_leaderboard, get_sources, get_latest_ai_visits

Pull results, leaderboards, cited sources, and AI bot visit data.

analyse_api

Analyze a page on your site for AEO improvements (AEO Copilot).

Parameters: websiteId (string, required), url (string, required)

Examples

Robots.txt scan

Ask your assistant:

Scan the robots.txt file for https://example.com
Generate LLMs.txt

Ask your assistant:

Generate an LLMs.txt for https://example.com

Troubleshooting

Vercel password protection / “Vercel authentication”

If your MCP client hits a password-protected page instead of the API route, MCP won't work. Disable Vercel password protection (or exclude /api/mcp from protection if your plan supports it).

Correct endpoint format: https://<your-app-domain>/api/mcp

Authentication errors
  • Confirm your header is exactly Authorization: Bearer ...
  • No quotes around the token, no extra whitespace
  • Restart your MCP client after changing config