Botify MCP connector
The Botify connector brings crawl analyses, segments, orphan URLs, sitemaps reports and search console stats to Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, so each person can ask about their site's SEO health inside their own Botify access.
- Connects with an API key
- Free 14-day trial
- No credit card
List orphan URLs from the latest analysis
Working in Botify with Elaichi
-
List all Botify analyses
-
Get single Botify analysis by ID
-
List all Botify lights
How to connect Botify to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Botify MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Botify MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Botify MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
Botify MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
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.
Botify MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Botify to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
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.
What teams do with Botify through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Botify is logged.
-
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”
What connecting Botify gets you
6 screens from Elaichi, each doing one job for your Botify account.
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, Cursor or Microsoft Copilot
The agent
Ask about your Botify crawls in plain language.
Get answers from live analyses, segments and search console stats, not exported spreadsheets.
Copy the endpoint
AI apps
Botify works in Claude, ChatGPT, Cursor and Microsoft Copilot.
One governed endpoint, every MCP client, no SDK and no shared API key to pass around.
Tool catalog
48 Botify tools, ready with no code.
Analyses, crawl statistics, orphan URLs, sitemaps reports and segments, covered without writing a connector.
Toolboxes
Every team gets its own Botify toolbox.
SEO sees crawl results, content sees scoring summaries, each team scoped to its own work.
Shared connections
Share one Botify connection, never the API key.
One person connects Botify, teams and members work through it without seeing a credential.
Audit log
Every Botify call is logged, with a name.
See who paused an analysis or launched a crawl, when, and on which project.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
Botify digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch analyses
Botify
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Botify
Queued
Automations
A schedule runs the Botify crawl digest.
Analyses are fetched, grouped, drafted into a digest, approved by a person, then posted back.
Botify health
Refreshed 4 minutes ago · every 15 minutes · from the analyses collection
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%
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.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Botify
All three can connect Botify to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Botify tools | Allow or restrict single Botify tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Botify call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
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.
No tools match your search.
Questions, answered
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, Microsoft Copilot, 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 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 restricting the ability to launch, pause or resume a crawl. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.
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, Microsoft Copilot and every other client at the same time.
Does the Botify MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Botify is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Botify?
Yes. Both let Claude, ChatGPT or Cursor use Botify. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Botify call.
How is Elaichi different from Composio for Botify?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Botify: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Botify in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot