MCP DevOps Kit
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., "@MCP DevOps Kit list my GitHub repositories"
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.
CodeBlueprint — MCP Servers
Model Context Protocol (MCP) servers for AI coding agents by CodeBlueprint.
Available Servers
mcp-devops-kit
GitHub, Docker, and filesystem tools for AI coding agents. View on GitHub: https://github.com/Jmfrodero/codeblueprint-mcp/tree/main/devops-kit
Related MCP server: GitHub MCP Server
Roadmap
mcp-docs-generator (in development)
mcp-spain-tools (planned)
Available Tools
9 toolsdocker_logsB
Get logs from a Docker container
Inputs: container_id (required), lines, tail.
docker_psB
List running Docker containers
Inputs: all.
docker_statsB
Get resource statistics for containers
Inputs: container_id, stream.
fs_lsC
List directory contents
Inputs: path (required).
fs_readC
Read file contents
Inputs: path (required), max_lines.
fs_statsB
Get file or directory statistics
Inputs: path (required).
github_create_issueB
Create a new issue on a GitHub repository
Inputs: owner (required), repo (required), title (required), body, +1 more.
github_get_repo_infoB
Get information about a GitHub repository
Inputs: owner (required), repo (required).
github_list_reposA
List repositories for a GitHub user or organization
Inputs: owner (required), type, per_page.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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'.
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
A Model Context Protocol (MCP) application for automated GitHub PR analysis and issue management.…
A MCP server built for developers enabling Git based project management with project and personal…
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA modular server that implements the Model Context Protocol standard, providing tools for interacting with GitHub, GitLab, Google Maps, Memory storage, and web automation through a unified gateway.556 npm3Apache 2.0
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI assistants to perform GitHub operations including repository management, file operations, issue tracking, and pull request creation.2-
- FlicenseNot gradedqualityNot gradedmaintenanceModel Context Protocol server that enables interaction with GitHub repositories, issues, pull requests, and search functionality through natural language.1-
- -licenseCqualityNot gradedmaintenanceA Model Context Protocol server with GitHub API integration that enables interaction with repositories, issues, pull requests, and file management through a standardized interface.1-