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.

Incident Management

Chronosphere MCP connector

The Chronosphere connector lets Claude, ChatGPT, Cursor, Microsoft Copilot, 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.

Connect on Elaichi How to connect

Connects with an API key
Free 14-day trial
No credit card

ChatGPT Elaichi connected

List every Chronosphere team and its members.

Working in Chronosphere with Elaichi

List all Chronosphere teams
Get single Chronosphere team by ID

Ask anything…

Governance / Audit log Last 24 hours

Get single Chronosphere team by ID Emily Carter ·

9:41 AM Done

List all Chronosphere teams Emily Carter ·

9:41 AM Done

List all Chronosphere teams Megan Brooks ·

9:38 AM Done

List all Chronosphere teams Ryan Hayes ·

9:35 AM Done

How to connect Chronosphere to Claude, ChatGPT, Cursor or Microsoft Copilot

Step by step, for each AI app

Chronosphere MCP connector for 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.

Chronosphere MCP connector for Claude Code

1

In a terminal, run claude mcp add with the endpoint.

https://api.elaichi.ai/mcp
2

Start Claude Code and run /mcp.
3

Pick elaichi, then sign in and approve in the browser.

Terminal

$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp

Use --scope project instead to share it with the repository through .mcp.json.

Chronosphere MCP connector for 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. The plugin directory lives at chatgpt.com/plugins.

Chronosphere MCP connector for 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.

Chronosphere MCP connector for Microsoft Copilot

1

In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2

Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.

https://api.elaichi.ai/mcp
3

Create a new connection, sign in and approve, then press Add to agent.
4

Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Server URL: https://api.elaichi.ai/mcp
Authentication: OAuth 2.0
Type: Dynamic discovery

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

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.

Connect Chronosphere on Elaichi See pricing

What teams do with Chronosphere through Elaichi

Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Chronosphere is logged.

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.”

See all 2 Chronosphere tools →

What connecting Chronosphere gets you

6 screens from Elaichi, each doing one job for your Chronosphere account.

Elaichi Agent

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, Cursor or Microsoft Copilot

The agent

Ask about Chronosphere teams in plain language.

The agent answers from live Chronosphere teams, no query language required.

ElaichiAI apps

Claude

ChatGPT

Cursor

Microsoft Copilot

Copy the endpoint

https://api.elaichi.ai/mcp

Client	Connected by	Status	Last used
Claude	E Emily Carter	• Connected	4 minutes ago
Cursor	M Megan Brooks	• Connected	2 hours ago
ChatGPT	R Ryan Hayes	• Connected	Yesterday

AI apps

Claude, ChatGPT, Cursor and Microsoft Copilot reach Chronosphere.

One governed MCP endpoint over OAuth, no SDK and no shared API key.

ElaichiTools

Tool	Action	Description
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.

Tool catalog

2 Chronosphere tools ready without custom code.

Browse tool names, resources and methods covering Chronosphere teams and lookups by id.

ElaichiToolboxes

Name	Source template	Tools	Created
Site reliability toolbox Chronosphere · teams and on-call ownership	Chronosphere starter	18	Mar 4, 2026
Platform engineering toolbox Chronosphere · services and monitors	—	9	Mar 2, 2026
Incident response toolbox Chronosphere · active incidents and escalations	—	24	Feb 27, 2026
Support toolbox Chronosphere · customer impact and status updates	Chronosphere starter	6	Feb 19, 2026
Security operations toolbox Chronosphere · alerting policies and coverage	—	31	Jan 30, 2026
Engineering leadership toolbox Chronosphere · team rosters and reporting	—	12	Jan 22, 2026

Toolboxes

Every team gets its own Chronosphere toolbox.

Curate toolboxes per team so on-call sees only the Chronosphere tools it needs.

ElaichiConnections

