Inngest MCP connector
The Inngest connector lets Claude, ChatGPT, Cursor, Microsoft Copilot and other MCP clients list your Inngest apps, functions, runs and environments, rerun or invoke functions, and manage webhooks and keys, with every action signed in as you and logged.
- Connects with an API key
- Free 14-day trial
- No credit card
ChatGPT
Elaichi connected
List failed event runs for our checkout functions this week.
Working in Inngest with Elaichi
-
List all Inngest accounts
-
-
Governance
/
Audit log
Last 24 hours
ChatGPT · 9:41 AM
Done
ChatGPT · 9:41 AM
Done
ChatGPT · 9:41 AM
Done
Claude · 9:38 AM
Done
Cursor · 9:35 AM
Done
How to connect Inngest to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Inngest 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.
Inngest MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith 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.
Inngest 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.
Inngest 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.
Inngest 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 Inngest 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.
What teams do with Inngest through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Inngest is logged.
-
Engineering
Find out why a run failed
Ask for the failed runs of a function from the last hour and pull up one run to see where it stopped and what it was working on.
-
On-call
Rerun the jobs that failed overnight
List the runs that failed while nobody was watching, then rerun them in one go once the cause is fixed.
-
Engineering
Trigger a function on demand
Invoke a function with the payload you need to test a fix or process one customer's data right now, without opening the Inngest dashboard.
-
Platform
Set up a new environment with webhooks
Create a staging or preview environment, add the webhooks it needs and confirm which event keys and signing keys belong to it.
-
Support
Check whether a customer's job ran
When a customer says an email or export never arrived, look up the event runs for that event and see whether the function ran, is still running or failed.
-
Product
Review function experiments and score runs
List the experiments running on a function, compare their runs and record a score against a run so the team can see which version is winning.
Try asking
- “List failed event runs for our checkout functions this week.”
- “Which Inngest apps have functions without a recent sync?”
- “Show function experiments running in the production env.”
What connecting Inngest gets you
6 screens from Elaichi, each doing one job for your Inngest account.
Ask Elaichi to work across your apps.
List failed event runs for our checkout functions this week.
Which Inngest apps have functions without a recent sync?
Show function experiments running in the production env.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about Inngest runs, get answers.
Plain language questions answered from live Inngest apps, functions and event runs.
ElaichiAI appsClaude
ChatGPT
Cursor
Microsoft Copilot
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach Inngest.
One governed MCP endpoint over OAuth, no SDK and no shared API key.
ElaichiToolsTool catalog
39 Inngest tools ready without custom code.
Browse apps, functions, experiments, envs and webhooks with methods already wired up.
ElaichiToolboxesToolboxes
Every team gets its own Inngest toolbox.
Platform, backend and on call each see the Inngest tools they need.
ElaichiConnectionsShared connections
Teammates run Inngest without a credential.
See who connected each Inngest account and which teams and members use it.
ElaichiAudit logAudit log
Every Inngest call is on the record.
When, who, what happened, type and resource for each Inngest function and run.
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.
Inngest digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch apps
Inngest
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
Inngest
Queued
Automations
A schedule fires, Inngest work gets done.
Fetch event runs, group them, draft a digest, approve, post back to Inngest.
Inngest health
Refreshed 4 minutes ago · every 15 minutes · from the apps collection
Apps
1,284 ↓ 12%
Functions
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Apps created
Last 14 days
By team
Share of activity
Production 34%
Staging 27%
Platform 21%
Payments 18%
Collections and dashboards
Inngest health, counted on a schedule.
Four metrics, 14 days of runs created and a breakdown by team.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Inngest
All three can connect Inngest to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| 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 Inngest tools | Allow or restrict single Inngest 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 Inngest 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.
Inngest tools for your AI agents
39 tools are ready to call through Elaichi's MCP endpoint the moment you connect Inngest, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect Inngest to Claude?
Connect Inngest in Elaichi by pasting an API key from your Inngest account; there is no OAuth app to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Claude signs you in through Elaichi and Inngest is available in your chat.
Does Inngest work with ChatGPT and Cursor as well as Claude?
Yes. Once Inngest 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 Inngest once and every client picks it up.
What can an AI agent actually do with my Inngest data?
With Inngest connected, an agent can list your apps, functions, environments, runs and event runs, open a single run to see what happened, rerun or delete a run, invoke a function, sync an app after a deploy, create or update environments, add webhooks and check event keys and signing keys. Because Inngest exposes many actions, short concrete asks such as "show failed runs for the billing function today" work better than long sentences.
Does connecting Inngest give the AI access to every environment and account?
No. Every request to Inngest runs under the API key of the person who connected it, so the agent can only see the accounts, environments and functions that key already reaches in Inngest. Elaichi can narrow that further with restrictions per action, and it can never widen it beyond what Inngest itself allows.
Can I stop an agent from deleting or changing things in Inngest?
Yes. Restrictions in Elaichi work per action, so you can allow reading Inngest runs and functions while restricting deleting a run, invoking a function or changing an environment. 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 Inngest connection when someone leaves?
When you offboard a person in Elaichi, their access to Inngest through every client ends at once. If they shared an Inngest connection, it keeps working for everyone else on the team. Disconnecting Inngest once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client together.
Does the Inngest MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Inngest 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 Inngest?
Yes. Both let Claude, ChatGPT or Cursor use Inngest. 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 Inngest call.
How is Elaichi different from Composio for Inngest?
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 Inngest: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Inngest 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