inngest_list_events
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.
limitcursorio.usefulapiPublished by usefulapi.ioOfficial publisherv1.39.2Updated Nov 14, 2026
Trace events to function runs to the failing step, and bulk-cancel runs.
The publisher's own server: Ably MCP by usefulapi
Hosted Inngest MCP server that lets an assistant trace events to function runs and failing steps, and bulk-cancel runs.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.usefulapi%2Finngest/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Add this to your client's mcpServers config.
{
"mcpServers": {
"inngest-by-usefulapi": {
"type": "http",
"url": "https://inngest.usefulapi.io/mcp"
}
}
}Trace events to function runs to the failing step, and bulk-cancel runs. Hosted, no local install.
Live endpoint: https://inngest.usefulapi.io/mcp · Homepage: https://usefulapi.io
https://inngest.usefulapi.io/mcp.claude mcp add --transport http inngest https://inngest.usefulapi.io/mcp, then run /mcp to log in.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, and the login page asks for your Inngest credentials.
Step-by-step setup, where to find your credentials, and FAQ: https://usefulapi.io/inngest/
On first connect you'll paste your Inngest credentials. They are validated, stored per-user, and scoped to you — no keys in config files.
read tools are read-only; write tools mutate data (clients should confirm them); meta tools report usage, manage your subscription or send a feature request.
Each paid plan covers this server only. Ask your AI to run inngest_upgrade and choose Pro or Pro+, billed monthly or yearly (it returns a Stripe Checkout link). If you already have Pro, ask to change it to Pro+. The change requires your confirmation, keeps your billing interval and charges the price difference for the rest of the period immediately. Cancel any time with inngest_cancel_subscription: your paid plan continues to the end of the paid period, with no refund for the current period, and asking to resume the same plan with inngest_upgrade before then undoes the cancel. Or write to [email protected].
MIT
Source: servers/inngest/README.md at commit f22f848
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.
limitcursorGet one event
Fetch a single event with its name, payload and timestamp. Inngest: GET /v1/events/{eventId}.
event_idrequiredList 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.
event_idrequiredGet one function run
Fetch a single function run — its status, output and error. Inngest: GET /v1/runs/{runId}.
run_idrequiredList 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.
run_idrequiredList bulk cancellations
List bulk-cancellation jobs and their progress. Inngest: GET /v1/cancellations.
limitcursorList webhooks
List the webhook ingresses configured for the environment — the external sources that turn into events. Inngest: GET /v1/webhooks.
limitcursorGet one webhook
Fetch a single webhook ingress with its URL and transform. Inngest: GET /v1/webhooks/{webhookId}.
webhook_idrequiredBulk 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.
ifapp_idrequiredfunction_idrequiredstarted_afterrequiredstarted_beforerequiredStop 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}.
cancellation_idrequiredDelete a webhook
Remove a webhook ingress. The external source stops producing events immediately. Inngest: DELETE /v1/webhooks/{webhookId}.
webhook_idrequired100% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
io.usefulapiOfficial publisher
Hosted MCP server for Ably that lets an assistant inspect realtime channels, presence and usage stats, publish messages, and review app configuration.
io.usefulapiOfficial publisher
Read-only access to ROLLER venue data: search bookings, check product availability, and look up guests, waivers, gift cards and daily reports.
io.usefulapiOfficial publisher
Hosted Planerio connector that lets an assistant read shifts, staffing requirements, staff, employees, absences and vacation days.
io.usefulapiOfficial publisher
Read-only access to Marmin UAE e-invoicing data: invoices, credit notes, UBL XML, Peppol status and business profiles.
io.usefulapiOfficial publisher
Remote MCP server for Oyster that lets an assistant read team, time off, expense, contract and invoice data and approve or decline requests.
{ "mcpServers": { "inngest": { "url": "https://inngest.usefulapi.io/mcp" } }}