Incident Management
Freshstatus MCP connector
The Freshstatus connector brings your status page services, groups, incidents and incident updates into Claude, ChatGPT and Cursor, so your team can open, update and resolve incidents by asking in plain language.
-
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.
38 tools
How to connect
How to connect Freshstatus to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Freshstatus once
-
Open Connections, choose Add connection, and pick Freshstatus.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Freshstatus API key. One person generates a token in Freshstatus 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 Freshstatus 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 Freshstatus 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 Freshstatus 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 Freshstatus 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 Freshstatus through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Support
Post an incident before the tickets pile up
When the same complaint arrives three times in five minutes, open a Freshstatus incident against the affected service and set its status, so customers checking the status page see it before they write in.
-
Engineering
Keep the status page current mid-incident
From the incident channel, add a Freshstatus incident update in a few words and the public timeline reflects what the responders actually know right now.
-
Engineering
Close the loop when the fix lands
Resolve the Freshstatus incident and post the final update in one ask, so the page moves back to operational without anyone remembering to do it later.
-
IT
Keep the service catalog tidy
Add a new service after a launch, move it into the right group, rename one that changed, or retire one that was decommissioned, all without clicking through the Freshstatus admin screens.
-
Customer Success
Brief an account on last month's incidents
Ask for every Freshstatus incident that touched a customer's services in a date range and get a plain summary to paste into the quarterly review.
-
Communications
Draft updates customers can actually understand
Give the agent the technical note from the responders and have it write and post a customer-facing Freshstatus incident update in calm, clear language.
Try asking
- “List all services currently showing degraded status.”
- “Which incidents are still open across all groups?”
- “Summarize incident status changes from this week.”
AI tools
Freshstatus tools for your AI agents
38 tools are ready to call through Elaichi's MCP endpoint the moment you connect Freshstatus, 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 Freshstatus gets you
6 screens from the product, each doing one job for your Freshstatus account.
The agent
Ask about incidents and get live answers.
Query Freshstatus services and incidents in plain language, right from the agent screen.
- services
- groups
- incidents
- incident statuses
Ask Elaichi to work across your apps.
List all services currently showing degraded status.
Which incidents are still open across all groups?
Summarize incident status changes from this week.
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint, any client, no shared keys.
Connect Claude, ChatGPT or Cursor to Freshstatus through a single governed org endpoint.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
38 Freshstatus tools, ready with no code.
Every service, group and incident status method cataloged for immediate use.
- List all Freshstatus services
- Get single Freshstatus service by ID
- Create a Freshstatus service
- Update a Freshstatus service by ID
ElaichiToolsToolboxes
Each team gets its own toolbox.
Scope Freshstatus toolboxes per team so incident response tools match responsibility.
- SRE
- Support
- Engineering
- IT Ops
ElaichiToolboxesShared connections
Delegate Freshstatus access without sharing logins.
See who connected each account and how many teams and members share it.
- Platform Ops
- Customer Support
- Infrastructure
- Product Eng
ElaichiConnectionsAudit log
Every Freshstatus action, logged and traceable.
See who did what and when, across every service and incident change.
- 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 starts real incident work.
Freshstatus records are fetched, grouped, drafted into a digest, approved, then posted back.
Freshstatus digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch services
Freshstatus
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
Freshstatus
Queued
Collections and dashboards
Freshstatus health, computed and refreshed automatically.
Track four metrics and a 14 day trend of records created, broken down by team.
Freshstatus health
Refreshed 4 minutes ago · every 15 minutes · from the services collection
Services
1,284 ↓ 12%
Groups
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Services created
Last 14 days
By team
Share of activity
Platform Ops 34%
Customer Support 27%
Infrastructure 21%
Product Eng 18%
FAQ
Frequently asked questions
How do I connect Freshstatus to Claude?
Two steps. In Elaichi, choose Freshstatus and paste in a Freshstatus API key, then in Claude go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. There is no OAuth application to register and no client ID or secret to generate; the API key is the whole sign-in step for Freshstatus.
Does Freshstatus work with ChatGPT and Cursor as well as Claude?
Yes. Once Freshstatus 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 Freshstatus once and every client you use picks it up.
What can an AI agent actually do with my Freshstatus data?
It can list your Freshstatus services and groups, look up an incident, open a new incident, change its status, add an incident update, resolve it, and add or tidy up services and groups. In practice that means asking things like "open an incident on the API service, investigating" or "resolve incident 42 and post the all-clear". Short, concrete asks like those work better than long paragraphs, because Freshstatus has a lot of actions and the agent searches for the right one.
Does connecting Freshstatus give the AI access to everything on my status page?
No. Every call to Freshstatus runs inside the access of the Freshstatus API key the person connected with, so the agent can only reach the services, groups and incidents that key can reach. Elaichi can narrow that further with restrictions, but it can never widen it beyond what Freshstatus itself allows.
Can I stop an agent from deleting or changing things in Freshstatus?
Yes. Restrictions in Elaichi work per action, so you can allow reading Freshstatus incidents and posting updates while blocking deletion of services, groups or incidents. A blocked action is never advertised to Claude, ChatGPT or Cursor at all, so no prompt, however worded, can reach it.
What happens to a Freshstatus connection when someone leaves?
Offboarding that person in Elaichi ends their access to Freshstatus at once, across every client they used. If they had shared a Freshstatus connection with a team, it keeps working for everyone else. If you want it gone entirely, disconnecting Freshstatus once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client at the same time.
Put Freshstatus in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.