Can my team share one Freshstatus connection?

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

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.

Connect on Elaichi How to connect

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.

freshstatus

All categories

Freshstatus

Better Stack

Chronosphere

FireHydrant

Freshservice

incident.io

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.

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

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

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

Connect Freshstatus on Elaichi See pricing

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

See all 38 Freshstatus tools below

Compare

Elaichi vs Zapier MCP vs Composio for Freshstatus

All three can connect Freshstatus 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 Freshstatus, 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 Freshstatus tools	Allow or restrict single Freshstatus 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 Freshstatus 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	$15 per user per month.	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.

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.

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 clients

Claude

ChatGPT

Cursor

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

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

ElaichiTools

Tool	Action	Description
List all Freshstatus services	List	List all Freshstatus service components — the building blocks displayed on your status page. Returns: id, name, description, order, status, display_options, group.
Get single Freshstatus service by ID	Get	Get a specific Freshstatus service component by id. Returns: id, name, description, order, status, display_options, group. Required: id.
Create a Freshstatus service	Create	Create a new service component in Freshstatus to display on your status page. Returns the created service including its id, name, description, order, display_options, and group. Required: name.
Update a Freshstatus service by ID	Update	Update a Freshstatus service by id. Returns the updated service object including id, name, description, order, status, display_options, and group. Required: id.
Delete a Freshstatus service by ID	Delete	Delete a Freshstatus service by id. Returns an empty 204 response on success. Required: id.

Toolboxes

Each team gets its own toolbox.

Scope Freshstatus toolboxes per team so incident response tools match responsibility.

SRE
Support
Engineering
IT Ops

ElaichiToolboxes

Name	Source template	Tools	Created
SRE toolbox Freshstatus · services and incident response	Freshstatus starter	18	Mar 4, 2026
Support toolbox Freshstatus · customer facing incident updates	—	9	Mar 2, 2026
Engineering toolbox Freshstatus · service health and groups	—	24	Feb 27, 2026
IT Ops toolbox Freshstatus · infrastructure incident status	Freshstatus starter	6	Feb 19, 2026
Product toolbox Freshstatus · service groups and dependencies	—	31	Jan 30, 2026
Leadership toolbox Freshstatus · incident visibility across teams	—	12	Jan 22, 2026

Shared 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

ElaichiConnections

Connection	Scope	Status	Access
FR Freshstatus (Platform Ops) Connected by Emily Carter	Personal	• Active	1 team · 6 members
FR Freshstatus (Customer Support) Connected by Jake Morgan	Organization	• Active	3 teams · 24 members
FR Freshstatus (Infrastructure) Connected by Megan Brooks	Organization	• Active	2 teams · 11 members
FR Freshstatus (Product Eng) Connected by Tyler Reed	Personal	• Needs re-auth	1 team · 3 members
FR Freshstatus (Regional Ops) Connected by Ryan Hayes	Personal	• Active	Not shared
FR Freshstatus (Leadership) Connected by Ashley Parker	Personal	• Active	2 teams · 9 members

Audit 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 log

When	Who	What happened	Type
2 minutes ago Mar 6, 2026, 3:10 PM	E Emily Carter emily.carter@northwind.io	Restriction Created	Access
8 minutes ago Mar 6, 2026, 3:04 PM	J Jake Morgan jake.morgan@northwind.io	Restriction Updated	Access
14 minutes ago Mar 6, 2026, 2:58 PM	M Megan Brooks megan.brooks@northwind.io	Role Assigned	Access
20 minutes ago Mar 6, 2026, 2:52 PM	T Tyler Reed tyler.reed@northwind.io	Freshstatus Users Updated	MCP
26 minutes ago Mar 6, 2026, 2:46 PM	R Ryan Hayes ryan.hayes@northwind.io	Freshstatus Services Created	MCP
32 minutes ago Mar 6, 2026, 2:40 PM	A Ashley Parker ashley.parker@northwind.io	Freshstatus Services List	Toolbox

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 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 Emily Carter

Run now

✓

Schedule

Every weekday at 8:00 AM

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

Live

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%

Related connectors

More from the catalog

Browse all 600+ connectors →

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.

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

Yes. Freshstatus 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.

Is Elaichi an alternative to Zapier MCP for Freshstatus?

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

How is Elaichi different from Composio for Freshstatus?

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

Put Freshstatus in front of your team

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

Connect Freshstatus Talk to us

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.