Turn Cursor into an operational intelligence interface
Opsphere connects Cursor to your existing infrastructure, observability, deployment, code and edge systems through MCP — combining live operational queries with structured, evidence-backed investigations and reusable operational context where high-level workflows apply.
From atomic tool calls to evidence-backed operational investigations — without leaving Cursor.
Connection Hub: link multiple client Opsphere workspaces to one Cursor login. Open a server-side work context, run scoped tools with context_id, and switch clients without re-authenticating.
MORE THAN MCP TOOLS
More than tools inside your IDE
Many MCP integrations stop at exposing individual actions or queries. That is useful, but it makes every server look the same: a list of atomic calls.
Opsphere adds a structured operational layer behind those tools. Cursor can run an atomic capability when a precise query is enough, or invoke a higher-level Opsphere workflow that combines multiple systems into a single evidence-backed investigation.
Ops tools don't speak MCP: your observability, deployment and paging stack was never built to stream structured operational context into an IDE agent. Opsphere sits between them and Cursor.
Atomic tools are the floor, not the ceiling
A generic MCP tool exposes one action at a time. Opsphere keeps those atomic tools available and adds high-level workflows that reason across systems.
Cursor is the interface, not the intelligence layer
The operational capabilities, scoping and guardrails live in Opsphere. Cursor stays the place where engineers ask and act on the answer.
Structured operational access over MCP
Opsphere exposes structured operational capabilities across your engineering stack through the Model Context Protocol — atomic queries and high-level investigations, read-only by default.
HOW OPSPHERE CONNECTS
Live in your editor in a couple of minutes
A single MCP client config entry connects Cursor to Opsphere — no agents, no sidecars, no infrastructure changes.
Install
Add the Opsphere MCP endpoint to your Cursor config. One JSON block, no binary to deploy.
Connect
Choose your connection mode: local dev environment, network-accessible cluster, or Opsphere-managed remote environment.
Query and investigate
Ask Cursor operational questions. Opsphere answers atomic queries directly and runs high-level, evidence-backed investigations when a question spans multiple systems — all from inside the editor.
EVIDENCE-BACKED INVESTIGATIONS
Investigate operational issues without reducing everything to a chat answer
High-level Opsphere investigation workflows return structured operational results through MCP — not only prose. A result can include hypotheses, supporting and contradicting evidence, calculated confidence, an investigation timeline, verification conditions, observed facts, inferences and recommended next steps, so both engineers and AI clients can inspect and reuse it.
- Cursor
- Opsphere Gateway
- Operational tools
- Investigation Core
- Structured result
Hypotheses → Evidence → Confidence → Timeline → Verification.
TWO INTERACTION MODES
Use the right level of abstraction for the task
Opsphere does not force every question into an agentic 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 Vercel deployments, query AWS inventory, search logs or errors, inspect DNS and TLS state.
High-level investigations
For cross-system operational questions: investigate an outage, diagnose environment degradation, correlate deployment and error signals, inspect endpoint health across DNS, HTTP and TLS, and produce structured evidence and verification.
OPERATIONAL CONTEXT
Give investigations context from the systems around them
Opsphere maintains a structured operational context layer that can preserve relevant relationships between services, environments, repositories, accounts and previous investigations, so high-level workflows do not start from an empty context every time. High-level Opsphere workflows can use shared operational context, while atomic tools remain focused on querying individual systems. The underlying systems stay authoritative — Opsphere does not become another telemetry datastore.
Your tools remain the source of truth. Opsphere provides the operational context around them.
STRUCTURED OUTPUT
Structured outputs that AI clients can reason about
Depending on the capability invoked, Cursor can receive machine-readable operational results — not only human-facing text.
Findings and evidence
Operational findings with the source and tool metadata behind them, plus individual evidence items that support or contradict a hypothesis.
Calculated confidence
How strongly the available evidence supports a conclusion, reported as HIGH, MEDIUM or LOW — derived from evidence, not model self-assessment.
Timelines
A compact sequence of relevant events when source systems provide reliable timestamps; no sequence is fabricated when they do not.
Verification and recommendations
Explicit verification conditions and recommended next steps, plus the scoped operational context used — returned as data an AI client can consume programmatically.
READ-ONLY BY DEFAULT
Investigate production without silently changing it
Opsphere is read-only by default. Cursor can use it to inspect, correlate and investigate operational systems without automatically mutating production infrastructure. Recommended actions and verification conditions come back as structured output, but execution stays governed by the engineer, team or external workflow.
Read-only by default · Tenant isolated · Account-aware · Environment scoped · Evidence-backed · Source systems remain authoritative
TECHNICAL BENEFITS
Built for how Cursor and MCP actually work
Opsphere's Cursor integration is engineered around the Model Context Protocol spec — not bolted on as an afterthought.
Native MCP Integration
Opsphere implements the Model Context Protocol natively. No wrappers, no proxies — direct, spec-compliant communication between Cursor and your infrastructure.
Three Connection Modes
Local dev environment, network-accessible cluster, or Opsphere-managed remote environment. Pick the mode that matches your security posture.
Read-Only, Secure By Design
Opsphere observes your infrastructure — it never writes. All data is encrypted in transit, and the MCP connection runs with the minimum permissions required.
Built For Interactive IDE Workflows
High-level investigations are inherently multi-step — they query several source systems before reaching a conclusion. The integration is designed for interactive use inside the editor rather than a fixed latency budget.
AI Agent Awareness
Opsphere exposes structured resource graphs that Cursor's AI agents can reason over — not just raw metrics, but correlated operational relationships across services.
Cursor Integration Specifications
- Built for
- Interactive IDE workflows
- MCP integration
- Native
- Connection modes
- Local · Network · Remote
- Install footprint
- 1 config block
- Default permissions
- Read-only
- Operational tools exposed
- 320+
- Primary IDE
- Cursor
- Transport options
- stdio · Remote
- Agent context format
- Structured graph
- Specialized subagents
- 4+ · Read-only · Slash commands
SUBAGENTS
Ready-made operational flows, not improvised prompts
Incident triage
/outage-triage
Multi-service outages and incidents → verdict + evidence
Endpoint health
/endpoint-health
One hostname: DNS, HTTP, and certificate in one report
CI investigator
/ci-investigator
Failed pipelines and GitHub Actions (Professional+)
Post-mortem writer
/postmortem-writer
Structured RCA; optional save to memory
Community: triage, endpoints, and post-mortems. Deep CI diagnostics on Professional, Team, and Enterprise plans.
EXAMPLE
Example: investigate a production regression from Cursor
A generic, read-only investigation
An engineer asks, in Cursor: "Why did checkout start failing after the latest deployment?" Here is how Opsphere works through it — without changing anything in production.
Cursor asks Opsphere to look
Cursor uses Opsphere to inspect the relevant operational systems for the checkout-api service and its environment.
A high-level investigation correlates the evidence
Recent deployment changes, application errors, Kubernetes health, service and environment relationships, network and edge status, and previous relevant investigations are evaluated against the same question.
Probable cause — HIGH confidence
A deployment-related configuration change correlates with the start of the errors. Evidence: the deployment changed just before the error spike; application errors increased immediately afterward; Kubernetes capacity stayed healthy; network and CDN checks stayed normal.
Verification conditions, not an auto-fix
Error rate returns to baseline; the checkout endpoint is healthy; relevant synthetics recover. The engineer decides what to change and applies it — Opsphere does not modify production.
KEEP EXPLORING
Related platform capabilities
GET STARTED
Bring operational intelligence into Cursor
Connect Opsphere over MCP and bring operational context and evidence-backed investigations into the editor where engineers already work.