Doubao Desktop
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DOUBAO_APP | Yes | Absolute path to the Doubao desktop executable (e.g., C:\Path\To\Doubao.exe). | |
| DOUBAO_DATA_DIR | Yes | Path to the Doubao User Data directory, typically %LOCALAPPDATA%\Doubao\User Data. | |
| DOUBAO_CLI_ENTRY | Yes | Absolute path to the doubao-cli entry script (deps/doubao-cli/bin/doubao.mjs). | |
| DOUBAO_CLI_CONFIG_DIR | Yes | Directory for doubao-cli configuration/data (e.g., .\data). |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| doubao_desktop_statusA | Check whether the localhost CDP endpoint belongs to the Doubao desktop app. Does not restart it. |
| doubao_desktop_sessionsB | List existing Doubao desktop conversations. Treat titles and messages as private user data. |
| doubao_desktop_create_taskB | Send a new task to a real Doubao desktop conversation in an existing local workspace. Returns conversationId and runId; inspect task result independently. |
| doubao_desktop_continue_taskB | Send a follow-up to a specified existing Doubao desktop conversation. Does not choose a conversation automatically. |
| doubao_desktop_waitC | Wait for an already submitted desktop run. A completed reply still requires independent artifact review. |
| doubao_desktop_readC | Read messages from a specified Doubao desktop conversation. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct action: create_task vs continue_task are clearly separated (new vs follow-up), read vs sessions separate message reading from conversation listing, and wait vs status separate run-waiting from endpoint checking. Descriptions explicitly call out these boundaries, so an agent can reliably pick the right tool.
All tools share the consistent doubao_desktop_ prefix and mostly use a verb_noun or action pattern (create_task, continue_task). Minor deviation: read, status, and sessions are bare nouns rather than verb_noun forms, but the set is still predictable and readable.
Six tools is well-scoped for a desktop-conversation automation server, with each tool (submit, follow up, wait, read, list, health-check) earning its place. No bloat or obvious redundancy.
Core lifecycle (submit -> wait -> read) plus session listing and status is covered, but there is no way to cancel/stop an in-flight run, close or delete a conversation, or perform the 'independent artifact review' the descriptions repeatedly reference. These gaps are notable though agents can partially work around them.