qbit_manage-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| QBIT_MANAGE_URL | Yes | The base URL of the qbit_manage instance, e.g. http://qbit-manage.example.com:8181. Include subpath if served under a base URL. | |
| QBIT_MANAGE_API_KEY | No | API key for qbit_manage. Required if authentication is enabled and you are not using Basic auth (username/password). Sent as a header if set. | |
| QBIT_MANAGE_PASSWORD | No | Password for Basic auth when no API key is set. Useful if authentication is enabled. | |
| QBIT_MANAGE_USERNAME | No | Username for Basic auth when no API key is set. Useful if authentication is enabled. |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| qbit_manage_configA | qbit manage config operations on qbit_manage. Pass
|
| qbit_manage_commandsA | qbit manage commands operations on qbit_manage. Pass
|
| qbit_manage_schedulerA | qbit manage scheduler operations on qbit_manage. Pass
|
| qbit_manage_logsA | qbit manage logs operations on qbit_manage. Pass
|
| qbit_manage_systemA | qbit manage system operations on qbit_manage. Pass
|
| qbit_manage_securityA | qbit manage security operations on qbit_manage. Pass
|
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
The six tools are clearly separated by resource domain: config, commands, scheduler, logs, system, and security. There is no meaningful overlap in purpose, so an agent can reliably choose the right tool.
Every tool follows the same qbit_manage_<noun> snake_case pattern. The naming is uniform and predictable, making tool selection and routing straightforward.
Six tools is a well-scoped count for managing a qbit_manage instance. Each tool represents a distinct functional area without unnecessary proliferation or overlap.
The tool surface covers config lifecycle, backup/restore, validation, command execution, scheduling, logs, system health/version, and security settings. These are the core domains needed to operate and manage a qbit_manage server, with no obvious critical gaps.