Ops MCP Server Skill

Access your infrastructure's observability data and execute operational procedures through a unified MCP interface.

Capabilities at a Glance

Setup (first-time)

CODEBLOCK0

How to Investigate: Decision Guide

When a user describes a problem, use this guide to choose starting tools and build a complete picture.

🔴 "Something is broken / service is down"

1. 1. Kubernetes Events first — check if pods crashed, restarted, or got evicted

   get-events-from-ops  subject_pattern="ops.clusters.*.namespaces.<ns>.pods.*.events"
   

1. 2. Logs — search for errors around the time of the incident

   query-logs-from-elasticsearch  query="FROM logs-* | WHERE @timestamp > NOW() - 30 minutes | WHERE level == 'error' | LIMIT 50"
   

1. 3. Traces — find failed or slow requests

🟡 "Performance is degraded / requests are slow"

1. 1. Metrics — check resource saturation

   query-metrics-from-prometheus  query="100 - (avg(rate(node_cpu_seconds_total{mode='idle'}[5m])) * 100)"
   query-metrics-range-from-prometheus  query="node_memory_MemAvailable_bytes"  time_range="1h"  step="1m"
   

1. 2. Traces — find slow spans

   find-traces-from-jaeger  serviceName=<service>  durationMin=1000
   

1. 3. Logs — look for timeouts or slow query warnings

🔵 "I need to run a procedure / restart something"

1. 1. List available SOPs

   list-sops-from-ops
   

1. 2. Get parameters

   list-sops-parameters-from-ops  sops_id=<id>
   

1. 3. Execute

🟢 "General health check / nothing specific"

Start with events + a key metrics query, then go deeper based on what you find.

Tool Quick Reference

Events — NATS subject pattern format

CODEBLOCK9

Wildcards: * = one segment, > = everything remaining (tail only)

Observation types: status | events | alerts | INLINECODE20

Time is Unix milliseconds: INLINECODE21

Logs — ES|QL query patterns

CODEBLOCK10

Metrics — PromQL patterns

CODEBLOCK11

Detailed Examples & Reference Files

For complete parameter lists, output formats, and advanced patterns, read the relevant file:

• - events → INLINECODE22
• metrics → INLINECODE23
• logs → INLINECODE24
• traces → INLINECODE25
• sops → INLINECODE26
• event subject format design → INLINECODE27

Read the relevant example file before making complex tool calls you're unsure about.

What This Skill is NOT For

• - Direct infrastructure changes (use dedicated automation tooling)
• Real-time alerting (investigation only, not a monitoring agent)
• Writing to or modifying operational data (all access is read-only)