Operational intelligence through MCP
Opsphere exposes operational capabilities across cloud, Kubernetes, observability, deployments, code, network and edge systems through MCP — from direct atomic queries to structured, high-level investigations with hypotheses, evidence, confidence, timeline and verification.
More than tools. Context, evidence and operational structure behind the same gateway.
MCP OPERATIONAL GATEWAY
Exposing tools is only the first layer
A generic MCP server can make individual APIs available to an AI client. That is useful, but complex operational questions still require the client to discover context, choose the right systems, correlate results and decide which findings matter.
Opsphere adds an operational intelligence layer behind those capabilities: atomic tools stay direct, while high-level workflows coordinate multiple checks and return a structured investigation.
Discovering context is left to the client
A raw tool list does not tell the client which systems are related, which environment is in scope, or what was already investigated.
Choosing the right systems is manual
For a cross-system question the client has to know which of dozens of tools to call, and in which order.
Correlating results falls on the client
Individual tool responses have to be reconciled into one operational picture before any conclusion can be drawn.
Deciding what matters has no structure
Without hypotheses, evidence and confidence, the client has to judge on its own which findings support or reject a cause.
TWO LEVELS OF ACCESS
Atomic queries and high-level investigations
The same gateway serves a direct question to one system and a structured investigation that crosses several — read-only, by default.
Atomic tools
Query an individual system directly — Kubernetes, AWS, Vercel, Datadog, Sentry, GitHub or Bitbucket, Cloudflare or Akamai, DNS / HTTP / TLS. Atomic tools stay atomic when a direct query is all that is needed.
High-level investigations
When a problem crosses systems, high-level capabilities coordinate multiple operational checks and return a structured result: hypotheses, evidence, confidence, timeline, verification, findings and recommendations.
Simple checks stay simple. Complex investigations get structure.
The gateway does not force every request through a full investigation. A direct query returns a direct answer; a cross-system question returns a structured investigation.
- Atomic query
- High-level workflow
- Structured result
CAPABILITIES
Context that does not live inside the AI client
Operational Context outside the client
Opsphere can maintain Operational Context independently from Cursor, Codex, Claude or another MCP client. High-level workflows can use relevant relationships and previous investigations without requiring the AI client itself to become the system of memory.
Shared context, focused tools
High-level workflows can use shared Operational Context; atomic tools remain focused on individual systems. Not every MCP call automatically loads Operational Context.
Machine-readable operational intelligence
Opsphere returns structured content that AI clients can reason over programmatically, instead of requiring every result to be reconstructed from prose.
One gateway, multiple AI workflows
The same Opsphere operational layer is reachable from different clients. Cursor and Codex have dedicated integration pages; Claude and Claude Code connect over MCP like any other compatible client, alongside other supported MCP-compatible clients.
Cursor
Atomic operational tools plus high-level, evidence-backed investigations inside the Cursor workflow.
Codex
The same gateway from OpenAI Codex — direct queries and structured investigations, read-only by default.
Claude / Claude Code and other MCP clients
Claude, Claude Code and other supported MCP-compatible clients connect to the same operational layer. Different client. Same Opsphere operational layer.
MCP access without silent production changes
Opsphere is read-only by default over MCP. It can inspect, correlate, diagnose and recommend without silently mutating production systems.
Read-only by default · Tenant isolated · Environment scoped · Evidence-backed · Source systems remain authoritative
How the gateway is layered
A request from an MCP client reaches the Opsphere MCP Gateway, which fronts the Operational Intelligence Layer — atomic tools, Operational Context, the investigation core and high-level workflows. The layer queries and correlates the systems that already own the data.
- Cursor / Codex / Claude / MCP client
- Opsphere MCP Gateway
- Operational Intelligence Layer
- AWS / Kubernetes / Datadog / Git / CDN / …
Opsphere is not just an MCP server. It exposes an Operational Intelligence Layer through MCP.
KEEP EXPLORING
Related platform capabilities
GET STARTED
Reach the operational intelligence layer through MCP
See how atomic tools, high-level investigations and reusable Operational Context are exposed through one read-only MCP gateway.