Statuspage Integration
Live

Uptime & incident intelligence
on a live graph.

Native Statuspage connector with integration-statuspage graph module — pages, incidents, and components traverse live via API alongside PagerDuty, Datadog, and Slack for cited ops context.

Federation path

Statuspage joins
your full stack.

Statuspage
Gyri graph
CRM · comms · docs
What connects

Statuspage data
in your graph.

Data

Pages

Data

Incidents

Data

Components

Auto-provisions graph module: integration-statuspage — live API types install when you connect credentials.

The problem

Statuspage alone
is not enough.

01

Public status silos

Statuspage tracks customer-facing incidents — but engineering context lives in PagerDuty, Jenkins, and Slack elsewhere.

02

Manual incident briefs

Teams prep comms updates by copying Statuspage links instead of joining deploy and CRM context in one cited summary.

03

No agent-ready uptime context

Statuspage dashboards cannot multihop to deal blockers, on-call rotations, and cited exec briefs in one query.

With Gyri

Federated, cited,
agent-ready.

Live graph module

Incidents as graph entities

integration-statuspage installs statuspage_*_live remote types — agents query live Statuspage API data.

Cross-source joins

Incident → deploys → CRM

Multihop queries link Statuspage incidents to Vercel deploys, HubSpot renewals, and Slack war-room threads.

Ops stack

Uptime joins GTM tools

Federate Statuspage with PagerDuty, Datadog, ServiceNow, and institutional memory.

MCP agents

Agents read your status

Claude and Cursor access Statuspage through the same cited graph as product and revenue teams.

Gyri think verbs

26 MCP think verbs —
not API wrappers.

Statuspage federates into one graph. Agents orient with recall and ground, capture with reflect, and commit with promote — the full epistemic lifecycle via MCP think.

think verb=recall

Semantic orient — load prior cited conclusions before you re-derive from scratch.

think verb=ground

FTS-only orient on live federated CRM, email, and Slack — zero embed cost.

think verb=consider

Classify novelty against the workspace corpus before you commit a thesis.

think verb=reflect

Capture drafts, tensions, and questions as typed thoughts on the graph.

think verb=traverse

Multihop GraphQL in one think call — deal → contact → email → ticket.

think verb=fetch

Hydrate full rows by ref when search or traverse surfaced the right node.

think verb=promote

Gated commit — draft thought → durable cited insight the whole team recalls.

think verb=wish

Natural-language buildout — queue workspace types, connectors, and workflows.

Full catalog via MCP think verb=catalog · Why Gyri think verbs beat API wrappers → · MCP for Claude & Cursor

Use cases

Built for
GTM operators.

Customer impact brief

Join active Statuspage incidents with HubSpot renewal stage and support ticket volume — cited comms summary.

Deploy correlation

Correlate Statuspage component outages with Jenkins builds and Datadog alert timestamps.

Post-incident review

Link Statuspage incidents to PagerDuty pages and Notion postmortems in one federated query.

Works with

Federate alongside
native connectors.

Setup

Connect in
minutes.

Statuspage API key and optional page ID in Settings → Integrations.

1. Start a free trial at app.gyri.io · 2. Open Settings → Integrations · 3. Run your first federated query with cited answers.

Connect Statuspage Setup guide

Connect Statuspage to Gyri.

Free trial — API credentials, auto graph module, cited federated answers.