ops-agent-toolkit-mcp
Tools to check service registration/health status and read service configuration from Consul KV store.
Tools to fetch or search distributed traces, formatted as a span tree.
Tools to query a metric's summary (mean/peak/threshold) from Prometheus.
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., "@ops-agent-toolkit-mcpsearch logs for payment-service for errors in the last hour"
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.
ops-agent-toolkit-mcp
MCP server exposing read-only ops tools to an agent troubleshooting the lab-environment sandbox.
Tools
Tool | Backend | Purpose |
| Loki | Search service logs by keyword and time window |
| Prometheus | Get a metric's summary (mean/peak/threshold), not raw series |
| Jaeger | Fetch or search distributed traces, formatted as a span tree |
| Consul | Check service registration/health status |
| Consul KV | Read a service's current config |
| Consul KV | Enable/disable a fault scenario |
See ROADMAP.md for planned additions (Kafka tools, multi-agent permission scoping, K8s tools).
Related MCP server: MCP Observability Server
Run locally (stdio mode)
pip install -r requirements.txt
python server.pyRun as a container (HTTP/SSE mode)
docker build -t ops-lab/mcp-toolkit:dev .Intended to run inside the lab-environment docker-compose network, so it can reach Loki/Prometheus/Jaeger/Consul by service name.
Design principles
Read-only by default. The one exception is
toggle_chaos_scenario, scoped to chaos toggle keys only. No tool restarts services, rolls back deployments, or writes real app config. Further write-capable tools require explicit discussion.Parameterized, not raw passthrough. Never expose PromQL/LogQL directly to the model.
Every call is audited — tool name, args, duration, and a result preview are logged.
One tool, one job. Keep tool boundaries narrow so the agent composes them itself.
Roadmap
See ROADMAP.md.
This server cannot be deployed
Maintenance
Related MCP Connectors
Read-only MCP server for AIStatusDashboard status, incidents, metrics, and fallback recommendations.
Guarded MCP server for agent-readable business truth, provenance, readiness, and discovery.
Read-only MCP access to a documented IT fleet: state, changes, posture. 15 tools.
- IrisOAuthbio.irishealth
Read-only health context MCP server for Iris users.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceIn-cluster MCP server for read-only diagnostics of Grafana, Prometheus, Alertmanager, and Loki, enabling metric queries, alert listings, and log queries through Grafana datasource proxies with Kubernetes RBAC authentication.-
- FlicenseNot gradedqualityCmaintenanceMCP server for observability that provides tools for log search, metrics inspection, SQL querying, incident summaries, and service discovery.-
- AlicenseNot gradedqualityBmaintenanceA read-only MCP server that exposes tools to query Datadog monitors and logs, and AWS CloudWatch Logs, and to group recurring errors by fingerprint. Designed for use with Claude Code to diagnose issues and propose fixes.MIT
- AlicenseNot gradedqualityAmaintenanceAn MCP server exposing scoped, read-only enterprise operations tools with fail-closed credential handling. It returns opaque approval IDs for mutations and requires a separate operator approval command to release one-time capabilities.MIT