ops MCP server
Commit Oct 13, 2026Exposes the fernedy ops suite as native tools to allow AI agents to perform container forensics and git repository analysis.
Also known as fernedy/ops-mcp
- Stars
- 6
- Tools
- 3
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Oct 13, 2026
- License
- MIT
What is ops MCP?
ops exposes the fernedy ops suite as native tools to allow AI agents to perform container forensics and git repository analysis. It exposes 3 tools, such as container_autopsy, container_obituary, git_sins.
Summary generated from the project's README
About ops MCP server
Performing container forensics and git repository analysis through an AI agent is what ops-mcp enables. This server connects the fernedy ops suite to MCP clients like Claude Desktop, Cursor, or opencode using the stdio protocol. It allows an agent to act as an interface that interprets technical reports rather than requiring you to copy and paste terminal output into a chat window.
Developers can run the server locally using Python or deploy it via Docker by mounting the docker.sock. The server provides three specific tools: container_autopsy for detailed forensic workups, container_obituary for summaries of container lifespans and causes of death, and git_sins for evaluating repository history. All operations are read-only, meaning the agent can diagnose issues without mutating or writing to your infrastructure. The implementation is a single Python file with no external dependencies, using hand-implemented JSON-RPC 2.0 framing.
What you can do with it
- 1Diagnose failed containersAsk an AI agent to investigate why a specific container died and provide a fix.
- 2Summarize container deathsRequest a brief summary of a container's lifespan and the reason it stopped running.
- 3Evaluate repository historyHave an agent analyze a git repository to determine its quality and historical issues.
Written from the project's README. Every use case is checked against a quote from it.
ops MCP tools 3
Detected from the READMEcontainer_autopsycontainer_obituarygit_sins
| container_autopsy | — | |
| container_obituary | — | |
| git_sins | — |
Automated checks
Ran Nov 15, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablefernedy/ops-mcp is public and reachablegithub.com/fernedy/ops-mcp ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-10-13github.com/fernedy/ops-mcp ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model3 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNo tool named like delete, drop or execPass
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHub🔌 ops-mcp
One MCP server. Your AI agent just learned forensics.
Zero dependencies · One file · The MCP framing is implemented by hand
You already have AI agents. What they don't have is your ops tooling.
ops-mcp is a Model Context Protocol server that exposes the fernedy ops suite as native tools for any MCP client — Claude Desktop, opencode, Cursor, or anything that speaks stdio JSON-RPC:
| Tool | Your agent can now ask... |
|---|---|
container_autopsy |
"Why did my-api die last night? Give me evidence and the fix." |
container_obituary |
"Write the obituary for the container that just died." |
git_sins |
"How sinful is the history of this repo we're about to fix?" |
No glue code, no copy-pasting terminal output into a chat window. The agent calls the tool, gets the markdown report, and reasons over it.
⚡ Quickstart
git clone https://github.com/fernedy/ops-mcp.git
git clone https://github.com/fernedy/container-autopsy.git # sibling repos
git clone https://github.com/fernedy/death-noticer.git
git clone https://github.com/fernedy/git-sins.git
cd ops-mcp
python ops_mcp.py # MCP stdio server, ready for any client
Point your MCP client at it (Claude Desktop example):
{
"mcpServers": {
"ops-mcp": {
"command": "python",
"args": ["/path/to/ops-mcp/ops_mcp.py"]
}
}
}
🐳 Deployed with Docker
The image is self-contained: it clones the three tool repos at build time.
docker build -t ops-mcp .
# clients must keep stdin open (-i): MCP speaks stdio
docker run --rm -i -v /var/run/docker.sock:/var/run/docker.sock ops-mcp
Or configure the client directly:
{
"mcpServers": {
"ops-mcp": {
"command": "docker",
"args": ["run", "--rm", "-i",
"-v", "/var/run/docker.sock:/var/run/docker.sock",
"ghcr.io/fernedy/ops-mcp:latest"]
}
}
}
🧰 The tools
container_autopsy(container, tail?)— full forensic workup of a dead (or running) container: evidence table, cause of death, contributing findings, the fix. Powered by container-autopsy.container_obituary(container)— a shorter, warmer goodbye: lifespan, cause of death, final words. Powered by death-noticer.git_sins(repo, share?)— a confession of any git repository: nine sins with evidence and penance, 0–100 Sin Score. Powered by git-sins.
Everything is read-only: the server invokes the tool CLIs in their own repos (OPS_MCP_TOOLS_HOME, defaults to the parent directory). It never restarts, mutates or writes to your infrastructure.
🤖 AI First, by construction
This server is the AI-First layer: the deterministic tools stay the source of truth, and your agent becomes the interface that interprets and explains their reports. Human in the loop is unchanged — tools diagnose, humans act.
🛠️ How it's built
One Python file, zero dependencies. The MCP stdio framing (newline-delimited JSON-RPC 2.0: initialize, tools/list, tools/call, ping) is implemented by hand — read the source as the protocol documentation.
python -m unittest discover -v # 14 tests: real stdio handshake, real tool calls
The suite spawns the actual server process and speaks MCP to it, including a real git_sins call against a real temp repository. CI runs on Python 3.8, 3.10 and 3.12. See .github/workflows/ci.yml.
🗺️ Roadmap
This is step 2 of a linear path: tools → MCP server → guard agent. Step 3 is an always-on agent that listens for container deaths, diagnoses them through this server and prepares the fix as a PR for human approval.
📜 License
MIT — see LICENSE.
Built AI-first by Fernedy Arias · Tech Explorer
If ops-mcp made your agent actually useful at 3 AM, drop a ⭐.
ops MCP questions
What tools does ops MCP provide?
It exposes 3 tools, including container_autopsy, container_obituary, git_sins.
How can I run this server using Docker?
You can run the self-contained image using docker run, ensuring you keep stdin open and mount the docker socket.