Glama lists the Opsphere connector for operational investigations
Glama lists Opsphere — DevOps & SRE Intelligence under io.opsphere.mcp-cursor. A Glama session can reach the remote Opsphere gateway over Streamable HTTP and OAuth2 to investigate bugs, assess release readiness, search logs, triage outages, diagnose failed CI, check deployments, and query connected cloud platforms. Glama marks ownership as verified and reports that OAuth works in Glama.
The listing includes read-only QA subagents. Opsphere is read-only by default. Connected systems remain the source of the evidence. Opsphere does not copy that telemetry into another store.
What changes
Opsphere is available from Glama as a connector to the same remote gateway. Glama is a client path. It does not replace the systems that hold logs, deployments, or cloud state.
How it works
The connector uses Streamable HTTP, and the listing reports MCP dated 2025-11-25. The user authenticates with OAuth2. Opsphere then queries the systems that the tenant has connected. Those systems supply the evidence.
Why it matters
A team working in Glama can use the connector for release readiness, failed CI, outages, and connected cloud platforms on the remote gateway. Systems that are already connected remain the source of that evidence.
Limits and requirements
Opsphere is read-only by default. Source systems remain authoritative for the underlying operational data. A user-initiated action is separate from that default.
- Requires OAuth. The Glama listing reports that OAuth works in Glama.
- QA subagents on the listing are read-only.
- Glama does not become the source of logs, deployments, or cloud state.