Incident Management
Chronosphere MCP connector
The Chronosphere connector lets Claude, ChatGPT, Cursor, or the Elaichi Agent list the teams in your Chronosphere organization and look up any single team by ID, with every request checked against the person who signed in and recorded in an audit log.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
2 tools
How to connect
How to connect Chronosphere to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Chronosphere once
-
Open Connections, choose Add connection, and pick Chronosphere.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Chronosphere API key. One person generates a token in Chronosphere and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect Chronosphere to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Connect Chronosphere to ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Connect Chronosphere to Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Chronosphere to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Chronosphere through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
SRE
Find the team behind a service mid-incident
Ask which Chronosphere teams exist and pull up the one that owns the affected monitors, without leaving the incident channel to click through the Chronosphere UI.
-
Platform engineering
Review the full Chronosphere team list
Get a plain list of every team in Chronosphere and spot duplicates, stale names, or teams that no longer match how the organization is structured.
-
Engineering management
Check a team's details before a reorg
Look up a Chronosphere team by its ID to confirm its name and description before moving people, dashboards, or alert ownership between groups.
-
On-call
Confirm who should get the page
When an alert lands with only a team ID attached, ask for that Chronosphere team and get its name and details back in seconds.
-
IT operations
Answer 'what teams do we have' quickly
Instead of exporting from Chronosphere by hand, ask for the current team list and drop it straight into a runbook, wiki page, or onboarding doc.
-
Compliance
Document team ownership for an audit
Pull the list of Chronosphere teams and the details of specific ones to show auditors how observability ownership is divided across the organization.
Try asking
- “List every Chronosphere team and its members.”
- “Which Chronosphere teams own more than one service?”
- “Show me the Chronosphere team behind last night's page.”
AI tools
Chronosphere tools for your AI agents
2 tools are ready to call through Elaichi's MCP endpoint the moment you connect Chronosphere, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Chronosphere gets you
6 screens from the product, each doing one job for your Chronosphere account.
The agent
Ask about Chronosphere teams in plain language.
The agent answers from live Chronosphere teams, no query language required.
- teams
- services
- monitors
- collections
Ask Elaichi to work across your apps.
List every Chronosphere team and its members.
Which Chronosphere teams own more than one service?
Show me the Chronosphere team behind last night's page.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor reach Chronosphere.
One governed MCP endpoint over OAuth, no SDK and no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
2 Chronosphere tools ready without custom code.
Browse tool names, resources and methods covering Chronosphere teams and lookups by id.
- List all Chronosphere teams
- Get single Chronosphere team by ID
ElaichiToolsToolboxes
Every team gets its own Chronosphere toolbox.
Curate toolboxes per team so on-call sees only the Chronosphere tools it needs.
- Site reliability
- Platform engineering
- Incident response
- Support
ElaichiToolboxesShared connections
Share a Chronosphere account, never a credential.
See who connected each Chronosphere account and how many teams and members use it.
- Production
- Staging
- Platform
- Site reliability
ElaichiConnectionsAudit log
Every Chronosphere call is written down.
When, who, what happened, type and resource for each Chronosphere request.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule drafts your Chronosphere team digest.
Fetch Chronosphere teams, group them, draft a digest, approve, then post it back.
Chronosphere digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch teams
Chronosphere
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Chronosphere
Queued
Collections and dashboards
Chronosphere health counted, not asked for.
Four metrics, 14 days of records created and a team breakdown, refreshed on schedule.
Chronosphere health
Refreshed 4 minutes ago · every 15 minutes · from the teams collection
Teams
1,284 ↓ 12%
Services
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Teams created
Last 14 days
By team
Share of activity
Production 34%
Staging 27%
Platform 21%
Site reliability 18%
FAQ
Frequently asked questions
How do I connect Chronosphere to Claude?
First, open Elaichi, choose Chronosphere, and paste in a Chronosphere API key when prompted; there is no OAuth application to register and no client ID or secret to generate. Then, in Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Sign in to Elaichi when Claude asks, and Chronosphere teams are available in your conversations.
Does Chronosphere work with ChatGPT and Cursor as well as Claude?
Yes. Once Chronosphere is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect Chronosphere once and every client picks it up.
What can an AI agent actually do with my Chronosphere data?
With this connector, an AI agent can list all of the teams in your Chronosphere organization and look up a single Chronosphere team by its ID to see its details. That is enough to answer questions like who owns a set of monitors, which teams exist, or what a team ID in an alert actually refers to. It cannot change teams, edit dashboards, or touch alerting rules through this connector.
Does connecting Chronosphere give the AI access to everything in my Chronosphere organization?
No. The connector can only read Chronosphere teams, and it can only reach what the Chronosphere API key used to connect is allowed to see. Each person still signs in to Elaichi as themselves, and Elaichi can narrow what a person or team can do with Chronosphere, but it can never widen access beyond what the key already has.
Can I stop an agent from deleting or changing things in Chronosphere?
This Chronosphere connector only lists teams and looks up a team by ID, so there is nothing it can delete or change to begin with. Beyond that, Elaichi restrictions work per action, and any action you block is never shown to Claude, ChatGPT, Cursor, or any other client, so no prompt can reach it.
What happens to a Chronosphere connection when someone leaves?
When you offboard a person in Elaichi, their access to Chronosphere through the endpoint ends at once. If they were using a shared Chronosphere connection, it keeps working for everyone else on the team. If you want to remove Chronosphere entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client at the same time.
Put Chronosphere in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.