devops-assistant-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| query_databaseA | Execute a SQL query on the local MySQL database. |
| get_system_timeA | Returns the current system time from the MCP server. |
| list_containersA | List all local Docker containers and their current status (running, stopped, etc.). |
| get_container_logsA | Retrieve the last 50 lines of logs from a specific Docker container. |
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 4 tools
Each tool targets a distinct operation: container logs, system time, container listing, and database query. No overlap in purpose.
All tool names follow a consistent verb_noun pattern in snake_case (get_, list_, query_), with clear actions and targets.
With 4 tools, the set is well-scoped for basic DevOps monitoring tasks, each tool earning its place without redundancy.
Major gaps exist for a 'DevOps assistant': missing container management (start/stop/restart), deployment, database schema exploration, and system monitoring beyond time.