Gen Ready AI
    HomeDeveloper DocsMCP Server

    GenReady MCP Server

    Model Context Protocol

    Connect AI agents directly to GenReady. Analyze websites from Claude Desktop, Cursor, Windsurf, and any MCP-compatible tool.

    What is MCP?

    The Model Context Protocol (MCP) is an open standard that lets AI assistants connect to external tools and data sources. Think of it as a USB port for AI - plug in GenReady, and your AI agent can analyze websites directly.

    Instead of copying URLs and pasting results, just ask your AI assistant to analyze a website. GenReady handles the rest.

    Learn more about MCP

    Installation

    1

    Get your API key

    Create an API key at genready.ai/api-keys. Copy it - you'll need it in step 3.

    2

    Open Claude Desktop settings

    Go to Settings → Developer → Edit Config to open your claude_desktop_config.json file.

    3

    Add the GenReady MCP server

    Add the following to your config file (replace the API key with your own):

    json{
  "mcpServers": {
    "genready": {
      "command": "npx",
      "args": ["@genready/mcp-server"],
      "env": {
        "GENREADY_API_KEY": "gr_live_your_key_here"
      }
    }
  }
}
    4

    Restart Claude Desktop

    Close and reopen Claude Desktop. The GenReady tools will appear in the tools menu (hammer icon).

    5

    Start analyzing!

    Try asking: "Analyze https://example.com for AI readiness"

    Available Tools

    Tip: Use the scope parameter to run faster, cheaper checks. A crawlability scan (technical checks only) completes in ~10 seconds. A content scan analyzes writing quality. A full scan does both. Each scope counts as one analysis credit.

    analyze_website

    Analyze a website's readiness for AI search engines. Returns an AI readiness score with detailed breakdown and actionable recommendations.

    Parameters:

    NameTypeRequiredDescription
    urlstringYesThe full URL to analyze (e.g., https://example.com/page)
    scopestringNo"full" (default), "content" (quality only), or "crawlability" (technical only)
    waitbooleanNoWait for analysis to complete (default: true)

    Example prompt:

    "Analyze https://example.com for AI readiness"

    get_report

    Retrieve a previously generated AI readiness report by its ID.

    Parameters:

    NameTypeRequiredDescription
    report_idstringYesThe report ID returned from analyze_website

    Example prompt:

    "Get the report for ID acae9782-f6aa-46d0-ae79-8aca8eb5a3bf"

    check_status

    Check the progress of a running analysis. Returns completion percentage and step-by-step status.

    Parameters:

    NameTypeRequiredDescription
    report_idstringYesThe report ID to check

    Example prompt:

    "Check the status of analysis acae9782-f6aa-46d0-ae79-8aca8eb5a3bf"

    What You'll See

    This is a real report from the MCP server - what your AI assistant receives:

    ## AI Readiness Report: example.com

**Overall Score: 72/100**

### Content: 65/100
- Facts & Details: 342 words (6.2/10) ⚠️
- Filler Words: (8/10) ✅
- Links to Sources: 1 external link (4/10) ⚠️
- Topic Focus: (7.8/10) ✅
- Heading Structure: H1×1, H2×4 (9/10) ✅
- Tables and Lists: (3/10) ❌
- Schema Markup: (1/10) ❌
- Freshness: published 2025-11-03 (6/10) ⚠️
- Originality: TTR 0.41 (7/10) ⚠️
- AI Text: human-written (9/10) ✅
- Writing Style Match: informational (5/10) ⚠️

### Crawlability: 88/100
- HTTPS Security: (18) ✅
- AI Access Rules: AI crawlers allowed (18) ✅
- Firewall: No blocking (15) ✅
- Loading Speed: 245ms (10) ✅
- Site Map: Found & valid (10) ✅
- Meta Tags: (8) ✅
- Page Size: 42KB (7) ✅
- Paywall Block: None (5) ✅
- LLM File: Not found (0) ❌
- Image Descriptions: (2) ⚠️
- Internal Links: (2) ✅

### Top Recommendations:
1. Add outbound links to authoritative sources
2. Add JSON-LD schema markup (Article, WebPage)
3. Include structured data like tables or bullet lists
4. Create an llms.txt file for AI crawlers

    Example Conversations

    You: Is my website ready for AI search engines? Check https://mysite.com

    Claude: I'll run a full AI readiness analysis on your site. The analysis checks both content quality and technical crawlability... **Overall Score: 72/100** - Your site has good technical foundations but could improve content structure for better AI citation.

    You: Just run a crawlability check on https://mysite.com - I only need the technical stuff

    Claude: Running a crawlability-only check (faster than a full scan)... **Crawlability Score: 88/100** ✅ HTTPS, robots.txt, and loading speed all look good. One issue: your XML sitemap lastmod dates are stale - AI crawlers use these to decide which pages to re-index.

    You: Check the status of my analysis and then get the full report

    Claude: Let me check... The analysis is complete (100%). Retrieving the full report now. **AI Readiness Report - mysite.com** Overall: 72 | Content: 65 | Crawlability: 88 Top recommendations: 1. Add outbound links to authoritative sources - 0 external citations found 2. Add JSON-LD schema markup (Article, WebPage) for structured data 3. Clean up heading hierarchy - multiple H1 tags detected on /blog posts

    Troubleshooting

    "GENREADY_API_KEY not set"

    Make sure the GENREADY_API_KEY environment variable is set in your MCP config. The key must start with gr_live_ or gr_test_. Double-check there are no extra spaces or quotes around the key value.

    "Connection refused" or server won't start

    Ensure npx is available in your system PATH and can download npm packages. Try running npx @genready/mcp-server --version in your terminal to verify the package installs correctly.

    "Invalid API key" or "Unauthorized"

    Verify your API key is active at genready.ai/api-keys. Keys may have been revoked or expired. Generate a new key if needed - remember, keys are only shown once at creation.

    Tools not showing in Claude Desktop

    Make sure you've restarted Claude Desktop after editing the config. Check that the JSON is valid (no trailing commas, correct brackets). The tools menu (hammer icon) should show GenReady's three tools.

    Remote SSE connection times out or hangs

    Verify your MCP client supports remote SSE connections - Claude Desktop and Cursor currently require the local npx setup instead. If your client does support SSE, try the ?apiKey= query parameter format instead of the Authorization header. Maximum 5 concurrent SSE connections per API key.

    Analysis takes too long

    A full analysis typically completes in 15–30 seconds. Use scope: "crawlability" for faster technical-only checks (~10 seconds). If the analysis is still running, use the check_status tool to monitor progress.

    Still stuck? Contact support and include your meta.requestId from any error responses.