hephaestus-docker-power
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HEPHAESTUS_ROOT | No | Path to Hephaestus installation (defaults to current directory) | current directory |
| FASTMCP_LOG_LEVEL | No | Log level for MCP server (default: ERROR) | ERROR |
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 |
|---|---|
| check_prerequisitesB | Check if all required tools are installed for running Hephaestus. |
| check_servicesA | Check the status of Docker daemon, Qdrant, and MCP server. |
| start_qdrantB | Start the Qdrant vector database container. |
| stop_qdrantC | Stop the Qdrant container. |
| validate_envA | Validate the .env file has required API keys configured. |
| health_checkB | Perform comprehensive health check of all Hephaestus services. |
| view_logsB | View recent logs from a Hephaestus service (qdrant, server, or monitor). |
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 7 tools
Tools are mostly distinct but check_services and health_check overlap slightly; both check service status but health_check is more comprehensive.
All tool names follow a consistent verb_noun pattern with snake_case, e.g., check_prerequisites, start_qdrant, view_logs.
7 tools is a reasonable number for managing Docker services, though adding start/stop for other services could be beneficial.
Covers prerequisites, service checks, Qdrant lifecycle, env validation, and logs but lacks start/stop for server/monitor and restart operations.