MCP Server for Z.AI - A Model Context Protocol server that provides AI capabilities
Nothing to run from here
Botpress MCP by usefulapi is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
19
tools declared
remote
at its publisher
—
calls last 7d
What it does
Read bots, logs, analytics, conversations, messages, tables and files in Botpress.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http botpress-mcp-by-usefulapi https://botpress.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# botpress_get_account, botpress_list_workspaces, botpress_list_workspace_members and 16 more
Botpress MCP by usefulapi costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
USAll 598 servers
usefulapi598 servers
25 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http botpress-mcp-by-usefulapi https://botpress.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
19 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Show the Botpress account that owns the token (id, email, display name). Admin API: GET /v1/admin/account/me.
No parameter schema on file.
List the workspaces the token's user can access, with plan, bot count and spending limit. Admin API: GET /v1/admin/workspaces.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| handle | string | no | Filter by workspace handle. |
| nextToken | string | no | Pagination cursor: the meta.nextToken value from the previous response. |
List the members of the connected workspace with their role and email. Admin API: GET /v1/admin/workspace-members.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| nextToken | string | no | Pagination cursor: the meta.nextToken value from the previous response. |
List the bots of the connected workspace (id, name, type, deploy time). Good first call: the other tools need a bot id. Admin API: GET /v1/admin/bots.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dev | boolean | no | If true, list only dev bots. Default: production bots. |
| sortField | string | no | — |
| sortDirection | string | no | Sort direction. |
| nextToken | string | no | Pagination cursor: the meta.nextToken value from the previous response. |
Get one bot: name, type, deploy time, tags and the enabled state of its integrations. The signing secret and integration configuration are left out on purpose. Admin API: GET /v1/admin/bots/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bot_id | string | yes | Bot id (from botpress_list_bots). |
Read the logs of a bot in a time range, with filters for level, user, conversation and message text. Admin API: GET /v1/admin/bots/{id}/logs.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bot_id | string | yes | Bot id (from botpress_list_bots). |
| timeStart | string | yes | Start of the time range, ISO 8601 (for example 2026-11-01T00:00:00Z). |
| timeEnd | string | no | End of the time range, ISO 8601. |
| level | string | no | Filter by log level. |
| userId | string | no | — |
| conversationId | string | no | — |
| workflowId | string | no | — |
| messageContains | string | no | Keep logs whose message contains this text. |
| nextToken | string | no | Pagination cursor: the top-level nextToken value from the previous response. |
Get usage analytics of a bot per period: users, sessions, messages, events and LLM calls, tokens and cost. Admin API: GET /v1/admin/bots/{id}/analytics.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bot_id | string | yes | Bot id (from botpress_list_bots). |
| startDate | string | yes | Start date/time, inclusive, ISO 8601. |
| endDate | string | yes | End date/time, inclusive, ISO 8601. |
List the grouped runtime issues (errors) of a bot with counts and last-seen time. Admin API: GET /v1/admin/bots/{id}/issues.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bot_id | string | yes | Bot id (from botpress_list_bots). |
| nextToken | string | no | Pagination cursor: the meta.nextToken value from the previous response. |
List the conversations of a bot, with channel, integration and message count. Filter by date, channel or participant. Runtime API: GET /v1/chat/conversations.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bot_id | string | yes | Bot id (from botpress_list_bots). |
| channel | string | no | Filter by integration channel name. |
| participantId | string | no | Only conversations with this participant (user id). |
| integrationName | string | no | Filter by integration name. |
| afterDate | string | no | Created on or after this ISO 8601 UTC date. |
| beforeDate | string | no | Created on or before this ISO 8601 UTC date. |
| sortField | string | no | — |
| sortDirection | string | no | Sort direction. |
| nextToken | string | no | Pagination cursor: the meta.nextToken value from the previous response. |
Get one conversation of a bot by id. Runtime API: GET /v1/chat/conversations/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bot_id | string | yes | Bot id (from botpress_list_bots). |
| conversation_id | string | yes | Conversation id. |
List the messages of a bot, for one conversation or for a date range. Runtime API: GET /v1/chat/messages.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bot_id | string | yes | Bot id (from botpress_list_bots). |
| conversationId | string | no | Only messages of this conversation. |
| afterDate | string | no | Created on or after this ISO 8601 UTC date. |
| beforeDate | string | no | Created on or before this ISO 8601 UTC date. |
| nextToken | string | no | Pagination cursor: the meta.nextToken value from the previous response. |
List the end users who talked to a bot. Filter by conversation or date. Runtime API: GET /v1/chat/users.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bot_id | string | yes | Bot id (from botpress_list_bots). |
| conversationId | string | no | Only users of this conversation. |
| afterDate | string | no | ISO 8601 UTC date, inclusive. |
| beforeDate | string | no | ISO 8601 UTC date, inclusive. |
| rangeField | string | no | Field the date range applies to (default createdAt). |
| sortField | string | no | — |
| sortDirection | string | no | Sort direction. |
| nextToken | string | no | Pagination cursor: the meta.nextToken value from the previous response. |
Get one end user of a bot by id. Runtime API: GET /v1/chat/users/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bot_id | string | yes | Bot id (from botpress_list_bots). |
| user_id | string | yes | User id. |
List the Tables of a bot with their schema. Tables API: GET /v1/tables.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bot_id | string | yes | Bot id (from botpress_list_bots). |
Get one Table with its schema, row count and indexing state. Tables API: GET /v1/tables/{table}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bot_id | string | yes | Bot id (from botpress_list_bots). |
| table | string | yes | Table name or id. |
Read rows of a Table with an optional MongoDB-like filter, text search, column selection and sorting. Read only. Tables API: POST /v1/tables/{table}/rows/find.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bot_id | string | yes | Bot id (from botpress_list_bots). |
| table | string | yes | Table name or id. |
| filter | object | no | MongoDB-like filter, for example {"name":{"$eq":"John"}}. |
| search | string | no | Text search term. |
| select | array | no | Columns to return (dot notation for nested). |
| orderBy | string | no | Column to sort by (default id). |
| orderDirection | string | no | Sort direction. |
| limit | integer | no | Rows per page (default 100). |
| offset | integer | no | Rows to skip. |
List the files in the knowledge base of a bot (key, size, type, indexing status). Files API: GET /v1/files.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bot_id | string | yes | Bot id (from botpress_list_bots). |
| indexed | boolean | no | Filter by indexing state. |
| sortField | string | no | — |
| sortDirection | string | no | Sort direction. |
| nextToken | string | no | Pagination cursor: the meta.nextToken value from the previous response. |
Get the metadata of one file of a bot, by id or key. Files API: GET /v1/files/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bot_id | string | yes | Bot id (from botpress_list_bots). |
| file | string | yes | File id or key. |
Semantic search over the indexed files of a bot. Returns the best matching text passages. Files API: GET /v1/files/search.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bot_id | string | yes | Bot id (from botpress_list_bots). |
| query | string | yes | Question or phrase in natural language. |
| limit | integer | no | Maximum passages to return. |
| contextDepth | integer | no | Neighbor passages to add as context (default 1). |
| consolidate | boolean | no | Merge passages of the same file into one. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Botpress MCP by usefulapi or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 1.3.2 · scanned 7 Nov 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 0 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest5ec73170eef8a8c50374df0c2a63093b52bc2eff9bec5e0451ff180e69f88f53
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| botpress_get_account | no tags | |
| botpress_list_workspaces | no tags | |
| botpress_list_workspace_members | no tags | |
| botpress_list_bots | no tags | |
| botpress_get_bot | no tags | |
| botpress_get_bot_logs | no tags | |
| botpress_get_bot_analytics | no tags | |
| botpress_list_bot_issues | no tags | |
| botpress_list_conversations | no tags | |
| botpress_get_conversation | no tags | |
| botpress_list_messages | no tags | |
| botpress_list_users | no tags | |
| botpress_get_user | no tags | |
| botpress_list_tables | no tags | |
| botpress_get_table | no tags | |
| botpress_find_table_rows | no tags | |
| botpress_list_files | sensitive-source | sensitive-source: keyword "list_files" |
| botpress_get_file | no tags | |
| botpress_search_files | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest5ec73170eef8a8c5
Scanned2026-11-07
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.3.2.
1.3.2
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Botpress MCP by usefulapi can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.