Skip to content

Analytics

Botify MCP connector

The Botify connector brings crawl analyses, segments, orphan URLs, sitemaps reports and search console stats to Claude, ChatGPT, Cursor and the Elaichi Agent, so each person can ask about their site's SEO health inside their own Botify access.

  • How it connects. Connects with an API key. The credential goes into a vault nobody reads back.

  • One address. https://api.elaichi.ai/mcp, the same for every user.

  • Their own access. An agent never gets more than the person it acts for.

How to connect

How to connect Botify to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Botify once

  1. Open Connections, choose Add connection, and pick Botify.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Paste a Botify API key. One person generates a token in Botify and pastes it once. Everyone else works through Share with, and never sees it.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

botify
Botify
Allium
Amplitude
Artie
DoiT
Google Analytics
2

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

Connect Botify to Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Connect Botify to ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Connect Botify to Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Connect Botify to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

Use cases

What teams do with Botify through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • SEO

    Check the latest crawl before standup

    Ask which Botify analyses finished overnight, pull the health lights and scoring summary, and know what changed on the site before anyone asks.

  • Content

    Find pages losing search traffic

    Pull search console stats by segment and see which sections of the blog or help center are slipping, then decide what to refresh first.

  • Web engineering

    Catch orphan and out-of-config pages

    List URLs that get visits or analytics traffic but have no internal links, and review sample pages that fell outside the crawl configuration before a release.

  • Marketing

    See where links and authority are going

    Ask for top domains and subdomains, link percentiles and lost pagerank across segments, and report on campaign landing pages without opening a dashboard.

  • Ecommerce

    Keep sitemaps and robots.txt in shape

    Review sitemaps reports and pages found only in the sitemap, and read the current robots.txt index in Botify before a category launch.

  • Agency

    Run and manage crawls for client sites

    Launch a new analysis, pause or resume a running one, and pull a single URL's crawl details when a client asks why a page is not indexed.

Try asking

  • “List orphan URLs from the latest analysis”
  • “Which segments lost the most pagerank this month?”
  • “Summarize search console stats for the blog segment”

See all 48 Botify tools below

AI tools

Botify tools for your AI agents

48 tools are ready to call through Elaichi's MCP endpoint the moment you connect Botify, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting Botify gets you

6 screens from the product, each doing one job for your Botify account.

The agent

Ask about your Botify crawls in plain language.

Get answers from live analyses, segments and search console stats, not exported spreadsheets.

  • analyses
  • segments
  • sitemaps
  • urls

Ask Elaichi to work across your apps.

List orphan URLs from the latest analysis

Which segments lost the most pagerank this month?

Summarize search console stats for the blog segment

Also runs in Claude, ChatGPT or Cursor

MCP clients

Botify works in Claude, ChatGPT and Cursor.

One governed endpoint, every MCP client, no SDK and no shared API key to pass around.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emma Laurent

• Connected 4 minutes ago
Cursor
S

Sofia Ricci

• Connected 2 hours ago
ChatGPT
C

Clara Nowak

• Connected Yesterday

Tool catalog

48 Botify tools, ready with no code.

Analyses, crawl statistics, orphan URLs, sitemaps reports and segments, covered without writing a connector.

  • List all Botify analyses
  • Botify analyses pause
  • Botify analyses resume
  • Get single Botify analysis by ID
ElaichiTools
Tool Action Description
List all Botify analyses List List all Botify analyses for a project. Returns each analysis with slug, name, status, url, date_launched, date_finished, and additional crawl metadata. Required: username, project_slug.
Botify analyses pause Pause Pause a running Botify analysis for a project. Returns the analysis object with slug, name, status, url, date_launched, and additional crawl metadata. Required: username, project_slug, analysis_slug.
Botify analyses resume Resume Resume a paused Botify analysis for a project. Returns the analysis object with slug, name, status, url, date_launched, and additional crawl metadata. Required: username, project_slug, analysis_slug.
Get single Botify analysis by ID Get Get a single Botify analysis by id. Returns: user, owner, slug, name, friendly_name, url, status, computing_revision, features, urls_done, urls_in_queue, config, date_launched, date_finished, date_last_modified, date_created, date_crawl_done, failures, red_button_domain, import_keywords_data, import_keywords_data_by_country, crawl_launch_type, to_be_deleted_at, comparable, excluded_from_trends,…. Required: id, username, project_slug.
Create a Botify create launch Create Create and launch an analysis for a Botify project. Returns the created analysis launch response object. Required: username, project_slug.

Toolboxes

Every team gets its own Botify toolbox.

SEO sees crawl results, content sees scoring summaries, each team scoped to its own work.

  • SEO
  • Content
  • Web engineering
  • Marketing
