Bring operational intelligence into the Antigravity CLI through MCP
Opsphere connects the local Antigravity CLI to the systems you already run — infrastructure, observability, deployments, code and edge — through MCP, so an Antigravity session can ask a direct operational question or open a structured, evidence-backed investigation.
From atomic operational tools to structured investigations and reusable context.
MORE THAN AN MCP TOOL CATALOG
More than an MCP tool catalog
A flat list of tool calls is useful, but it is where most MCP agent integrations stop. The Antigravity CLI then has to reconstruct every cross-system investigation from scratch.
Opsphere adds a structured operational intelligence layer behind those tools. In a local Antigravity CLI session, engineers can run an atomic check when a precise query is enough, or delegate to specialized agents that correlate signals across systems into one evidence-backed investigation — with browser-based sign-in, stable CIMD identity, zero vendor secrets stored locally, and session tokens managed securely by the Antigravity runtime.
Ops tools don't speak Antigravity CLI: your observability, deployment and paging stack was never built to return structured operational context to an Antigravity CLI session over MCP. Opsphere sits between them and the Antigravity CLI.
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 the Antigravity CLI to reconstruct the whole investigation itself.
The intelligence layer belongs to Opsphere
The Antigravity CLI 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
The Antigravity CLI can call individual Opsphere tools to query specific systems: Kubernetes resources, AWS infrastructure, observability 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 the Antigravity CLI 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.
- Hypotheses
- Evidence
- Confidence
- Timeline
- Verification
The Antigravity CLI 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 Antigravity CLI 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 the Antigravity CLI. Source data in the systems that own it.
READ-ONLY BY DEFAULT
Investigate without changing production
The Antigravity CLI can use Opsphere to inspect and investigate operational systems while Opsphere stays read-only by default. Recommendations can be structured. Opsphere does not apply those changes in production.
EXAMPLE
Example: investigate a deployment regression from the Antigravity CLI
An engineer asks, in the local Antigravity CLI: "Why did checkout-api start failing after the last production deployment?" Opsphere works through deployment evidence, observability evidence, Kubernetes state, network and edge checks, and relevant operational context.
- Probable cause
- Supporting evidence
- Alternative hypotheses
- Timeline
- Verification
- Recommended next checks
ONE LAYER, MANY INTERFACES
One operational layer across AI workflows
The Antigravity CLI is one of several interfaces that connect to Opsphere. Whether your team works in Antigravity, GitHub Copilot CLI, Cursor, Codex, Claude Code, 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 the Antigravity CLI
Incident investigation
outage-triage
Multi-service outages and incidents → probable cause with evidence
Endpoint health
endpoint-health
One hostname: DNS, HTTP, and certificate in one report
CI investigation
ci-investigator
Failed pipelines and GitHub Actions (Professional+)
Post-mortem writer
postmortem-writer
Structured RCA; optional save to Investigation Memory
Antigravity agents are invoked by name for focused investigations (such as "Use outage-triage"). Onboarding is guided by opsphere-onboarding. This package supports the local Antigravity CLI (agy), installed as the opsphere plugin from package opsphere-antigravity. Community covers triage, endpoints, and post-mortems; deep CI diagnostics require Professional, Team, or Enterprise plans.
KEEP EXPLORING
Related platform capabilities
GET STARTED
Connect the Antigravity CLI to your operational stack
Install the Opsphere plugin for the Antigravity CLI (agy), complete browser sign-in once, and bring operational context and evidence-backed investigations into a local CLI session. The plugin is opsphere, package opsphere-antigravity, from the public marketplace opsphere-io/opsphere-plugin.