cubox-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port number for HTTP transport (only used when MCP_TRANSPORT=http). | 3000 |
| CUBOX_TOKEN | Yes | The token from your Cubox API Extension link (e.g., last path segment of https://cubox.pro/c/api/save/abcd12345). Required when not using interactive login. | |
| CUBOX_SERVER | No | Cubox server domain. Use cubox.pro for China instance, cubox.cc for international instance. | cubox.pro |
| CUBOX_CLI_BIN | No | Override path to the cubox-cli binary. Default: auto-resolved via dependency. | |
| MCP_TRANSPORT | No | Transport mode: stdio (for mcphub/Claude Desktop) or http (for standalone HTTP server). | stdio |
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 |
|---|---|
| cubox_cliA | Run any cubox-cli command and get its JSON output back. This is a thin, generic pass-through — it does not enumerate Cubox's capabilities itself. If you don't know what's available, first call this tool with args: ['--help'], or args: ['', '--help'] (e.g. ['card', '--help']) to discover current sub-commands and flags directly from the CLI, since they may change over time. Example: args: ['card', 'list', '--folder', 'Reading'] lists cards in a folder. Destructive operations (delete/remove) are blocked unless a force/confirm flag is included in args — call once without it to see a dry-run / confirmation prompt, then call again with the force flag the CLI reports (e.g. --force) once you've confirmed the target is correct. |
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 1 tool
With only a single tool, there is no possibility of confusion between tools. The tool's description clearly states its purpose as a generic CLI pass-through, leaving no room for ambiguity.
A single tool inherently follows a consistent naming pattern. The name 'cubox_cli' is clear and matches the server's purpose, so there are no inconsistencies to penalize.
One tool is at the low end of typical server scopes, but it acts as a general-purpose gateway to the entire Cubox CLI. This can be seen as minimalistic yet functional, though it may feel thin compared to more structured multi-tool servers.
The generic pass-through tool allows access to all cubox-cli commands, including destructive operations with safeguards. Agents can discover and execute any CLI command, making the tool surface complete for the targeted domain.