Inngest MCP by usefulapi

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

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Hosted Inngest MCP server that lets an assistant trace events to function runs and failing steps, and bulk-cancel runs.

What you can do
  • List and read events, including payloads and timestamps
  • Follow an event to the function runs it triggered and inspect each run's status, output and error
  • List the individual steps of a run with status and timing to find where a durable function failed
  • List bulk-cancellation jobs and webhook ingresses, and read a single webhook's URL and transform
  • Create or delete bulk cancellations and delete webhook ingresses
  • Check usage, request a feature, upgrade or cancel the subscription
When to use it
Useful when debugging Inngest-backed workflows: finding which event arrived, which function run it started, and which step failed. Also handy for stopping in-flight runs in a time window or removing a webhook ingress.
Requirements
Remote MCP endpoint; no local install. Connect with the URL only and sign in through OAuth, pasting your Inngest credentials on first connect, which are stored per user. No API key or Authorization header goes in the client config.
Before you install
Write tools change data: creating a cancellation stops in-flight runs of a production function, deleting a cancellation stops further cancelling, and deleting a webhook immediately stops its external source from producing events. Inngest credentials are pasted into the hosted service and stored per user. Free plan is limited to 50 tool calls per month; paid plans cost $9/month (Pro) or $39/month (Pro+), billed through a Stripe checkout link, with no refund for the current period on cancellation.

Installation

In SourceWeft

  1. Open Inngest MCP by usefulapi in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "inngest-by-usefulapi": {
      "type": "http",
      "url": "https://inngest.usefulapi.io/mcp"
    }
  }
}

README

Inngest MCP by usefulapi

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

Connect

  • Claude (claude.ai, Desktop): open Customize → Connectors, click + Add → Add custom connector, and paste https://inngest.usefulapi.io/mcp.
  • Claude Code: claude mcp add --transport http inngest https://inngest.usefulapi.io/mcp, then run /mcp to log in.
  • VS Code: Add to VS Code.
  • Cursor and other clients: add the URL as a remote MCP server:
json
{  "mcpServers": {    "inngest": {      "url": "https://inngest.usefulapi.io/mcp"    }  }}

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.

Tools

ToolTypeWhat it does
inngest_list_eventsreadList events
inngest_get_eventreadGet one event
inngest_list_event_runsreadList the runs an event started
inngest_get_runreadGet one function run
inngest_list_run_jobsreadList a run's steps
inngest_list_cancellationsreadList bulk cancellations
inngest_list_webhooksreadList webhooks
inngest_get_webhookreadGet one webhook
inngest_create_cancellationwriteBulk cancel function runs
inngest_delete_cancellationwriteStop a bulk cancellation
inngest_delete_webhookwriteDelete a webhook
inngest_usage_statusmetaUsage status (free-tier meter)
inngest_request_featuremetaRequest a missing feature
inngest_upgrademetaUpgrade to Pro or Pro+
inngest_cancel_subscriptionmetaCancel the Pro subscription

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.

Pricing

PlanPriceLimit
Free$050 tool calls / month
Pro$9/mo or $90/yr (2 months free)10,000 tool calls / month
Pro+$39/mo or $390/yr (2 months free)100,000 tool calls / month

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

License

MIT

Source: servers/inngest/README.md at commit f22f848

Tools

11

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.

Parameterslimitcursor

inngest_get_event

Get one event

Fetch a single event with its name, payload and timestamp. Inngest: GET /v1/events/{eventId}.

Parametersevent_idrequired

inngest_list_event_runs

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.

Parametersevent_idrequired

inngest_get_run

Get one function run

Fetch a single function run — its status, output and error. Inngest: GET /v1/runs/{runId}.

Parametersrun_idrequired

inngest_list_run_jobs

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.

Parametersrun_idrequired

inngest_list_cancellations

List bulk cancellations

List bulk-cancellation jobs and their progress. Inngest: GET /v1/cancellations.

Parameterslimitcursor

inngest_list_webhooks

List webhooks

List the webhook ingresses configured for the environment — the external sources that turn into events. Inngest: GET /v1/webhooks.

Parameterslimitcursor

inngest_get_webhook

Get one webhook

Fetch a single webhook ingress with its URL and transform. Inngest: GET /v1/webhooks/{webhookId}.

Parameterswebhook_idrequired

inngest_create_cancellation

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.

Parametersifapp_idrequiredfunction_idrequiredstarted_afterrequiredstarted_beforerequired

inngest_delete_cancellation

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

Parameterscancellation_idrequired

inngest_delete_webhook

Delete a webhook

Remove a webhook ingress. The external source stops producing events immediately. Inngest: DELETE /v1/webhooks/{webhookId}.

Parameterswebhook_idrequired

Version history

26
  1. v1.39.2LatestNov 14, 2026
  2. v1.39.1Nov 13, 2026
  3. v1.38.0Nov 12, 2026
  4. v1.37.3Nov 11, 2026
  5. v1.36.5Nov 8, 2026
  6. v1.36.4Nov 7, 2026
  7. v1.35.3Nov 5, 2026
  8. v1.35.2Nov 5, 2026
  9. v1.35.1Nov 4, 2026
  10. v1.35.0Nov 3, 2026
  11. v1.34.1Nov 3, 2026
  12. v1.33.0Nov 1, 2026
  13. v1.31.0Oct 31, 2026
  14. v1.30.0Oct 31, 2026
  15. v1.29.2Oct 30, 2026
  16. v1.29.0Oct 30, 2026
  17. v1.24.0Oct 26, 2026
  18. v1.21.3Oct 25, 2026
  19. v1.21.0Oct 25, 2026
  20. v1.20.0Oct 24, 2026
  21. v1.17.0Oct 23, 2026
  22. v1.16.4Oct 22, 2026
  23. v1.16.3Oct 21, 2026
  24. v1.11.1Oct 9, 2026
  25. v1.10.0Oct 9, 2026
  26. v1.0.0Sep 29, 2026

Score

100% 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.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Usefulapi integrations