Skip to content

Artificial Intelligence

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.

  • 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 Botpress to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Botpress once

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

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

  3. Paste a Botpress API key. One person generates a token in Botpress 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.

botpress
Botpress
AirOps
Algolia
Chatvolt
Cohere
DigitalOcean
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 Botpress 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 Botpress 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 Botpress 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 Botpress 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 Botpress through Elaichi

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

  • 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.”

See all 198 Botpress tools below

AI tools

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.

See it in Elaichi

What connecting Botpress gets you

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

The agent

Ask about Botpress integrations in plain language.

Starter prompts pull live hub integrations, plugins and admin accounts into an answer.

  • integrations
  • plugins
  • admin accounts
  • account pats

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 or Cursor

MCP clients

Claude, ChatGPT and Cursor reach Botpress here.

One org MCP endpoint over OAuth, no SDK work and no shared API key.

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

198 Botpress tools are ready to call.

Hub integrations, plugins, admin accounts and account PATs, with no custom code written.

  • Create a Botpress helper vrl
  • Delete a Botpress admin account by ID
  • List all Botpress admin accounts
  • Botpress admin accounts bulk update
ElaichiTools
Tool Action Description
Create a Botpress helper vrl Create Run a VRL (Vector Remap Language) script in Botpress. Returns the result of the script execution.
Delete a Botpress admin account by ID Delete Delete the Botpress account associated with the authenticated user. Returns: id, name, createdAt, updatedAt.
List all Botpress admin accounts List Retrieve the current authenticated account's profile, including email, display name, email verification status, and profile picture.
Botpress admin accounts bulk update Update Update details of the Botpress account associated with the authenticated user. Returns: id, name, createdAt, updatedAt.
List all Botpress account pats List List Personal Access Tokens (PATs) for the authenticated Botpress account. Returns: id, createdAt, updatedAt.

Toolboxes

Each team gets its own Botpress toolbox.

Curate one toolbox per team so support, platform and analytics see different Botpress tools.

  • Support
  • Platform
  • Security
  • Analytics
ElaichiToolboxes
Name Source template Tools Created

Support toolbox

Botpress · bot conversations and handoffs

Botpress starter 18 Mar 4, 2026

Platform toolbox

Botpress · hub integrations and plugins

9 Mar 2, 2026

Security toolbox

Botpress · admin accounts and PATs

24 Feb 27, 2026

Analytics toolbox

Botpress · conversation and usage records

Botpress starter 6 Feb 19, 2026

Product toolbox

Botpress · bot flows and preferences

31 Jan 30, 2026

Partnerships toolbox

Botpress · third party hub integrations

12 Jan 22, 2026

Shared connections

Share a Botpress account, never the token.

The connections table shows who connected each account and which teams and members use it.

  • Support EMEA
  • Platform
  • Security
  • Analytics
ElaichiConnections
Connection Scope Status Access
BO

Botpress (Support EMEA)

Connected by Emma Laurent

Personal • Active 1 team · 6 members
BO

Botpress (Platform)

Connected by James Whitfield

Organization • Active 3 teams · 24 members
BO

Botpress (Security)

Connected by Sofia Ricci

Organization • Active 2 teams · 11 members
BO

Botpress (Analytics)

Connected by Daniel Ortega

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

Botpress (Product)

Connected by Clara Nowak

Personal • Active Not shared
BO

Botpress (Partner bots)

Connected by Michael Brennan

Personal • Active 2 teams · 9 members

Audit log

Every Botpress call has a name on it.

When, who, what happened, type and resource, appended for each plugin and integration call.

  • 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]

Botpress Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

C

Clara Nowak

[email protected]

Botpress Integrations Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

M

Michael Brennan

[email protected]

Botpress Integrations 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 whole Botpress digest.

Six steps fetch integrations, group them, draft a digest, wait for approval, post back.

Botpress digest

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

  1. Schedule

    Every weekday at 08:00

    0.2s
  2. Fetch integrations

    Botpress

    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

    Botpress

    Queued

Collections and dashboards

Botpress health arrives before anyone asks.

Four metrics, 14 days of records created and a team breakdown, computed without a model.

Botpress health

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

Live

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%

FAQ

Frequently asked questions

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, 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 hiding deletions from a team, but it can never widen what Botpress itself allows.

Can my team share one Botpress connection?

Yes. One administrator connects Botpress in Elaichi and shares the connection with a team, and nobody else ever handles the Botpress API key. Each teammate still signs in to Elaichi as themselves, so the audit log names the person who listed the accounts or created the bot, not a shared login.

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 blocking deletion of admin accounts or tokens. A blocked action is never shown to Claude, ChatGPT or any other client at all, so no prompt, however worded, can reach it.

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.

Put Botpress in front of your team

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