Botpress MCP integration for AI agents.
Connect AI agents to Botpress through 3 structured actions, including get bot, list bots, and list workspaces. Review authentication, inputs, workflows, and…
- ACTION CONTRACTS
- 3
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Botpress integration exposes
The Botpress Agent App exposes 3 provider-backed actions for ai and developer tools work. Its current contract lets an authorized agent get details for one botpress bot in the connected workspace, list botpress bots in the connected workspace, and list botpress workspaces accessible to the connected api token. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Botpress account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Botpress capabilities.
Showing 3 of 3 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_botREADGet details for one Botpress bot in the connected workspace.
INPUTS: botId
list_botsREADList Botpress bots in the connected workspace.
INPUTS: dev / tags / nextToken / sortField / sortDirection
list_workspacesREADList Botpress workspaces accessible to the connected API token.
INPUTS: nextToken / handle
INPUT CONTRACTS
Know what the action needs before it runs.
get_bot
botIdOPTIONAL- The Botpress bot ID.
list_bots
devOPTIONAL- Whether to return development bots instead of production bots.
tagsOPTIONAL- Botpress tags to filter by.
nextTokenOPTIONAL- The Botpress meta.nextToken value from the previous response.
sortFieldOPTIONAL- The Botpress field to sort by.
sortDirectionOPTIONAL- The Botpress sort direction.
list_workspaces
nextTokenOPTIONAL- The Botpress meta.nextToken value from the previous response.
handleOPTIONAL- The Botpress workspace handle to filter by.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Bot
Get details for one Botpress bot in the connected workspace. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_botVerify with List Bots
List Botpress bots in the connected workspace. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
list_botsSAFETY BOUNDARY
Operate Botpress with explicit limits
- Authorize Botpress with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Botpress data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Botpress rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Botpress task completed successfully.
CONNECTION MODEL
API key
Botpress API token sent as a Bearer token. Generate a token from the Botpress dashboard API settings and use it with your workspace ID: https://botpress.com/docs/api-reference/admin-api/getting-started.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 3
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Botpress.