xseek Logo
Back to Documentation

xSeek AEO MCP

Integrate AI SEO tools directly into your development workflow with our Model Context Protocol (MCP) server

Get StartedView Tools

Contents

What is MCP?

The Model Context Protocol (MCP) is an open standard that allows AI assistants to securely connect to external data sources and tools. The xSeek AEO MCP server provides AI SEO tools that can be used directly within compatible applications.

Direct Integration

Access AI SEO tools directly from within your development environment without switching between applications or copying URLs.

Secure Authentication

Uses your existing XSeek API key for secure authentication, ensuring your data remains protected.

Setup Guide

1. Get Your API Key

First, you'll need an API key from xSeek and create an account.

Create an account here

2. Configure Your Application

Add the xSeek AEO MCP server to your application's MCP configuration. Create or edit the MCP configuration file:

~/.cursor/mcp.json

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

Important: Replace "YOUR_API_KEY_HERE" with your actual XSeek API key.

3. Restart Your Application

After configuring the MCP server, restart your application to load the new configuration. You should now have access to XSeek AI SEO tools directly in your development environment.

Available Tools

The xSeek AEO MCP server provides the following AI SEO tools that you can use directly in compatible applications:

robots_txt_scan

Scans and analyzes a website's robots.txt file to determine which AI bots and crawlers are allowed or disallowed from accessing the site.

Parameters:

  • url - The website URL to scan (string, required)

Returns:

  • • robots.txt content
  • • List of allowed AI bots and crawlers
  • • List of disallowed AI bots and crawlers
  • • Scan status and any error messages

generate_llms_txt

Generates an AI LLMs.txt file for a given URL, providing structured information about the website's content that AI language models can use for better understanding and indexing.

Parameters:

  • url - The website URL to generate LLMs.txt for (string, required)

Returns:

  • • Generated LLMs.txt content
  • • Structured website information
  • • AI-friendly content description

Website Management

get_websites

Retrieve all websites associated with your organization.

Returns:
  • • List of all websites with their details
  • • Website IDs, names, URLs, and configuration

create_website

Create a new website for AI SEO tracking.

Parameters:
  • name - Website name (string, required)
  • url - Website URL (string, required)
  • competitors - List of competitor URLs (array, optional)
  • robotsUrl - Robots.txt URL (string, optional)
  • sitemapUrl - Sitemap URL (string, optional)

update_website

Update an existing website's configuration.

Parameters:
  • websiteId - Website ID to update (string, required)
  • name - New website name (string, optional)
  • url - New website URL (string, optional)
  • competitors - Updated competitor list (array, optional)
  • robotsUrl - Updated robots.txt URL (string, optional)
  • sitemapUrl - Updated sitemap URL (string, optional)

Prompt Management

get_prompts

Retrieve all prompts for a specific website.

Parameters:
  • websiteId - Website ID (string, required)
Returns:
  • • List of all prompts for the website
  • • Prompt details, status, and configuration

create_prompt

Create a new prompt for AI SEO tracking.

Parameters:
  • websiteId - Website ID (string, required)
  • prompt - Prompt text (string, required)
  • competitors - Competitor list (array, optional)
  • mainCompany - Main company name (string, optional)
  • isActive - Whether prompt is active (boolean, optional)
  • frequency - Run frequency: daily/weekly/monthly (string, optional)

update_prompt

Update an existing prompt's configuration.

Parameters:
  • websiteId - Website ID (string, required)
  • promptId - Prompt ID to update (string, required)
  • name - Prompt name (string, optional)
  • prompt - Updated prompt text (string, optional)
  • mainCompany - Updated company name (string, optional)
  • competitors - Updated competitor list (array, optional)
  • isActive - Updated active status (boolean, optional)
  • frequency - Updated frequency (string, optional)

get_latest_prompt_runs

Get the latest execution results for a specific prompt.

Parameters:
  • websiteId - Website ID (string, required)
  • promptId - Prompt ID (string, required)
  • page - Page number for pagination (number, optional)
  • pageSize - Results per page (number, optional)
Returns:
  • • Latest prompt execution results
  • • AI model responses and mentions
  • • Execution timestamps and status

get_leaderboard

Get the competitive leaderboard showing company mentions and rankings.

Parameters:
  • websiteId - Website ID (string, required)
  • lastDays - Number of days to include (number, optional)
Returns:
  • • Company ranking by mentions
  • • Mention counts and competitive positioning
  • • Competitor identification

Usage Examples

Scan a Website's robots.txt

Use the robots.txt scanner to check if AI bots can access a website:

// In your application, you can now use:
"Scan the robots.txt file for https://example.com to see which AI bots are allowed"

// The MCP tool will return:
{
  "success": true,
  "data": {
    "url": "https://example.com",
    "robotsTxtContent": "User-agent: *\nDisallow: /admin\n...",
    "allowedBots": ["gptbot", "claude-web", "perplexitybot"],
    "disallowedBots": ["chatgpt-user"],
    "status": "success"
  }
}

Generate LLMs.txt File

Generate an AI-friendly LLMs.txt file for better AI search engine optimization:

// In your application, you can now use:
"Generate an LLMs.txt file for https://example.com to help AI understand the site"

// The MCP tool will return:
{
  "success": true,
  "data": "# LLMs.txt for example.com\n\n## Overview\nThis website provides...\n\n## Key Content Areas\n- Blog posts about...\n- Product information...\n\n## Contact Information\n..."
}

Troubleshooting

Authentication Issues

If you're getting authentication errors, check the following:

  • Ensure your API key is correct and active
  • Verify you have an Enterprise plan subscription
  • Check that the API key is properly formatted in the mcp.json file
  • Make sure there are no extra spaces or characters in the Bearer token

Tool Not Available

If the xSeek tools don't appear in your application:

  • Check your application's console for any error messages
  • Verify the MCP configuration is properly formatted JSON
  • Try restarting your application completely

Need More Help?

Having trouble setting up the xSeek AEO MCP? Our support team is here to help.

Contact Support