Connect SEOAI to your AI assistant (MCP)

SEOAI has a remote MCP server. MCP (Model Context Protocol) is the standard that lets an AI assistant such as Claude or ChatGPT use outside tools. Once you connect SEOAI, your assistant can read the Gaps side of your workspace: the prompts where AI answers do not cite you, which competitor pages they cite instead, the citability audit for a prompt, the AI answers themselves, off-site gaps, fan-out gaps and Search Console or Bing queries next to your AI visibility.

The point is to close the loop from gap to fix. You ask the assistant to take your biggest gaps, and it comes back with a change list per page: what to add, where, why, and which competitor page to use as a reference. Nothing is copied out of the SEOAI app by hand.

The connection is read-only. The assistant cannot change anything in SEOAI: it cannot start audits, re-run prompts, edit brands or touch billing.

Who can use it

MCP access is included in the Pro and Agency plans, for every workspace on one of them. Free and Starter workspaces have no MCP access. Without access, the Connected apps page under Settings tells you what is missing.

You also need an AI assistant that can connect to a remote MCP server and sign in with OAuth. The server address is:

https://seoai.de/api/mcp

Connect your assistant

The sign-in works the same in every assistant: you add the address, the assistant opens a SEOAI sign-in page in your browser, and you allow the connection for one workspace. The Connected apps page under Settings shows the address and these steps with a copy button.

Claude.ai and Claude Desktop

1. Open Settings, then Connectors.
2. Choose Add custom connector.
3. Paste the server address and confirm.
4. Sign in to SEOAI when asked, pick your workspace and press Allow.

A connector you add on claude.ai also appears in Claude Desktop and in Claude Code sessions of the same Claude account, so you only connect once.

Claude Code

Run this command in your terminal:

claude mcp add --transport http seoai https://seoai.de/api/mcp

Start Claude Code, type /mcp, select seoai and choose Authenticate. Your browser opens the SEOAI sign-in. Allow the connection for your workspace and return to the terminal.

ChatGPT

