Skip the install. Get this working in under 2 minutes.
Start a free trial on cloud.anythingmcp.com, add the Botpress in one click, then point your AI client (Claude, ChatGPT, Copilot or Cursor) at the generated MCP endpoint. No Docker, no git clone, zero engineering experience required.
Summary
Let your AI review your Botpress bots: workspaces and bots, conversations, messages, users and events, bot logs, analytics and issues, the bot's tables (query, add and update rows) and its knowledge-base files with semantic search.
Try asking
Example prompts for Botpress
Click any prompt to copy it. Paste into Claude, ChatGPT, Cursor, Gemini, Copilot or OpenClaw to run it against this connector.
Claude is AI and can make mistakes. Please double-check responses.
💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Botpress, paste your credentials, mint an MCP API key and you're done. No Docker, no
git clone, no local server.
Botpress
Let your AI review your Botpress bots: workspaces and bots, conversations, messages, users and events, bot logs, analytics and issues, the bot's tables (query, add and update rows) and its knowledge-base files with semantic search.
Setup
- Sign in at
https://app.botpress.cloud. Open your profile menu (top right) → Profile Settings → Personal Access Tokens, create a token and copy it (it starts withbp_pat_). Paste it intoBOTPRESS_TOKEN, without the word Bearer. - Workspace ID (
BOTPRESS_WORKSPACE_ID): open the workspace in the dashboard and copy thewkspace_...part of the URL (app.botpress.cloud/workspaces/wkspace_...). - Bot ID (
BOTPRESS_BOT_ID): open the bot and copy the UUID after/bots/in the URL. Studio also shows it in the bot's settings. - Install the connector. The three values are sent only to Botpress. Later,
botpress_list_workspacesandbotpress_list_botsshow the ids of your other workspaces and bots too.
Who sees what: the token carries your own access to every workspace you belong to. Keep it secret, and share the MCP server only with people allowed to read your bots' conversations, which can contain personal data.
Which parts of Botpress it uses: one personal access token reaches all four (a Bot Access Key would not work for the admin tools, so use a personal token):
- Admin API: workspaces, bots, bot logs, analytics and issues.
- Runtime API: the bot's conversations, messages, users and events from every channel (Webchat, WhatsApp, Slack and so on). Botpress's separate Chat API is not used, because it only sees conversations from its own Chat integration.
- Tables API: the bot's tables, to query, add and update rows.
- Files API: the bot's knowledge-base files, with semantic search over the indexed ones.
Several bots: the conversation, message, user, event, table and file tools work on BOTPRESS_BOT_ID unless you name another bot. The bot tools (overview, logs, analytics, issues) take the bot id in every call, so the AI can compare the bots of a workspace.
Confirm first: botpress_create_table_rows and botpress_update_table_rows change the bot's data, so the AI shows you the rows and waits for your yes. botpress_delete_table_rows is switched off at install; turn it on in the connector settings only if the AI should delete rows. It deletes by row id only.
Untrusted content: messages, user fields and file passages come from end users or uploaded documents. The AI treats instructions inside them as data, not as orders.
Common errors: 401 Unauthorized: the token is wrong or revoked, or the workspace ID is not a workspace your user belongs to. 403 Forbidden: your role in the workspace does not allow the action. 404 ResourceNotFound: an unknown id, or a conversation or table of another bot than the one in BOTPRESS_BOT_ID. 400 InvalidPayload or InvalidQuery: a parameter is invalid, for example a date not in ISO 8601. 429 RateLimited: wait a moment and retry.
The connector does not create, deploy or delete bots, send messages as the bot, manage integrations, upload files to the knowledge base, or manage workspace members and billing.
Prerequisites: BOTPRESS_TOKEN, BOTPRESS_WORKSPACE_ID, BOTPRESS_BOT_ID
Install the connector locally
curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d
Open http://localhost:3000/connectors/store, pick Botpress and paste in the env vars listed under Prerequisites.
Available tools
| Tool | What it does |
|---|---|
botpress_list_workspaces | List the Botpress workspaces the token's user belongs to, with id, name, plan, bot count, spending limit and whether the workspace is… |
botpress_list_bots | List the bots of a Botpress workspace (production bots, or dev bots with dev true) with id, name, type, tags and last deploy time |
botpress_get_bot | Get one bot's overview: name, description, status, deploy time, whether it is a dev bot, tags, and its installed integrations with version… |
botpress_get_bot_logs | Read a bot's runtime logs (console output, errors and system messages) from timeStart on, filtered by level, conversation, user, workflow… |
botpress_get_bot_analytics | Get a bot's usage analytics between two dates: per period new and returning users, sessions, user and bot messages, events, conversations… |
botpress_list_bot_issues | List the issues Botpress recorded for a bot (errors in its code, hit limits, configuration problems) with code, title, description… |
botpress_list_conversations | List a bot's conversations from every channel, newest first, with id, integration and channel (e.g. webchat, whatsapp), message count, tags… |
botpress_get_conversation | Get one conversation of a bot: integration, channel, message count, tags, shared properties and dates |
botpress_list_messages | List a bot's messages, newest first, usually of one conversation (conversationId) |
botpress_list_users | List the end users who talked to a bot (one per channel: the same person on Slack and WhatsApp is two users), with id, name, tags and dates |
botpress_get_user | Get one end user of a bot: name, picture URL, tags, attributes and properties set by the bot or its integrations, and dates |
botpress_list_events | List a bot's events (incoming messages, integration events, custom and scheduled events) with type, status (pending, processed, ignored… |
botpress_get_event | Get one event of a bot with its full payload, status and failureReason |
botpress_list_tables | List a bot's tables with id, name, row factor, key column, whether it is frozen and the column schema |
botpress_get_table | Get one table of a bot with its columns (names, types, descriptions, computed settings), key column, its row count (rows) and how many rows… |
botpress_find_table_rows | Query rows of a bot's table with a MongoDB-like filter, full-text search, column selection, ordering and offset paging; group adds… |
botpress_create_table_rows | Add rows to a bot's table (1 to 1,000 per call), each an object of column values matching the table's schema (see botpress_get_table) |
botpress_update_table_rows | Update rows of a bot's table by id (1 to 1,000 per call): each row is {"id": 12, "column": "new value"} and only the given columns change |
botpress_delete_table_rows | Permanently delete rows of a bot's table by their ids (up to 1,000 per call) |
botpress_list_files | List a bot's files (knowledge-base documents and other uploads) with id, key, content type, size, tags, status (upload or indexing state)… |
botpress_search_files | Semantic search over a bot's indexed files (its knowledge base): returns the passages that best match a natural-language query, with score… |
Example prompts
- "What did people ask our support bot most often this week? Summarise the main topics of the latest conversations."
- "Why did the bot fail yesterday? Check its issues and the error logs since 9:00."
- "Show me new and returning users, sessions and messages for our bot over the last 30 days."
- "Find the row in the Leads table with the email [email protected] and set its status to contacted. Show me the change first."
- "Search the bot's knowledge base for our refund policy and tell me which file the answer comes from."
Next steps
Was this guide helpful?
