Knowledge base

Connect Findrix to your AI assistant

Once connected, you can ask your AI assistant how your brand shows up in AI answers, what to fix next, or for a PDF report, and it gets the answer from your Findrix account. With Claude it takes about two minutes and you don't need a key or any settings file.

Before you start

  • A Findrix account with at least one site on a paid plan (Presence or higher). Without one, your assistant can only tell you who you are in Findrix.
  • The assistant app you want to use, signed in. If your Claude account belongs to a company (Claude Team or Enterprise), an owner may need to add Findrix for the whole organization first.
  • A few minutes: about two for Claude, about five for Cursor or Codex.

Claude: claude.ai and the desktop appRecommended

The easiest way. You sign in with your Findrix account, so there is no key to copy and nothing to install. It works the same on Mac and Windows, in the browser and in the Claude desktop app.

Add Findrix to Claude

Opens claude.ai with the name and the server address filled in. Server address:

https://app.findrix.ai/api/mcp
  1. Click Add Findrix to Claude above. Claude opens the Add custom connector form with the name and the server address already filled in. To add it by hand instead, open Customize → Connectors → Add custom connector in Claude and paste the server address https://app.findrix.ai/api/mcp.

  2. Leave Request headers empty.

  3. Under Authentication, choose Sign in when needed.

  4. Under OAuth client, choose Use Claude's published identity. Don't pick Register automatically: Findrix doesn't support it, and the connection fails.

  5. Click Add.

    Claude’s Add custom connector form: Request headers left empty, Sign in when needed, Use Claude’s published identity, then Add. Illustration — your screen may look a little different.
  6. Open a new chat and ask: Who am I in Findrix, and which sites do I have? Claude asks you to connect Findrix. Click Connect, sign in to Findrix, and on the Authorize access screen click Allow.

    The Findrix screen that opens when Claude connects: keep Make changes for you ticked to let Claude make changes, then click Allow. Illustration — your screen may look a little different.

Leave Make changes for you ticked if Claude should approve fixes, add prompts or log work for you. Untick it, and Claude can only read.

Using the Claude desktop app? A connector you add on claude.ai appears there by itself, under the same Claude account. You can also add it from the desktop app's own settings, under Connectors, with the same choices.

Own a Claude Team or Enterprise organization? Add Findrix for everyone under Organization settings → Connectors instead.

Check that it works

Ask your assistant Who am I in Findrix, and which sites do I have? It should answer with your email, your plan and the list of your sites. If it does, Findrix is connected.

A first question in a new chat, and the kind of answer that shows Findrix is connected. Illustration — your screen may look a little different.

Then try one of these:

  • How is yourbrand.com doing in AI answers this month?
  • Which competitors do AI engines mention instead of us?
  • What should I fix on my homepage first?
  • What changed this week, and what is waiting for my decision?
  • Make a PDF report of our AI visibility.
  • Show me the fixes that are ready to approve, then approve them.

Name your site by its domain. If you have several sites, say which one in your first message: the assistant remembers it for the rest of the chat.

Cursor and Codex: get a key first

Cursor and Codex connect with a Findrix key, a long password made for one app. You create it in your Findrix account, and Findrix gives you the whole setup to paste, with the key already in it.

  1. Open MCP & connections in your Findrix account (Account → MCP & connections).

  2. Create a key and name it after the app, for example Cursor. An account can have up to five keys.

  3. Findrix shows the key only once, together with a ready-made setup. Under Set up a client, pick your app and your system (macOS / Linux or Windows) and click Copy. Keep the page open until you have pasted it.

    Right after you create a key, Findrix shows it once with a ready-made setup: under Set up a client, pick your app and your system, then click Copy. Illustration — your screen may look a little different.

Treat the key like a password: don't paste it into a chat with the assistant and don't send it by email. If it leaks, revoke it on the same page and create a new one.

Cursor

  1. Get a key with the ready-made setup for Cursor (above) and click Copy.

  2. In Cursor, open Cursor Settings → Tools & MCP and click New MCP server (Add new global MCP server in older versions). Cursor opens a file named mcp.json.

  3. If the file is empty or only has {}, select everything in it and paste. If it already lists other servers, paste only the "findrix": { … } part inside "mcpServers", with a comma between it and the server before it.

    Cursor’s mcp.json after pasting: a findrix entry with the server address and your key. Illustration — your screen may look a little different.
  4. Save the file.

    On a Mac

    Press Cmd+S.

    On Windows

    Press Ctrl+S.

  5. Back in Tools & MCP, Findrix appears with a green dot. If it doesn't, quit Cursor completely and open it again.

  6. Open a new chat and ask: Who am I in Findrix, and which sites do I have?

