MCP DocumentationIntroduction

Introduction

Use AIclicks from any MCP-compatible AI assistant — Claude, Cursor, and more.

The AIclicks MCP server lets your AI assistant query your AIclicks data directly. No glue code, no custom integration — your assistant gets a typed tool surface over the same /api/v1/* endpoints that power the dashboard.

It speaks the Model Context Protocol, so any MCP-aware client (Claude Desktop, Claude Code, claude.ai web, Cursor, …) can connect to it the same way.

The MCP is available exclusively to teams on the Pro or Business plan. Upgrade your plan or contact support@aiclicks.io to enable API access.

What it gives you

Once connected, your assistant can answer questions like:

  • "How visible is my brand in AI search results this week?"

  • "Which sources are LLMs citing when they mention us?"

  • "Compare our share of voice against competitors over the last 30 days."

  • "Which prompts are losing visibility month over month?"

  • "Where are we underperforming on Claude vs. ChatGPT?"

…by routing the request through one of the tools described in Tools.

How it works?

  • Read-only. No write tools — you can't create domains, add prompts, or trigger analyses from the MCP surface.

  • No raw SQL. All queries go through the same /api/v1/* envelope as the public API. Results are cached server-side; you get the dashboard view, not raw rows.

  • No background work. Each tool call is a single synchronous request. There are no long-running jobs you need to poll.

How it's hosted

The server is a streamable-HTTP MCP endpoint at:

https://mcp.aiclicks.io/mcp

You authenticate one of two ways: sign in (OAuth) — click Connect, log in to AIclicks, and pick a team, or use an ak_live_* API key, the same key as the public REST API. Either way there's no separate signup. See Setup for client-specific install steps.

Team keys are scoped to one team. A master key spans every team you belong to (each still gated by that team's developer_access). Both inherit the allowed_domains allowlist of the user who created the key.

The MCP server is a thin auth-aware proxy over /api/v1/*. Every request inherits the same rate limit, the same domain scoping, and the same caching as the underlying REST endpoint.

Next steps

  • Setup — connect your client (Claude Desktop, Claude Code, claude.ai web, Cursor, others).

  • Tools — the full tool reference.

  • Recipes — prompts and tool-chain templates you can copy.

  • Troubleshooting — common errors and how to fix them.

Was this page helpful?