Connection	Scope	Status	Access
CH Chronosphere (Production) Connected by Emily Carter	Personal	• Active	1 team · 6 members
CH Chronosphere (Staging) Connected by Jake Morgan	Organization	• Active	3 teams · 24 members
CH Chronosphere (Platform) Connected by Megan Brooks	Organization	• Active	2 teams · 11 members
CH Chronosphere (Site reliability) Connected by Tyler Reed	Personal	• Needs re-auth	1 team · 3 members
CH Chronosphere (Security operations) Connected by Ryan Hayes	Personal	• Active	Not shared
CH Chronosphere (Support EMEA) Connected by Ashley Parker	Personal	• Active	2 teams · 9 members

Shared connections

Share a Chronosphere account, never a credential.

See who connected each Chronosphere account and how many teams and members use it.

ElaichiAudit log

When	Who	What happened	Type
2 minutes ago Mar 6, 2026, 3:10 PM	E Emily Carter [email protected]	Restriction Created	Access
8 minutes ago Mar 6, 2026, 3:04 PM	J Jake Morgan [email protected]	Restriction Updated	Access
14 minutes ago Mar 6, 2026, 2:58 PM	M Megan Brooks [email protected]	Role Assigned	Access
20 minutes ago Mar 6, 2026, 2:52 PM	T Tyler Reed [email protected]	Chronosphere Users Updated	MCP
26 minutes ago Mar 6, 2026, 2:46 PM	R Ryan Hayes [email protected]	Chronosphere Teams Created	MCP
32 minutes ago Mar 6, 2026, 2:40 PM	A Ashley Parker [email protected]	Chronosphere Teams List	Toolbox

Audit log

Every Chronosphere call is written down.

When, who, what happened, type and resource for each Chronosphere request.

From answering questions to doing the work

A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.

Chronosphere digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

Run now

✓

Schedule

Every weekday at 8:00 AM

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 Jake Morgan

Approve Deny
Post the digest

Chronosphere

Queued

Automations

A schedule drafts your Chronosphere team digest.

Fetch Chronosphere teams, group them, draft a digest, approve, then post it back.

Chronosphere health

Refreshed 4 minutes ago · every 15 minutes · from the teams collection

Live

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%

Collections and dashboards

Chronosphere health counted, not asked for.

Four metrics, 14 days of records created and a team breakdown, refreshed on schedule.

For IT and engineering

Elaichi vs Zapier MCP vs Composio for Chronosphere

All three can connect Chronosphere to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for Chronosphere, by what to check
What to check	Elaichi	Zapier MCP	Composio
Where the AI connects	One address for the whole organization. `https://api.elaichi.ai/mcp`	A server per member, created at sign-in.	An MCP endpoint per team, or an SDK.
Control over Chronosphere tools	Allow or restrict single Chronosphere tools, per role or user.	App and action restrictions on the account.	Role permissions, down to the action.
Record of calls	One audit entry per Chronosphere call.	A History tab of tool calls.	A log of every tool call.
Single sign-on	SAML or OIDC, plus SCIM, on Gold.	SAML on Enterprise.	SAML and OIDC on Enterprise.
Price	Free for one person; $15 per user per month on Gold.	2 tasks per successful call.	Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

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.

More from the catalog

Browse all 650+ connectors →

Questions, answered

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, Microsoft Copilot, 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 restrict still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor, Microsoft Copilot, or any other client cannot run it, whatever the prompt says.

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, Microsoft Copilot, and every other client at the same time.

Does the Chronosphere MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Chronosphere is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Is Elaichi an alternative to Zapier MCP for Chronosphere?

Yes. Both let Claude, ChatGPT or Cursor use Chronosphere. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Chronosphere call.

How is Elaichi different from Composio for Chronosphere?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Chronosphere: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Chronosphere in front of your team

14 days of Black, no credit card. Connect it once and pick what each team can call.

Connect Chronosphere Talk to us

When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.

Add one link to your AI app

The same link for everyone on your team.

https://api.elaichi.ai/mcp

ChatGPT
Claude
Cursor
Microsoft Copilot