AstrBot MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ASTRBOT_TIMEOUT | No | HTTP 请求超时时间 | 30 |
| ASTRBOT_BASE_URL | No | AstrBot Dashboard 地址 | http://127.0.0.1:6185 |
| ASTRBOT_PASSWORD | No | Dashboard 密码 | |
| ASTRBOT_USERNAME | No | Dashboard 用户名 | |
| ASTRBOT_LOG_LEVEL | No | 日志级别 | INFO |
| ASTRBOTMCP_DISABLE_PROXY | No | 是否禁用代理(防止本地请求被代理拦截) | true |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_astrbot_logsA | 获取 AstrBot 日志。
|
| get_message_platformsB | 获取 AstrBot 中配置的消息平台列表,对应 /api/config/platform/list。 |
| send_platform_message_directB | Directly send a message chain to a platform group/user (bypass LLM). This calls AstrBot dashboard endpoint: POST /api/platform/send_message Notes:
|
| send_platform_messageA | 通过 AstrBot 的 Web Chat API 发送消息链(支持文本、图片、文件等)。 参数:
|
| restart_astrbotB | 重启 AstrBot Core,对应 /api/stat/restart-core。 重启后会等待 AstrBot 重新启动并可用。 |
| get_platform_session_messagesA | Get a platform target's recent messages from AstrBot logs. This tool intentionally uses AstrBot's log broker history (/api/log-history) as the source of truth, since some AstrBot builds do not persist platform conversation history under /api/conversation/detail for group/user targets. Args:
|
| browse_plugin_marketA | 查看 AstrBot 插件市场(支持搜索与按时间排序)。 用法:
返回字段:
|
| list_astrbot_config_filesB | List AstrBot config files (abconfs), via /api/config/abconfs. |
| inspect_astrbot_configB | Inspect a node in an AstrBot config JSON. This tool is designed for step-by-step exploration:
|
| apply_astrbot_config_opsA | Apply multiple edits to an AstrBot config, then save + hot reload. Supported ops (batch in a single tool call):
|
| search_astrbot_config_pathsB | Search AstrBot config and return only matched key paths (no big values). Modes:
Returns:
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| astrbot_info | Basic info resource to allow MCP hosts to discover this server. |
TDQS
Scored across 11 tools
Most tools have distinct purposes, such as config management, message handling, and logging. However, send_platform_message and send_platform_message_direct could be confusing as both involve sending messages, though one targets WebChat and the other real platforms. The descriptions help clarify this, but some overlap exists.
Tool names generally follow a consistent snake_case pattern with descriptive verbs and nouns, like apply_astrbot_config_ops and get_astrbot_logs. There are minor deviations, such as browse_plugin_market using 'browse' instead of 'list' or 'get', but overall the naming is predictable and readable.
With 11 tools, the count is well-suited for managing an AstrBot instance, covering config operations, messaging, logging, and system control. Each tool serves a clear function without redundancy, making the set comprehensive yet manageable for the domain.
The toolset provides strong coverage for AstrBot management, including config inspection, editing, messaging, logging, and system restarts. A minor gap is the lack of tools for plugin installation or management beyond browsing the market, but core workflows are well-supported.