Codex

The Codex app, the Codex command line and the Codex extension for VS Code or Cursor share one settings file, so you set Findrix up once for all of them.

  1. Get a key with the ready-made setup for Codex (above) and click Copy.

  2. Open the Codex settings file.

    On a Mac

    Open Terminal (press Cmd+Space, type Terminal, press Return), paste this line and press Return. The file opens in TextEdit.

    mkdir -p ~/.codex && touch ~/.codex/config.toml && open -e ~/.codex/config.toml

    On Windows

    Press Win+R, paste this line and press Enter. If Notepad asks whether to create the file, click Yes. If it says the path can't be found, open Codex once, close it and try again.

    notepad %USERPROFILE%\.codex\config.toml
  3. Paste the setup at the end of the file and save it.

    Codex’s config.toml after pasting: the setup starts with [mcp_servers.findrix]. Illustration — your screen may look a little different.
  4. Quit Codex completely and start it again. Using Codex inside VS Code or Cursor? Restart that app.

    On a Mac

    Press Cmd+Q in Codex, then open it again.

    On Windows

    Close Codex, and close it in the system tray too if its icon is there. Then open it again.

  5. Ask: Who am I in Findrix, and which sites do I have?

The settings file now holds your key. Don't share it, and don't keep it in a synced or shared folder.

Connected Codex to Findrix before, with a FINDRIX_MCP_KEY variable? Replace the old [mcp_servers.findrix] part with the new setup instead of adding a second one.

ChatGPTComing soon

ChatGPT connects to other services only by signing in, and Findrix sign-in from ChatGPT is still being checked. Until it is ready, use Claude, or Codex if you work with OpenAI's tools. This page will say so as soon as ChatGPT works.

Reading and making changes

Your assistant can always read. Making changes (approving fixes, adding prompts or competitors, logging work) needs your permission:

  • Connected by signing in (Claude): it's the Make changes for you box on the Findrix screen you saw when connecting. To change it, disconnect and connect again.
  • Connected with a key (Cursor, Codex): it's the Allow writes switch next to the key on MCP & connections. Switched off, the assistant can still read, but every change is refused with writes_disabled. Switch it off for a key you hand to someone else.
  • Every change made this way appears in your Work Log marked via MCP.
  • To undo, ask Undo the last change within 24 hours. A removed competitor can't be brought back that way (add it again instead), and neither can a generated file (it expires on its own). If you changed the same thing in the dashboard afterwards, the undo is refused, so your own edit stays.
  • Before anything in bulk, like approving every fix, ask the assistant to show you the list first.
  • Your assistant can't start a new AI visibility measurement (Findrix runs those on schedule) and never pays for anything: for a plan change it gives you a checkout link to open yourself.

How to disconnect

  • Claude: remove Findrix under Customize → Connectors in Claude. Then, on MCP & connections in Findrix, click Disconnect next to it under Connected apps: access stops at once.
  • Cursor or Codex: delete the Findrix part from the settings file, then revoke the key on MCP & connections. A revoked key stops working at once.

If something doesn't work

The assistant doesn't see Findrix
Start a new chat. Cursor, Codex and the Claude desktop app pick up a new connection only after a full restart: quit the app, not just its window, and open it again. In Claude, also check that Findrix is switched on in the chat's tools menu.
Every request fails with 401 or "Unauthorized"
The key is missing, mistyped or revoked. Create a new key on MCP & connections and copy the ready-made setup again; don't retype the key by hand.
plan_required
The site, or your account, isn't on a paid plan. Subscribe the site in Findrix, or ask the assistant for a checkout link.
writes_disabled
Changes are switched off for this connection. Turn on Allow writes next to the key, or disconnect Claude and connect again with Make changes for you ticked.
rate_limited
Too many requests in a short time: wait as long as the message says. Each connection can make 120 reads a minute and 5,000 a day, and 60 changes a minute and 1,000 a day.
Claude doesn't connect after choosing Sign in now
That option is still being checked. Remove the connector and add it again with Sign in when needed.
There is no Add custom connector in Claude
Your Claude plan or your organization's settings may not allow custom connectors. In a company account, ask an owner to add Findrix for the organization.
In Codex, long answers are cut off in the middle
Copy the ready-made setup for Codex from Findrix again: it includes the line that prevents this.

For developers

Claude Code, VS Code, n8n, MCP Inspector and the Claude and OpenAI APIs connect too. The configs for each, every tool and its actions, the limits and the changelog are in the MCP server reference; the same configs are on MCP & connections in your account, under Connect a client. The server address is https://app.findrix.ai/api/mcp; it accepts sign-in (OAuth) and keys sent as Authorization: Bearer.