P12 SRE Ops MCP Server
Click on "Install 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., "@P12 SRE Ops MCP Servercheck SLO status for payment service"
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.
P12 · SRE Ops MCP Server
Custom MCP (Model Context Protocol) server exposing SRE tools as LLM-callable actions. Capstone project of the Staff SRE · AI Engineer Portfolio.
Where things live
What | Where |
MCP server code | This repo ( |
Interactive demo | |
Tool examples + audit log |
Related MCP server: PilotOps MCP
Tools exposed
Tool | Description |
| SLO burn rate + error budget per service |
| Fetch runbook steps for an alert |
| Recent firing alerts by severity |
| Create incident record |
| Timeline of events for an incident |
| LLM-generated incident summary |
Use with Claude Desktop
{
"mcpServers": {
"sre-ops": {
"command": "python",
"args": ["-m", "src.mcp_server"],
"cwd": "/path/to/p12-sre-mcp"
}
}
}Then ask Claude: "What's burning right now?" — it calls query_alerts +
get_slo_status automatically and synthesizes a response.
SRE additions
Every tool call audit logged (timestamp, latency, success — postmortem-ready)
Tool latency tracked — SLO: p95 < 500ms
Graceful fallback when tools fail
JSON-RPC 2.0 protocol compliance
Both stdio (Claude Desktop) and HTTP (HF Space demo) transports
Run locally
git clone https://github.com/amarshiv86/p12-sre-mcp
cd p12-sre-mcp
pip install -r requirements.txt
# Run tests
pytest tests/ -v
# Start MCP server (stdio transport)
python -m src.mcp_server
# Test with manual JSON-RPC call
echo '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}' | python -m src.mcp_serverProject structure
p12-sre-mcp/
├── src/
│ ├── tools.py # 6 SRE tools + audit logging + timed_tool decorator
│ └── mcp_server.py # JSON-RPC 2.0 stdio transport
├── tests/
│ └── test_mcp.py # 20 tests (tools + MCP protocol)
├── hf_space/
│ ├── app.py # Gradio demo — scenario runner + manual tool call
│ ├── README.md # sdk_version: 5.29.0
│ └── requirements.txt
├── data/
│ ├── raw/tool_call_examples.jsonl
│ └── processed/sample_audit_log.json
├── .github/workflows/
│ ├── ci.yml
│ ├── deploy-hf-space.yml
│ └── deploy-hf-dataset.yml
└── requirements.txtStack
MCP Protocol · JSON-RPC 2.0 · Qwen2.5-0.5B · Gradio 5 · Audit logging · GitHub Actions
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Flicense-qualityDmaintenanceEnables interaction with Incident.io to manage incidents, severities, and health checks via natural language. Provides endpoints for getting and creating incidents.Last updated1
- Flicense-qualityDmaintenanceEnables AI-driven incident response by connecting Claude to monitoring tools like Prometheus, Grafana, Loki, PagerDuty, and Slack for automated investigation and runbook generation.Last updated9
- Alicense-qualityDmaintenanceEnables AI assistants to interact with Datadog's observability platform via natural language, covering metrics, logs, APM, monitors, dashboards, incidents, and infrastructure.Last updated9121MIT
- Flicense-qualityDmaintenanceProvides New Relic observability tools for AI assistants, enabling discovery, data access, alerting, incident response, and performance analytics via natural language queries.Last updated
Related MCP Connectors
AI agent run monitoring with incident replay and SLA receipts.
Runtime permission, approval, and audit layer for AI agent tool execution.
Let AI operate servers without SSH. Choose actions, approve risky changes, and audit every step.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/amarshiv86/p12-sre-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server