Setup

Connect your MCP client to AIclicks with an API key.

Pick your client below. Every flow needs an AIclicks API key — grab one from Settings → Developers in your dashboard.

The server is hosted at https://mcp.aiclicks.io/mcp and speaks streamable HTTP. Auth is a bearer token on every request — the same ak_live_* key as the REST API.

Two ways to authenticate. Sign in (OAuth) — recommended for Claude: add the URL, click Connect, log in, and pick a team; OR API key — send Authorization: Bearer ak_live_*, best for Cursor, scripts, and mcp-remote.

Open Connectors

Go to Customize → Connectors in Claude.

Add custom connector

Click + → Add custom connector:

Name: AIclicks
URL: https://mcp.aiclicks.io/mcp

Leave the Authorization header blank — that's what triggers sign-in.

Connect & authorize

Click Connect. A window opens to AIclicks — sign in if needed, pick the team (or all teams) to grant access to, and click Allow.

Verify

New conversation → "List my AIclicks domains."

Prefer an API key? Add the connector the same way but set the Authorization header to Bearer YOUR_API_KEY.

Once you've set it up on claude web, it works on claude desktop automatically but you can confirm on the connectors page.

Get your API key

In your AIclicks dashboard, go to Settings → Developers, click Create API Key, and copy it.

Add the server

claude mcp add --transport http aiclicks https://mcp.aiclicks.io/mcp \
  --header "Authorization: Bearer YOUR_API_KEY"

Replace YOUR_API_KEY with the key from step 1.

Verify

claude mcp list

The aiclicks server should show as Connected.

Get your API key

In your AIclicks dashboard, go to Settings → Developers, click Create API Key, and copy it.

Add the config

Add to .cursor/mcp.json (per-project) or ~/.cursor/mcp.json (global):

{
  "mcpServers": {
    "aiclicks": {
      "url": "https://mcp.aiclicks.io/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Replace YOUR_API_KEY with the key from step 1.

Verify

Open Cursor's MCP settings panel. The aiclicks server should show as Connected with its tool list visible.

Any MCP-compatible client can connect using:

URL:           https://mcp.aiclicks.io/mcp
Transport:     Streamable HTTP
Authorization: Bearer YOUR_API_KEY

If your client doesn't support remote HTTP servers, use the mcp-remote proxy:

{
  "mcpServers": {
    "aiclicks": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.aiclicks.io/mcp",
        "--header",
        "Authorization: Bearer YOUR_API_KEY"
      ]
    }
  }
}

Connecting without a key runs OAuth: the client opens the AIclicks authorize page, you sign in and pick a team, and AIclicks issues a read-only connection scoped to that team. Revoke any time from Settings → Developers (shown as a Claude (MCP) key).

Start using it

Once connected, ask your AI assistant questions like:

"How visible is my brand in AI search results?"
"Which sources are LLMs citing when they mention us?"
"Compare our AI visibility against competitors."
"Which prompts are winning or losing visibility?"
"Which model surfaces my brand the most — ChatGPT or Claude?"

See Tools for the full tool reference, or Troubleshooting if a connection or call isn't working.

Was this page helpful?