OpsPilot
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPSPILOT_PORT | No | Web UI / HTTP MCP bridge port | 4317 |
| OPSPILOT_DATA_DIR | No | Data directory | ~/.opspilot |
| OPSPILOT_APPROVAL_TIMEOUT_MS | No | Approval timeout | 600000 |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| opspilot_statusA | Return local broker status and listen address. |
| opspilot_probe_remoteA | Verify the broker is ready for a remote connection without exposing stored values. |
| opspilot_list_hostsA | List registered host aliases and optional environment labels. |
| opspilot_describe_hostB | Describe registered services, log path roots (directories), and whether a stored connection is attached. |
| opspilot_inspect_hostB | Inspect one registered host with redacted read-only facts. |
| opspilot_restart_serviceB | Request a single registered service restart for local approval. |
| opspilot_get_requestA | Get the status of a broker request by request ID. |
| opspilot_list_log_filesB | List files under a catalog log root directory. Catalog log_paths are directories; list before fetching. |
| opspilot_fetch_logsA | Fetch a concrete log file under a catalog log root with safe truncation. Do not pass a directory; list files first. |
| opspilot_read_fileA | Read a catalog-allowlisted remote file. |
| opspilot_write_fileC | Request an approved write to a catalog-allowlisted remote file. |
| opspilot_upload_fileB | Request an approved upload to a catalog-allowlisted remote file. |
| opspilot_docker_psA | List remote Docker containers for one registered host. |
| opspilot_docker_logsC | Fetch truncated remote Docker container logs. |
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 14 tools
Most tools have clear, distinct purposes (status vs probe, list vs fetch, etc.). However, describe_host and inspect_host overlap somewhat in that both inspect a registered host, though they emphasize different aspects (services/log paths vs redacted facts).
All tools follow the opspilot_ prefix with a consistent verb_noun pattern (e.g., list_hosts, restart_service, fetch_logs). Minor exception is opspilot_status which is a noun phrase, but it's clearly a status check and doesn't disrupt the overall pattern.
14 tools is well within the ideal range for a focused ops server. Each tool covers a meaningful operation (broker status, host management, logs, file ops, docker) without being excessive or sparse.
The tool set covers core operational workflows: broker health, host discovery, service restart, log retrieval, file operations, and docker inspection. Missing operations like remote command execution or file deletion, but these are likely out of scope for a safety-focused pilot tool.