Trace events to function runs to the failing step, and bulk-cancel runs. Hosted by usefulapi — connect from Claude, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"inngest": {
"url": "https://inngest.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"inngest": {
"type": "http",
"url": "https://inngest.usefulapi.io/mcp"
}
}
}Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your Inngest signing key.
Copy it from Inngest → Manage → Signing key. Your token is used only to call the API on your behalf and to derive a private account id; it is never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Inngest signing key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the Inngest connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
inngest_list_events | read | List events List the events received in the key's environment, newest first. Events are what start functions, so this is where an investigation begins. Inngest: GET /v1/events. |
inngest_get_event | read | Get one event Fetch a single event with its name, payload and timestamp. Inngest: GET /v1/events/{eventId}. |
inngest_list_event_runs | read | List the runs an event started List every function run one event triggered, with each run's status. This is the hop from 'this event arrived' to 'and here is what it did'. Inngest: GET /v1/events/{eventId}/runs. |
inngest_get_run | read | Get one function run Fetch a single function run — its status, output and error. Inngest: GET /v1/runs/{runId}. |
inngest_list_run_jobs | read | List a run's steps List the individual steps (jobs) of one run, with their status and timing — how you find which step of a durable function failed. Inngest: GET /v1/runs/{runId}/jobs. |
inngest_list_cancellations | read | List bulk cancellations List bulk-cancellation jobs and their progress. Inngest: GET /v1/cancellations. |
inngest_list_webhooks | read | List webhooks List the webhook ingresses configured for the environment — the external sources that turn into events. Inngest: GET /v1/webhooks. |
inngest_get_webhook | read | Get one webhook Fetch a single webhook ingress with its URL and transform. Inngest: GET /v1/webhooks/{webhookId}. |
inngest_create_cancellation | write | Bulk cancel function runs Cancel every run of one function that started within a time window, optionally narrowed by an event expression. This STOPS IN-FLIGHT WORK across your production functions — scope the window tightly. Runs already finished are unaffected. Inngest: POST /v1/cancellations. |
inngest_delete_cancellation | write | Stop a bulk cancellation Delete a bulk-cancellation job so it stops cancelling further runs. Runs it already cancelled stay cancelled. Inngest: DELETE /v1/cancellations/{cancellationId}. |
inngest_delete_webhook | write | Delete a webhook Remove a webhook ingress. The external source stops producing events immediately. Inngest: DELETE /v1/webhooks/{webhookId}. |
inngest_usage_status | Usage status (free-tier meter) Report the caller's current free-tier usage this month: calls used, monthly limit, remaining, and whether the cap is reached. Read-only; does not count against the meter. | |
inngest_request_feature | Request a missing feature Tell usefulapi that the user needs something the Inngest tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
inngest_upgrade | Upgrade to Pro (unlimited) Subscribe to the Pro plan for UNLIMITED Inngest tool calls (the free tier caps monthly usage). Choose monthly ($9/month) or yearly ($90/year — 2 months free) billing. Returns a Stripe Checkout link to open in your browser; after payment your account upgrades automatically. Does not count against the meter. | |
inngest_cancel_subscription | Cancel the Pro subscription Cancel the caller's Inngest Pro subscription at the end of the paid period (no refund for the current period; unlimited calls continue until then, then the free tier applies). Requires confirm: true. Run inngest_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 100 tool calls / month |
| Pro | $9/mo · $90/yr | Unlimited |
Pro covers this Inngest server only. Subscribe with inngest_upgrade (it returns a Stripe Checkout link). Cancel any time with inngest_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running inngest_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by Inngest. The server calls the Inngest API with your own Inngest access, so it sees only the data that your account can see.
The login page asks for your Inngest signing key. See Before you connect for where to find it.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Inngest signing key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Inngest API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Inngest.
Yes, if you approve it. 3 of the 11 Inngest tools can create or change data. The other 8 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 100 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls, for this Inngest server only. Run inngest_usage_status to see how many calls you used.
Ask the AI to run inngest_upgrade: it returns a Stripe Checkout link. To cancel, run inngest_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with inngest_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.