MCP DevOps Kit
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| github_list_reposA | List repositories for a GitHub user or organization |
| github_create_issueB | Create a new issue on a GitHub repository |
| github_get_repo_infoB | Get information about a GitHub repository |
| docker_psB | List running Docker containers |
| docker_logsB | Get logs from a Docker container |
| docker_statsB | Get resource statistics for containers |
| fs_lsC | List directory contents |
| fs_readC | Read file contents |
| fs_statsB | Get file or directory statistics |
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 9 tools
Each tool targets a clear and distinct operation: Docker tools cover logs, listing, and stats; filesystem tools cover listing, reading, and stats; GitHub tools cover issue creation, repo info, and repo listing. No overlap across categories.
All tools follow a consistent domain_verb_noun pattern (e.g., docker_logs, fs_ls, github_create_issue), making it easy to infer action and scope from the name.
With 9 tools across three well-defined domains, the count is within the optimal range (3–15). Each tool serves a distinct purpose without redundancy.
The tool set covers only monitoring and basic read operations for Docker and filesystem, and minimal GitHub actions. Missing fundamental operations like container management, file writes, GitHub issues listing/updating, and PR handling. This is a significant gap for a 'DevOps Kit'.