MCP Server

AI Rank Lab tools, inside your AI agent

The AI Rank Lab MCP server exposes the same tools as the developer API — URL audits, Core Web Vitals, keyword research, AI brand-visibility checks, FAQ and llms.txt generation, bot-visit and citation data — over the Model Context Protocol. Add it to Claude Code, Claude Desktop, or Cursor and your agent can run them directly.

Get your API key REST API reference

Introduction

The Model Context Protocol (MCP) is an open standard that lets AI assistants call external tools. Our MCP server is a thin layer over the /api/v1 REST API: same tools, same credit billing, same account — but callable by Claude, Cursor, or any other MCP-compatible client as part of a conversation.

The server uses the Streamable HTTP transport in stateless mode, so there is nothing to install or host — you point your client at the endpoint with your API credentials.

Endpoint & authentication

The server lives at a single endpoint:

POST https://www.airanklab.com/api/v1/mcp

Every request must carry the same two headers as the REST API: x-api-key and x-api-secret. Generate both from Dashboard → API & Integrations.

Your MCP client config stores the secret in plain text on your machine. Keep the config file out of version control, and rotate the key pair from the dashboard if it ever leaks.

Claude Code

One command adds the server to Claude Code (CLI v1.x or later):

Terminal

claude mcp add --transport http airanklab https://www.airanklab.com/api/v1/mcp \
  --header "x-api-key: YOUR_API_KEY" \
  --header "x-api-secret: YOUR_API_SECRET"

Then ask Claude Code things like “run an audit of example.com and summarize the critical issues” — it will call the audit_url tool for you.

Claude Desktop

Add this to your Claude Desktop configuration (Settings → Developer → Edit Config, file claude_desktop_config.json), then restart the app:

claude_desktop_config.json

{
  "mcpServers": {
    "airanklab": {
      "url": "https://www.airanklab.com/api/v1/mcp",
      "headers": {
        "x-api-key": "YOUR_API_KEY",
        "x-api-secret": "YOUR_API_SECRET"
      }
    }
  }
}

Cursor

Add the same block to ~/.cursor/mcp.json (global) or .cursor/mcp.json in your project:

mcp.json

{
  "mcpServers": {
    "airanklab": {
      "url": "https://www.airanklab.com/api/v1/mcp",
      "headers": {
        "x-api-key": "YOUR_API_KEY",
        "x-api-secret": "YOUR_API_SECRET"
      }
    }
  }
}

Available tools & pricing

MCP tools mirror the REST tool endpoints one-to-one and spend the same credit balance — a tool costs the same whether you call it from the dashboard, the REST API, or MCP. Data reads are free; failed tool calls are refunded automatically.

Tool	Description	Credits per call
`audit_url`	Run a full AEO/SEO audit of a URL	50
`keyword_research`	Keyword volume, difficulty and ideas	50
`core_web_vitals`	Core Web Vitals / PageSpeed scan	25
`brand_visibility`	Ask a live AI engine about a brand	100 per engine
`generate_faq`	Generate an FAQ for a page	20
`generate_llms_txt`	Generate an llms.txt manifest	20
`tracking_stats`	AI bot visit stats for your domain	Free
`citations`	Where AI engines cite your site	Free
`credits`	Current credit balance	Free

Long-running tools

Heavier tools (audits, brand visibility) normally finish within the request. Each call has a 120-second budget: if the work isn't done in time, the tool returns a jobId with polling instructions instead of the result.

Poll GET /api/v1/jobs/{jobId} (REST, same headers) until the status is completed — see Async jobs in the API reference.

Rate limits

MCP requests count against the same per-key limit as the REST API: 60 requests per minute by default. A 429 response includes Retry-After. Need a higher limit? Contact us.

Connect your agent

Generate your API key and secret, paste one config block, and your AI agent can run real marketing tools.

Get your API key