Opsphere

Bring operational intelligence into Claude Code through MCP

Check deployments, investigate errors and inspect infrastructure from Claude Code. Opsphere brings live operational evidence and guided investigations into your session through MCP.

From a quick endpoint check to a cross-system investigation.

MORE THAN AN MCP TOOL CATALOG

More than an MCP tool catalog

Explaining an operational failure often means checking deployments, logs and infrastructure together. Individual queries are useful; connecting their findings takes context.

Opsphere gives Claude Code direct operational tools and guided workflows for investigations across systems. Sign in through your browser. Provider credentials stay on the Opsphere gateway; your client manages its own sign-in session.

Ops tools don't speak Claude Code: your observability, deployment and paging stack was never built to return structured operational context to a Claude Code session over MCP. Opsphere sits between them and Claude Code.

  • Simple checks should stay simple

    For a direct question — one Kubernetes resource, one endpoint, one deployment list — an atomic tool is the right tool. Opsphere keeps those available.

  • Multi-system troubleshooting needs structure

    When a question spans deployments, errors, cluster state and edge checks, a flat list of tool calls forces Claude Code to reconstruct the whole investigation itself.

  • The intelligence layer belongs to Opsphere

    Claude Code is the interface where engineers ask and act. The operational capabilities, scoping and guardrails live in Opsphere.

TWO WAYS IN

Atomic tools and high-level investigations

Opsphere does not force every question into a long workflow. Simple checks stay simple; complex investigations use higher-level context and structure.

  • Atomic tools

    For direct operational questions: inspect a Kubernetes resource, check an HTTP endpoint, list deployments, query AWS inventory, search errors, inspect DNS and TLS state.

  • High-level investigations

    For cross-system questions: investigate an outage, diagnose environment degradation, correlate deployment and error signals, and return structured evidence and verification.

ATOMIC TOOLS

Query individual systems directly

Claude Code can call individual Opsphere tools to query specific systems: Kubernetes resources, AWS infrastructure, Datadog errors, deployments, DNS / HTTP / TLS, repositories, CDN and edge state. A direct query when a precise answer is all you need.

EVIDENCE-BACKED INVESTIGATIONS

Run structured operational investigations

High-level Opsphere workflows can return a structured investigation to Claude Code instead of an opaque answer. Depending on the workflow, the result can include hypotheses, evidence, confidence, timeline, verification, observed facts, inferences and recommended next steps.

  1. Hypotheses
  2. Evidence
  3. Confidence
  4. Timeline
  5. Verification

Claude Code can reason over structured operational evidence instead of reconstructing the entire investigation from raw tool calls.

OPERATIONAL CONTEXT

Give high-level workflows reusable operational context

Opsphere keeps Operational Context separate from the model and the client. That context can include relevant relationships between services, environments, repositories and previous investigations.

High-level Opsphere workflows can use shared operational context, while atomic tools remain focused on individual systems.

SOURCE SYSTEMS AUTHORITATIVE

Operational context without copying your entire stack into the session

Opsphere does not load all of your telemetry or infrastructure into the Claude Code session. The source systems keep the operational data; Opsphere queries what is needed and returns structured findings and context.

Operational intelligence in Opsphere. Model interaction in Claude Code. Source data in the systems that own it.

READ-ONLY BY DEFAULT

Investigate without changing production

Opsphere is read-only by default. Use Claude Code to inspect production, correlate evidence and review recommended next steps. These investigation workflows do not change production.

EXAMPLE

An operational question from Claude Code

Ask Claude Code: “Why did checkout-api start failing after the last production deployment?” Opsphere queries the relevant configured systems and returns evidence, possible explanations and next checks. Coverage depends on your integrations and plan.

  1. Probable cause
  2. Supporting evidence
  3. Alternative hypotheses
  4. Timeline
  5. Verification
  6. Recommended next checks

ONE LAYER, MANY INTERFACES

One operational layer across AI workflows

Claude Code is one of several interfaces that connect to Opsphere. Whether your team works in Claude Code, Cursor, Codex, or the Web Client, they consume the same operational layer through supported surfaces, keeping capabilities, context and guardrails consistent.

Different AI interface. Same Opsphere operational layer.

SUBAGENTS & GUIDED SKILLS

Ready-made operational flows for Claude Code

  • Incident investigation

    @opsphere:outage-triage

    Multi-service outages and incidents → probable cause with evidence

  • Endpoint health

    @opsphere:endpoint-health

    One hostname: DNS, HTTP, and certificate in one report

  • CI investigation

    @opsphere:ci-investigator

    Failed pipelines and GitHub Actions (Professional+)

  • Post-mortem writer

    @opsphere:postmortem-writer

    Structured RCA; optional save to Investigation Memory

Subagents run with the @opsphere: prefix for focused investigations. Interactive skills use the /opsphere: prefix (such as /opsphere:opsphere-onboarding). Community covers triage, endpoints, and post-mortems; deep CI diagnostics require Professional, Team, or Enterprise plans.

DIRECT ANSWERS

Key facts about Bring operational intelligence into Claude Code through MCP

A concise, verifiable summary based on the capabilities and operating boundaries described on this page.

What does Bring operational intelligence into Claude Code through MCP do?
Check deployments, investigate errors and inspect infrastructure from Claude Code. Opsphere brings live operational evidence and guided investigations into your session through MCP.
How does Bring operational intelligence into Claude Code through MCP work in practice?
Opsphere does not force every question into a long workflow. Simple checks stay simple; complex investigations use higher-level context and structure.
Does Opsphere change production systems?
Opsphere is read-only by default. It queries connected source systems, correlates evidence and recommends next steps; source systems remain authoritative.

GET STARTED

Connect Claude Code to your operational stack

Install the Opsphere plugin for Claude Code from the public GitHub repository, then complete browser sign-in. Start with “Check DNS for example.com” and explore guided investigations from your session.