Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
QBIT_MANAGE_URLYesThe 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_KEYNoAPI 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_PASSWORDNoPassword for Basic auth when no API key is set. Useful if authentication is enabled.
QBIT_MANAGE_USERNAMENoUsername 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

CapabilityDetails
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

NameDescription
qbit_manage_configA

qbit manage config operations on qbit_manage. Pass operation and an arguments dict matching that operation's parameters.

  • qbit_manage_backup_config(filename) — Create a timestamped manual backup of a config file (keeps up to 30 per config). WRITE: this modifies your qbit_manage instance.

  • qbit_manage_create_config(filename, body={}) — Create a new config file (body is {"data": }). Returns 409 if the file already exists. WRITE: this modifies your qbit_manage instance.

  • qbit_manage_delete_config(filename) — Delete a config file permanently (a backup is created before deletion). DESTRUCTIVE: this deletes data.

  • qbit_manage_get_config(filename) — Fetch a parsed config file. data mirrors the YAML structure; !ENV references are preserved as "!ENV ".

  • qbit_manage_list_config_backups(filename) — List available backups for a config file, newest first.

  • qbit_manage_list_configs() — List available config files in the config directory (sensitive files like qbm_settings.yml are filtered out).

  • qbit_manage_restore_config_from_backup(filename) — Load a backup by name (filename is the backup file name in the path, e.g. config_20260521_100000.yml) and return its data for restoring.

  • qbit_manage_update_config(filename, body={}) — Update an existing config file (body is {"data": }); a timestamped backup is auto-created before writing. WRITE: this modifies your qbit_manage instance.

  • qbit_manage_validate_config(filename, body={}) — Validate a config through the parser without executing (body is {"data": }); defaults backfilled during validation are written back to the real config.

qbit_manage_commandsA

qbit manage commands operations on qbit_manage. Pass operation and an arguments dict matching that operation's parameters.

  • qbit_manage_run_command(body={}) — Run qbit_manage commands against a config (body is a CommandRequest: config_file, commands list, hashes, dry_run, skip_cleanup, skip_qb_version_check, log_level). Valid commands: cat_update, tag_update, recheck, rem_unregistered, tag_tracker_error, rem_orphaned, tag_nohardlinks, share_limits. WRITE: this runs real qbit_manage operations against your qBittorrent instance.

qbit_manage_schedulerA

qbit manage scheduler operations on qbit_manage. Pass operation and an arguments dict matching that operation's parameters.

  • qbit_manage_get_scheduler_status() — Return scheduler status: current schedule (type interval|cron + value), next run time, is_running, source, persistent/file_exists/disabled state.

  • qbit_manage_toggle_schedule_persistence() — Toggle whether the schedule persists across restarts. WRITE: this modifies your qbit_manage instance.

  • qbit_manage_update_schedule(body={}) — Set the schedule (body {"schedule": "1440" or "0 4 * * *", "type": "interval" or "cron" optional}). Takes effect immediately; type auto-detected if omitted. WRITE: this modifies your qbit_manage instance.

qbit_manage_logsA

qbit manage logs operations on qbit_manage. Pass operation and an arguments dict matching that operation's parameters.

  • qbit_manage_get_documentation(file) — Fetch a markdown docs file by name (e.g. Home.md, Commands.md, Config-Setup.md). Returns markdown text, not JSON.

  • qbit_manage_get_logs(limit=None, log_filename=None) — Fetch recent log lines in chronological order. limit caps the tail; log_filename selects the active (.log) or rotated (..log) file (default qbit_manage.log).

  • qbit_manage_list_log_files() — List available log files (active and rotated).

qbit_manage_systemA

qbit manage system operations on qbit_manage. Pass operation and an arguments dict matching that operation's parameters.

  • qbit_manage_force_reset_running_state() — Force-reset the internal is_running flag to recover from a stuck run state. WRITE: this modifies your qbit_manage instance.

  • qbit_manage_get_base_url() — Return the configured base URL the web server is served under (always public).

  • qbit_manage_get_version() — Get the current qbit_manage version with update availability details (always public).

  • qbit_manage_health_check() — Liveness/readiness probe (always public): status healthy|degraded|busy|unhealthy, queue size, config/log directory state, next scheduled run.

qbit_manage_securityA

qbit manage security operations on qbit_manage. Pass operation and an arguments dict matching that operation's parameters.

  • qbit_manage_get_security_settings() — Get security settings (API key and password hash are redacted).

  • qbit_manage_get_security_status() — Get auth summary without sensitive data: has_api_key, method, enabled.

  • qbit_manage_update_security_settings(body={}) — Update security settings (body is a SecuritySettingsRequest: enabled, method none|basic|api_only, username, password, generate_api_key, clear_api_key, trusted_proxies, bypass_auth_for_local, current_* credentials for reauthentication). WRITE: this modifies your qbit_manage instance.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.3/5.0

Scored across 6 tools

Disambiguation5/5

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.

Naming Consistency5/5

Every tool follows the same qbit_manage_<noun> snake_case pattern. The naming is uniform and predictable, making tool selection and routing straightforward.

Tool Count5/5

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.

Completeness5/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo issues