Skip to content

Instatus MCP connector

The Instatus connector brings your status pages, components, incidents, scheduled maintenances and templates to Claude, ChatGPT, Cursor and Microsoft Copilot, so anyone can post an incident update or check what is down without leaving the chat.

  • Connects with an API key
  • Free 14-day trial
  • No credit card
Claude Elaichi connected

Which components are degraded right now?

Working in Instatus with Elaichi

  • List all Instatus pages
  • List all Instatus components
  • Get single Instatus component by ID
Ask anything…
Governance / Audit log Last 24 hours
Instatus Get single Instatus component by ID Emily Carter · Claude · 9:41 AM Done
Instatus List all Instatus components Emily Carter · Claude · 9:41 AM Done
Instatus List all Instatus pages Emily Carter · Claude · 9:41 AM Done
Instatus Create a Instatus page Megan Brooks · ChatGPT · 9:38 AM Done
Instatus Update a Instatus page by ID Ryan Hayes · Cursor · 9:35 AM Done

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

Step by step, for each AI app

Instatus MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 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 Claude Code

  1. 1

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

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

    Start Claude Code and run /mcp.

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

Instatus MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

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

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

Instatus MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 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.

Instatus MCP connector for Microsoft Copilot

  1. 1

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

  2. 2

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

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

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

  4. 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 Instatus to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 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.

What teams do with Instatus through Elaichi

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

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

See all 96 Instatus tools →

What connecting Instatus gets you

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

Elaichi Agent

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

The agent

Ask what is down and post the update.

Plain questions, answered from live Instatus incidents, components and maintenances.

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

One endpoint puts Instatus in every client.

Claude, ChatGPT, Cursor and Microsoft Copilot share one governed endpoint, no SDK and no shared API key.

ElaichiTools
Tool Action Description
List all Instatus pages List List the Instatus status pages in your workspace, one page per element. Returns status page objects including id, subdomain, name, status, language, brandColor, createdAt, and updatedAt. Pagination defaults to page 1 with 50 items per page, maximum 100.
Create a Instatus page Create Create a new status page in Instatus. Returns the created page including id, subdomain, name, status, language, color settings, and the initial components array. Requires email, name, and subdomain.
Delete a Instatus page by ID Delete Delete a status page in Instatus by its id. Returns an empty 204 response on success.
Update a Instatus page by ID Update Update an existing status page in Instatus by its id. Returns the updated page including id, subdomain, name, status, subscriberConfirmationMode, and translations. Required: id.
List all Instatus components List List all components on an Instatus status page. Returns each component's id, name, status, uniqueEmail, description, showUptime, order, group, and translations. Required: page_id. Max 100 items per page.

Tool catalog

96 Instatus tools, no code to write.

Pages, components, incidents, maintenances and templates, ready to use without a line of custom code.

ElaichiToolboxes
Name Source template Tools Created

Support toolbox

Instatus · incident updates and customer wording

Instatus starter 18 Mar 4, 2026

Engineering toolbox

Instatus · incidents and component status

— 9 Mar 2, 2026

IT toolbox

Instatus · scheduled maintenances

— 24 Feb 27, 2026

Customer success toolbox

Instatus · status checks before calls

Instatus starter 6 Feb 19, 2026

Communications toolbox

Instatus · templates and tone

— 31 Jan 30, 2026

Product toolbox

Instatus · pages and component lists

— 12 Jan 22, 2026

Toolboxes

Each team gets its own Instatus toolbox.

Support posts updates, engineering resolves incidents, IT schedules maintenance, each from its own scoped toolbox.

ElaichiConnections
Connection Scope Status Access
IN

Instatus (Support)

Connected by Emily Carter

Personal • Active 1 team · 6 members
IN

Instatus (Engineering)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
IN

Instatus (IT ops)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
IN

Instatus (Platform)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
IN

Instatus (Customer success)

Connected by Ryan Hayes

Personal • Active Not shared
IN

Instatus (Public status)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

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.

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]

Instatus Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

Instatus Pages Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

Instatus Pages List Toolbox

Audit log

Every status change names who made it.

Who opened the incident, who resolved it, and when, in one append-only log.

From answering questions to doing the work

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

Instatus digest

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

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch pages

    Instatus

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Jake Morgan

    Approve
  6. Post the digest

    Instatus

    Queued

Workflows

A schedule fires, the digest posts itself.

Instatus incidents fetched and grouped, a digest drafted, one approval, then posted back to the page.

Instatus health

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

Live

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%

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.

For IT and engineering

Elaichi vs Zapier MCP vs Composio for Instatus

All three can connect Instatus 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 Instatus, 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 Instatus tools Allow or restrict single Instatus 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 Instatus 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.

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.

Questions, answered

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, Microsoft Copilot, 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 my team share one Instatus connection?

Yes. One person connects Instatus in Elaichi and shares it with a team, and nobody else ever handles the API key. Each teammate still signs in to Elaichi as themselves, so the audit log records who opened or resolved each Instatus incident.

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 restricting deleting pages, components or incidents in Instatus. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.

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, Microsoft Copilot 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, 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 Instatus?

Yes. Both let Claude, ChatGPT or Cursor use Instatus. 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 Instatus call.

How is Elaichi different from Composio for Instatus?

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 Instatus: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Instatus in front of your team

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

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