Botpress MCP connector
The Botpress connector brings your bots, admin accounts, access tokens and hub plugins into Claude, ChatGPT and Cursor through one governed endpoint, so each person works inside their own Botpress access with every action logged.
- Connects with an API key
- Free 14-day trial
- No credit card
List all Botpress hub integrations added this month.
Working in Botpress with Elaichi
-
List all Botpress admin accounts
-
List all Botpress account pats
-
Get single Botpress account preference by ID
How to connect Botpress to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Botpress 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.
Botpress 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.
Botpress 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.
Botpress 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.
Botpress 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 Botpress 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 Botpress through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Botpress is logged.
-
Support
Spin up a bot for a new queue
Ask for a new Botpress bot when a product line or region gets its own support desk, then check it appears in the bot list alongside the ones already running.
-
IT
Audit who holds admin access
Pull the full list of Botpress admin accounts before a quarterly review, spot accounts that belong to people who have moved on, and remove them by ID.
-
Security
Clean up stale personal access tokens
List every personal access token on the Botpress account, retire the ones nobody recognizes, and issue a fresh token for a new automation without opening the console.
-
Product
Browse the hub before you build
Look up Botpress hub plugins and interfaces by name to see what already exists before the team commits a sprint to building the same thing.
-
Operations
Keep the bot inventory straight
Get a plain list of every Botpress bot in the workspace with its ID, so the runbook and the on-call sheet match what is actually deployed.
-
Workspace admins
Update many accounts in one pass
Apply the same change across a batch of Botpress admin accounts at once, and set account preferences for new starters so their workspace looks right on day one.
Try asking
- “List all Botpress hub integrations added this month.”
- “Which admin accounts hold active Botpress account PATs?”
- “Show Botpress hub plugins used by the support bot.”
What connecting Botpress gets you
6 screens from Elaichi, each doing one job for your Botpress account.
Ask Elaichi to work across your apps.
List all Botpress hub integrations added this month.
Which admin accounts hold active Botpress account PATs?
Show Botpress hub plugins used by the support bot.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about Botpress integrations in plain language.
Starter prompts pull live hub integrations, plugins and admin accounts into an answer.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach Botpress here.
One org MCP endpoint over OAuth, no SDK work and no shared API key.
Tool catalog
198 Botpress tools are ready to call.
Hub integrations, plugins, admin accounts and account PATs, with no custom code written.
Toolboxes
Each team gets its own Botpress toolbox.
Curate one toolbox per team so support, platform and analytics see different Botpress tools.
Shared connections
Share a Botpress account, never the token.
The connections table shows who connected each account and which teams and members use it.
Audit log
Every Botpress call has a name on it.
When, who, what happened, type and resource, appended for each plugin and integration call.
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.
Botpress digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch integrations
Botpress
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
Botpress
Queued
Automations
A schedule runs the whole Botpress digest.
Six steps fetch integrations, group them, draft a digest, wait for approval, post back.
Botpress health
Refreshed 4 minutes ago · every 15 minutes · from the integrations collection
Integrations
1,284 ↓ 12%
Plugins
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Integrations created
Last 14 days
By team
Share of activity
Support EMEA 34%
Platform 27%
Security 21%
Analytics 18%
Collections and dashboards
Botpress health arrives before anyone asks.
Four metrics, 14 days of records created and a team breakdown, computed without a model.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Botpress
All three can connect Botpress 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 Botpress tools | Allow or restrict single Botpress 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 Botpress 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.
Botpress tools for your AI agents
198 tools are ready to call through Elaichi's MCP endpoint the moment you connect Botpress, 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 Botpress to Claude?
First, connect Botpress inside Elaichi by pasting a Botpress API key when asked, which takes about a minute. 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 https://api.elaichi.ai/mcp. Sign in with your Elaichi account and Botpress is available in the conversation.
Does Botpress work with ChatGPT and Cursor as well as Claude?
Yes. Botpress connects to Elaichi once, and the same endpoint, https://api.elaichi.ai/mcp, is added to Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You do not repeat the Botpress setup for each client, and every client follows the same restrictions and writes to the same audit log.
What can an AI agent actually do with my Botpress data?
With Botpress connected, an agent can list your bots and create new ones, show every admin account and remove or update them, manage personal access tokens and account preferences, and look up plugins and interfaces in the Botpress hub by name. Because Botpress exposes a large number of actions, the agent searches for the right one as you ask, so short concrete requests such as "list all admin accounts" work better than long paragraphs.
Does connecting Botpress give the AI access to my whole workspace?
No. Access follows the person who signed in, so an agent working through Botpress sees only the bots, accounts and tokens that person's Botpress API key can already reach. Elaichi can narrow that further, for example by restricting deletions for a role, but it can never widen what Botpress itself allows.
Can I stop an agent from deleting or changing things in Botpress?
Yes. Restrictions in Elaichi apply per action, so you can allow listing Botpress bots and accounts while restricting deletion of admin accounts or tokens. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT or any other client cannot run it, whatever the prompt says.
What happens to a Botpress connection when someone leaves?
Offboarding a person in Elaichi ends their access to Botpress through every connected client at once, with nothing to revoke in Claude or ChatGPT separately. If they connected a shared Botpress account, it keeps working for everyone else on the team. Disconnecting Botpress once in Elaichi removes it from every client for everyone.
Does the Botpress MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Botpress 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 Botpress?
Yes. Both let Claude, ChatGPT or Cursor use Botpress. 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 Botpress call.
How is Elaichi different from Composio for Botpress?
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 Botpress: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Botpress 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