hephaestus-docker-power
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@hephaestus-docker-power run quick setup for my project at /path/to/project"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Hephaestus Docker Power
A Kiro Power for setting up and managing Hephaestus using Docker containers.
Overview
This power provides MCP tools and steering guides for:
Setting up Hephaestus development environment
Managing Docker containers (Qdrant, MCP server)
Initializing databases
Troubleshooting common issues
Production deployment best practices
Related MCP server: MCP Development Environment
Installation
Option 1: Install via Kiro Powers Panel
Open Kiro
Go to Powers panel
Add this repository URL
Option 2: Manual MCP Configuration
Add to your .kiro/settings/mcp.json:
{
"mcpServers": {
"hephaestus-setup": {
"command": "python",
"args": ["/path/to/hephaestus-docker-power/src/setup_server.py"],
"env": {
"HEPHAESTUS_ROOT": "/path/to/Hephaestus",
"FASTMCP_LOG_LEVEL": "ERROR"
}
}
}
}Available Tools
Tool | Description |
| Verify Python, tmux, git, docker, node, npm are installed |
| Check Docker daemon, Qdrant, MCP server status |
| Start Qdrant vector database container |
| Stop Qdrant container (optionally remove volume) |
| Initialize SQLite and Qdrant databases |
| Check .env has required API keys |
| Update hephaestus_config.yaml with project path |
| Comprehensive health check of all components |
| View logs from server, monitor, or qdrant |
| Full reset (requires confirmation) |
| Complete setup in one command |
Quick Start
# Complete setup in one command
quick_setup(project_path="/path/to/your/project")Or step by step:
check_prerequisites()
validate_env()
start_qdrant()
init_databases()
configure_project("/path/to/project")
health_check()Steering Files
steering/getting-started.md- Full setup walkthroughsteering/troubleshooting.md- Common issues and solutionssteering/production.md- Production deployment guide
Requirements
Python 3.10+
Docker
fastmcp (
pip install fastmcp)pyyaml (
pip install pyyaml)
Environment Variables
HEPHAESTUS_ROOT- Path to Hephaestus installation (defaults to current directory)FASTMCP_LOG_LEVEL- Log level for MCP server (default: ERROR)
License
MIT
Available Tools
7 toolscheck_prerequisitesB
Check if all required tools are installed for running Hephaestus.
Inputs: no named parameters. Returns: object
check_servicesA
Check the status of Docker daemon, Qdrant, and MCP server.
Inputs: no named parameters. Returns: object
health_checkB
Perform comprehensive health check of all Hephaestus services.
Inputs: no named parameters. Returns: object
start_qdrantB
Start the Qdrant vector database container.
Inputs: no named parameters. Returns: object
stop_qdrantC
Stop the Qdrant container.
Inputs: remove_volume. Returns: object
validate_envA
Validate the .env file has required API keys configured.
Inputs: no named parameters. Returns: object
view_logsB
View recent logs from a Hephaestus service (qdrant, server, or monitor).
Inputs: service, lines. Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Official Sevalla MCP: deploy, debug and manage apps, static sites and databases.
Manage CloudPepper servers, Odoo instances, backups, and deployments over MCP.
Manage Pipefork API projects, drafts, connections, secrets, and deployments through MCP.
Create, deploy, and operate MCP servers directly from your GitHub repositories.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables remote Docker management over SSH via a local MCP server, providing tools to manage containers, images, Compose, and system resources.1GPL 3.0
- AlicenseNot gradedqualityDmaintenanceProvides a Docker-based development environment with Python and Node.js MCP servers, enabling file operations, SQL queries, Redis caching, and debugging for building and testing MCP servers.MIT
- FlicenseNot gradedqualityDmaintenanceEnables Docker container management and test execution via MCP tools, supporting image building, container operations, and automated test runs.-
- FlicenseNot gradedqualityDmaintenanceEnables managing a local Minecraft hosting service through MCP, including server creation, start/stop, mod installation, and log retrieval.-