ChatGPT lets only some plans add a custom MCP server. On Business and Enterprise or Edu plans, a workspace admin or owner adds it: open Plugins, choose the plus button, then Add custom MCP server, paste the server address, choose OAuth and confirm the risk warning. Pro users can add custom MCP servers with read and fetch permissions, which is all SEOAI needs. Free and Plus can't add custom MCP servers. OpenAI changes these menus and plans often, so check OpenAI's help article on connecting custom MCP servers (https://help.openai.com/en/articles/12584461) if your screen looks different. SEOAI supports what ChatGPT needs, including refresh tokens, but we have not verified ChatGPT ourselves yet.

Cursor and Codex

Both can connect to remote MCP servers with OAuth, so SEOAI should work in them. We have not tested either. In Cursor, add the server to your MCP configuration:

{
  "mcpServers": {
    "seoai": {
      "url": "https://seoai.de/api/mcp"
    }
  }
}

In Codex, add SEOAI as a remote MCP server with the same address in its MCP settings and sign in when asked. If one of these does not connect, write to hello@seoai.de with the name of the app, and we will look at it.

What happens when you connect

1. The assistant sends you to seoai.de. Sign in with your usual account.
2. The consent page names the app, shows its web address and says in plain words what it may do: read your Gaps data, change nothing.
3. Pick the workspace for this connection. Workspaces without MCP access are listed but cannot be picked, with the reason next to them. The demo workspace is never offered.
4. Press Allow. The assistant now lists SEOAI's tools.

One connection covers one workspace. To read another workspace, connect again and pick that one. On the Agency plan the sites of your clients are brands inside your workspace, so one connection covers all of them.

Send this page to your AI

The quickest way to get going is to let the assistant read the docs. Paste the addresses of this page and the technical reference into your chat and ask it to set up and use SEOAI:

Read https://support.seoai.de/docs/mcp/ and https://support.seoai.de/docs/mcp-reference/.
Then list my SEOAI brands and show me the three biggest gaps for the first one.

What to ask

Ask in your own language; the assistant answers in it. A few starting points:

• List my SEOAI brands and the biggest gaps for each.
• Which prompts do we lose over the last 90 days, and which competitor page is cited instead?
• Take the audit for our top gap and write the exact sentence to add to our page, with its placement.
• What did ChatGPT actually answer for that prompt, and which brands did it name?
• Which sites do AI answers cite that we are not on?
• Which Google queries have impressions but no tracked prompt in SEOAI?

The guided workflow

SEOAI also offers a prompt for the most common job. It is called Fix the top gaps and takes a brand and a number of gaps (1 to 10, default 5). Its technical name, which some apps show, is:

fix_top_gaps

It takes the brand's gaps that have a current (ready) audit, most runs first, and writes a change list per page: what to add or change, where, why, and the competitor page cited instead. Gaps without a usable audit, or with an outdated one, are listed with a link where you can start or refresh the audit in SEOAI, because the connection itself cannot start audits. If a gap has no matching page of yours yet, it proposes which page to create. The prompt only proposes; it never publishes.

Where your app shows server prompts depends on the app. If you cannot find it, ask the assistant to run the SEOAI prompt Fix the top gaps for your brand.

Review every change before you publish

Part of what the assistant reads is third-party text: web pages and AI answers. A page could contain sentences written to steer an assistant. SEOAI marks such text as untrusted and tells the assistant to treat it as data, never as instructions, but no filter is perfect. Your review is the safeguard that counts.

Limits

Every tool call and every use of the prompt counts as one call against the monthly quota of the workspace:

• Pro: 2,000 calls per month
• Agency: 10,000 calls per month

The quota is shared by everyone who connects an assistant to the workspace, and it resets at the start of each calendar month, UTC. Every tool answer carries the number of calls left. Listing the available tools is free, and a call that SEOAI refuses because of a limit does not count. Reading data uses no run quota and no audit quota.

There are also two short-term limits: 30 calls per minute per connection and 60 calls per minute per workspace. When one is hit, the assistant is told how many seconds to wait. These numbers may be adjusted as usage grows.

Usage this month and the reset date are shown at the top of the Connected apps page.

Manage and revoke connections

Settings, then Connected apps, lists every connection of the workspace: the app, who connected it, when, and when it was last used. Owners and admins see everyone's connections; members see their own.

Revoke ends a connection at once. The next call from that app is refused, and it cannot renew its access. You can connect again at any time. A connection also stops working when its person is removed from the workspace, and a workspace that loses MCP access, for example after a downgrade, keeps the page so you can still revoke connections.

Your data and the AI provider

When you use SEOAI through an assistant, the Gaps data the assistant asks for leaves SEOAI and goes to the AI provider you connected. That includes prompts, excerpts of AI answers, audit results, competitor pages and search queries of your brands. The provider processes it under its own terms and your agreement with it, for example your Claude or ChatGPT plan. SEOAI does not control that processing, so check the provider's data and training settings, and make sure you may share your clients' data this way.

SEOAI logs each call so it can count your quota and show usage: the tool, the time, the result status, how long it took and how large the answer was, plus the workspace, the person and the app. The log does not contain your questions, the data returned or any tokens. It is kept for 13 months. More on this in the data retention page.

If something does not work

• The consent page says the workspace cannot use the connection: it needs a Pro or Agency plan. Upgrade the workspace on the billing page, or pick another workspace. If the workspace is on Pro or Agency and the page says MCP is not switched on for it, write to hello@seoai.de.
• The assistant reports the quota as used up: wait for the reset date, or upgrade your plan.
• The assistant reports too many requests: it should wait the number of seconds it was given. Ask it to make fewer, more targeted calls.
• A gap has no audit: audits are started in SEOAI on the Gaps page. After one has finished, ask the assistant again.
• Nothing shows for the last 30 days: ask for the last 90 days.
• The connection stopped working: check the Connected apps page. If it is gone, someone revoked it; connect again.