# 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. Source: https://elaichi.ai/connectors/chronosphere/ ## Facts | | | | --- | --- | | Application | Chronosphere | | Category | Incident Management | | AI tools | 2 | | Authentication | Connects with an API key | | Needs your own OAuth app | No | | MCP endpoint | https://api.elaichi.ai/mcp | | Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent | | Tools advertised by name | Yes | ## What you can ask once Chronosphere is connected - 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. ## Connect Chronosphere in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick Chronosphere. 2. Optionally set Share with, then press Connect. 3. 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. Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Chronosphere tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## Connect Chronosphere to Claude Endpoint: https://api.elaichi.ai/mcp 1. Open Customize, then Connectors. 2. Press Add. 3. Name it, paste the MCP server URL, then Continue. 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 Endpoint: https://api.elaichi.ai/mcp 1. Open Plugins, then press the + button. 2. Name it and paste the endpoint into Server URL. 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 Endpoint: https://api.elaichi.ai/mcp 1. Open `~/.cursor/mcp.json`. 2. Add the endpoint under `mcpServers`. 3. Reload Cursor, then sign in and approve. Set up per machine, so repeat it on each computer you work from. ## Connect Chronosphere to any MCP client Endpoint: https://api.elaichi.ai/mcp 1. Add the endpoint as a remote MCP server. 2. Sign in and approve. The Elaichi Agent already has these tools, with nothing to set up. ## What the consent screen decides Only Read is granted by default, which is not enough to call a Chronosphere tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone. ## What teams do with Chronosphere through Elaichi ### Find the team behind a service mid-incident SRE. 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. ### Review the full Chronosphere team list Platform engineering. 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. ### Check a team's details before a reorg Engineering management. Look up a Chronosphere team by its ID to confirm its name and description before moving people, dashboards, or alert ownership between groups. ### Confirm who should get the page On-call. When an alert lands with only a team ID attached, ask for that Chronosphere team and get its name and details back in seconds. ### Answer 'what teams do we have' quickly IT operations. 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. ### Document team ownership for an audit Compliance. Pull the list of Chronosphere teams and the details of specific ones to show auditors how observability ownership is divided across the organization. ## 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 my team share one Chronosphere connection? Yes. One person connects Chronosphere in Elaichi with an API key and shares the connection with a team, and nobody else ever has to see or handle that key. Each teammate still signs in to Elaichi as themselves, so every request to Chronosphere is logged under the name of the person who made it. ### 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. ## All 2 Chronosphere tools Every tool below is callable through https://api.elaichi.ai/mcp once Chronosphere is connected, subject to the toolbox it is in and the restrictions on the caller. - **List all Chronosphere teams** (List). List teams in Chronosphere. Returns each team's name, slug, description, user_emails, created_at, and updated_at in the response. - **Get single Chronosphere team by ID** (Get). Get details about a specific team in Chronosphere using id. Returns name, slug, description, created_at, updated_at, and user_emails of the team.