Inngest MCP by usefulapi

Reviewed 1d ago.

• tools: 11 tools scanned
• metadata: scanned

No findings.

Tools (11)

• inngest_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

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

• inngest_list_event_runs

  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

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

• inngest_list_run_jobs

  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

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

• inngest_list_webhooks

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

• inngest_get_webhook

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

• inngest_create_cancellation

  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

  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

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