ElaichiToolboxes
Name Source template Tools Created

SEO toolbox

Botify · crawl analyses and segments

Botify starter 18 Mar 4, 2026

Content toolbox

Botify · scoring summaries and search console stats

9 Mar 2, 2026

Web engineering toolbox

Botify · robots.txt, sitemaps reports and crawl statistics

24 Feb 27, 2026

Marketing toolbox

Botify · top domains, subdomains and visits

Botify starter 6 Feb 19, 2026

Ecommerce toolbox

Botify · category segments and orphan URLs

31 Jan 30, 2026

Analytics toolbox

Botify · link percentiles and lost pagerank

12 Jan 22, 2026

Shared connections

Share one Botify connection, never the API key.

One person connects Botify, teams and members work through it without seeing a credential.

  • SEO
  • Content
  • Web engineering
  • Marketing
ElaichiConnections
Connection Scope Status Access
BO

Botify (SEO)

Connected by Emma Laurent

Personal • Active 1 team · 6 members
BO

Botify (Content)

Connected by James Whitfield

Organization • Active 3 teams · 24 members
BO

Botify (Web engineering)

Connected by Sofia Ricci

Organization • Active 2 teams · 11 members
BO

Botify (Marketing)

Connected by Daniel Ortega

Personal • Needs re-auth 1 team · 3 members
BO

Botify (Ecommerce)

Connected by Clara Nowak

Personal • Active Not shared
BO

Botify (Agency clients)

Connected by Michael Brennan

Personal • Active 2 teams · 9 members

Audit log

Every Botify call is logged, with a name.

See who paused an analysis or launched a crawl, when, and on which project.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emma Laurent

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

James Whitfield

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

S

Sofia Ricci

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

D

Daniel Ortega

[email protected]

Botify Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

C

Clara Nowak

[email protected]

Botify Analyses Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

M

Michael Brennan

[email protected]

Botify Analyses List Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

A schedule runs the Botify crawl digest.

Analyses are fetched, grouped, drafted into a digest, approved by a person, then posted back.

Botify digest

Run 418 · started 2 minutes ago · on behalf of Emma Laurent

  1. Schedule

    Every weekday at 08:00

    0.2s
  2. Fetch analyses

    Botify

    1.4s
  3. Group by owner

    Transform

    0.1s
  4. Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. Post the digest

    Botify

    Queued

Collections and dashboards

Botify crawl health, computed without a model.

Four metrics, 14 days of analyses created, a breakdown by team, refreshed on a schedule.

Botify health

Refreshed 4 minutes ago · every 15 minutes · from the analyses collection

Live

Analyses

1,284 ↓ 12%

Segments

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Analyses created

Last 14 days

By team

Share of activity

SEO 34%

Content 27%

Web engineering 21%

Marketing 18%

FAQ

Frequently asked questions

How do I connect Botify to Claude?

Two steps. First, connect Botify in Elaichi by pasting in your Botify API key, there is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste the Elaichi endpoint, https://api.elaichi.ai/mcp. Claude will ask you to sign in to Elaichi as yourself, and Botify is ready.

Does Botify work with ChatGPT and Cursor as well as Claude?

Yes. Botify is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any MCP client and the Elaichi Agent. There is nothing extra to set up per client.

What can an AI agent actually do with my Botify data?

It can list your Botify analyses, launch, pause or resume a crawl, and read the results: health lights, crawl statistics, scoring summaries, search console stats, sitemaps reports, orphan URLs, link percentiles, lost pagerank and top domains. It can look at segments, the robots.txt index and the crawl details of a single URL. Because Botify offers a lot of tools, short concrete asks such as "orphan URLs, latest analysis, main site" work better than long sentences.

Does connecting Botify give the AI access to every project?

No. Every request runs as the person who signed in, so the AI sees only the Botify projects and analyses that person can already see in Botify. Elaichi can narrow that further by team, and it can never widen it beyond what Botify itself allows.

Can my team share one Botify connection?

Yes. One person connects Botify with the API key, shares the connection with a team in Elaichi, and nobody else ever handles the key. Each teammate still signs in to Elaichi as themselves, so the audit log names the person who paused an analysis or launched a crawl, not a shared account.

Can I stop an agent from launching, pausing or changing things in Botify?

Yes. Restrictions in Elaichi work per action, so you can allow reading Botify analyses and crawl results while blocking the ability to launch, pause or resume a crawl. A blocked action is never advertised to Claude, ChatGPT or Cursor, so no prompt can reach it.

What happens to a Botify connection when someone leaves?

Offboarding that person in Elaichi ends their Botify access at once, across every client they used. If the Botify connection was shared, it keeps working for everyone else on the team. Disconnecting Botify once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client at the same time.

Put Botify in front of your team

Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.