LLMClicks MCP Server

Connect your LLMClicks AI visibility data directly to Claude Desktop, Cursor, Windsurf, and any MCP-compatible AI tool.

Ask Claude: "What's my AI visibility for my project?" — and get live data, without opening a browser.

Prerequisites

• Node.js 18+ installed on your machine
• An active LLMClicks.ai account
• A LLMClicks API Key (starts with rr-) — get it from LLMClicks.ai → Settings → API Keys

Quick Setup

Step 1 — Install Dependencies

cd llmclicks-mcp
npm install

Step 2 — Test Your API Key (Optional but Recommended)

LLMCLICKS_API_KEY=rr-yourkey node test.js

You should see something like:

✅ API Key Format: OK
✅ PASS — Found 3 project(s).
✅ PASS — Found 52 citation(s).

Step 3 — Connect to Claude Desktop

Open your Claude Desktop configuration file:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json

Add this block (replace rr-yourkey with your real API key and update the path):

{
  "mcpServers": {
    "llmclicks": {
      "command": "node",
      "args": ["C:\\Users\\dell\\Desktop\\rreso_2805\\llmclicks-mcp\\index.js"],
      "env": {
        "LLMCLICKS_API_KEY": "rr-yourkey"
      }
    }
  }
}

Step 4 — Restart Claude Desktop

Fully quit and reopen Claude Desktop. You should see the LLMClicks integration appear as a tool (🔌 icon).

Available MCP Tools

| Tool | Description | |------|-------------| | list_projects | List all your LLMClicks projects | | get_visibility | Get the latest AI visibility data for a project | | get_citations | Get citations (domains cited by AI engines) for a project | | run_scan | Trigger a new AI visibility scan for a specific query |

Example Prompts to Try in Claude

"List my LLMClicks projects."

"What is my current AI visibility for my main project?"

"Show me the top citations for project [ID]."

"Run a scan for 'best project management software' on my project."

"Give me a full AI visibility report for my Acme Corp project."

Connect to Cursor or Windsurf

Add to your Cursor MCP settings (~/.cursor/mcp.json):

{
  "mcpServers": {
    "llmclicks": {
      "command": "node",
      "args": ["C:\\Users\\dell\\Desktop\\rreso_2805\\llmclicks-mcp\\index.js"],
      "env": {
        "LLMCLICKS_API_KEY": "rr-yourkey"
      }
    }
  }
}

Environment Variables

| Variable | Required | Description | |----------|----------|-------------| | LLMCLICKS_API_KEY | ✅ Yes | Your LLMClicks API key (starts with rr-) | | LLMCLICKS_API_BASE | ❌ No | Override the API base URL (for self-hosted instances) |

Troubleshooting

"Missing LLMCLICKS_API_KEY" error: → Make sure the env block in your MCP config has your API key set correctly.

"Invalid or inactive API key" from API: → Go to LLMClicks.ai → Settings → API Keys and verify your key is active.

No tools appearing in Claude: → Make sure you fully quit and restarted Claude Desktop after editing the config.

Network error reaching API: → Run node test.js manually to confirm the API is reachable from your machine.

How It Works

Claude Desktop / Cursor
      │ (MCP stdio protocol)
      ▼
llmclicks-mcp/index.js      ← this package (runs locally)
      │ (HTTPS REST)
      ▼
LLMClicks API (api-v1)      ← your live Supabase edge function
      │
      ▼
Your project data (Supabase DB)

The MCP server runs as a background process on your local machine. It never stores your data — it simply relays requests from Claude to the LLMClicks API in real time.