Instatus MCP connector
The Instatus connector brings your status pages, components, incidents, scheduled maintenances and templates to Claude, ChatGPT and Cursor, so anyone can post an incident update or check what is down without leaving the chat.
-
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.
How to connect
How to connect Instatus to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Instatus once
-
Open Connections, choose Add connection, and pick Instatus.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste an Instatus API key. One person generates a token in Instatus 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.
Instatus 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.
Instatus 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 today. The plugin directory lives at chatgpt.com/plugins.
Instatus 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.
Connect Instatus 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 Instatus through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Support
Open an incident while the queue fills
When tickets about the same outage start arriving, open an Instatus incident from a template and mark the affected components, so customers see the status page before they write in.
-
Engineering
Post the next update from the war room
Ask for the current incident and add the latest update in plain words while the fix is still in progress. Resolve it and set the components back to operational once it is over.
-
IT
Schedule Saturday's maintenance window
Create a scheduled maintenance on the right Instatus page with the start time, the duration and the components it touches, then adjust it if the window moves.
-
Customer success
Check what is down before a call
Ask which components are degraded right now and what the last incident update said, so you walk into a customer call already knowing.
-
Communications
Keep incident wording consistent
Review the Instatus templates your team posts from, tighten the wording once and update them, so every future incident reads the same way.
-
Product
Keep the component list current
When a new service ships or an old one is retired, add, rename or remove components on each Instatus page so the status page matches what customers actually use.
Try asking
- “Which components are degraded right now?”
- “Open an incident from the API outage template.”
- “Schedule maintenance on the checkout components for Saturday at 2am.”
AI tools
Instatus tools for your AI agents
96 tools are ready to call through Elaichi's MCP endpoint the moment you connect Instatus, 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 Instatus gets you
6 screens from the product, each doing one job for your Instatus account.
The agent
Ask what is down and post the update.
Plain questions, answered from live Instatus incidents, components and maintenances.
- pages
- components
- incidents
- maintenances
Ask Elaichi to work across your apps.
Which components are degraded right now?
Open an incident from the API outage template.
Schedule maintenance on the checkout components for Saturday at 2am.
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint puts Instatus in every client.
Claude, ChatGPT and Cursor share one governed endpoint, no SDK and no shared API key.
Copy the endpoint
Tool catalog
96 Instatus tools, no code to write.
Pages, components, incidents, maintenances and templates, ready to use without a line of custom code.
- List all Instatus pages
- Create a Instatus page
- Delete a Instatus page by ID
- Update a Instatus page by ID
Toolboxes
Each team gets its own Instatus toolbox.
Support posts updates, engineering resolves incidents, IT schedules maintenance, each from its own scoped toolbox.
- Support
- Engineering
- IT
- Customer success
Shared connections
Teammates post updates without touching the key.
One person connects Instatus, the team works through it, and nobody else sees the API key.
- Support
- Engineering
- IT ops
- Platform
Audit log
Every status change names who made it.
Who opened the incident, who resolved it, and when, in one append-only log.
- When
- Who
- What happened
- Type
Launching 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 fires, the digest posts itself.
Instatus incidents fetched and grouped, a digest drafted, one approval, then posted back to the page.
Instatus digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch pages
Instatus
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
Instatus
Queued
Collections and dashboards
Incident numbers arrive before anyone asks.
Four metrics, 14 days of incidents and a team breakdown, refreshed on schedule without a model.
Instatus health
Refreshed 4 minutes ago · every 15 minutes · from the pages collection
Pages
1,284 ↓ 12%
Components
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Pages created
Last 14 days
By team
Share of activity
Support 34%
Engineering 27%
IT ops 21%
Platform 18%
FAQ
Frequently asked questions
How do I connect Instatus to Claude?
Connect Instatus in Elaichi first, which asks for an Instatus API key from your Instatus account settings, and there is no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in with your Elaichi account and Instatus is ready in the chat.
Does Instatus work with ChatGPT and Cursor as well as Claude?
Yes. Once Instatus 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 Instatus once and every client picks it up.
What can an AI agent actually do with my Instatus status pages?
An agent can read your Instatus status pages, tell you which components are degraded, open an incident from a template, post the next update and resolve it when the fix lands. It can also schedule and adjust maintenance windows and keep components and templates current. Short, concrete asks such as post an update to the checkout incident work better than long paragraphs.
Does connecting Instatus give the AI access to every status page?
No. Everything the AI does in Instatus runs under the Instatus account whose key was used to connect, so it can only reach the pages and components that account can reach. Elaichi can narrow that further, for example to reading only or to specific pages, but it can never widen it beyond what the account already has.
Can I stop an agent from deleting or changing things in Instatus?
Yes. Restrictions in Elaichi apply per action, so you can allow reading status and posting updates while blocking deleting pages, components or incidents in Instatus. A restricted action is never advertised to Claude, ChatGPT or Cursor at all, so no prompt, however worded, can reach it.
What happens to an Instatus connection when someone leaves?
Offboarding someone in Elaichi ends their access to Instatus through every client at once, with no key to rotate. A shared Instatus connection keeps working for everyone else on the team. If you later want it gone, disconnecting Instatus once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client.
Does the Instatus MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Instatus 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, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Put Instatus in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.