Integration

Inngest integration

Inngest is an event-driven background jobs platform for developers. Build reliable workflows with automatic retries, step functions, scheduling, and event coordination. Features include durable execution, fan-out patterns, debouncing, throttling, and observability. Perfect for async processing, scheduled tasks, event-driven architectures, and complex workflow orchestration without managing infrastructure.

Connect Inngest How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Inngest.Built from the 11 Inngest tools below, on the connection you add once.

Common Inngest use cases

performance analysis
auditing event flow
debugging step failures
inspecting event payload
auditing cancellation rules
debugging failed executions
emergency bulk cancellation
stopping erroneous executions
cleaning up cancellation rules
tracing event-to-function flow

What you can do with Inngest

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Run, 4 operations

cancel_runCancel runPOSTCancels a running Inngest function execution. Stops the run at the next step boundary.
get_runGet runGETRetrieves detailed information about an Inngest function run. Returns status, timing, and output data.
get_run_jobsGet run jobsGETFetches step-level job details for an Inngest function run. Returns individual step execution data.
list_event_runsList event runsGETLists function runs triggered by a specific event. Returns run status, timing, and output data.

Cancellation, 3 operations

create_cancellationCreate cancellationPOSTCreates a bulk cancellation rule to cancel Inngest function runs matching specific criteria within a time window.
delete_cancellationDelete cancellationDELETEDeletes a specific bulk cancellation rule from the Inngest environment.
list_cancellationsList cancellationsGETLists all bulk cancellation rules in the current Inngest environment.

Event, 3 operations

get_eventGet eventGETRetrieves detailed information about an Inngest event. Shows event data and metadata.
list_eventsList eventsGETLists events sent to Inngest. Returns event history with names, data, and timestamps.
send_eventSend eventPOSTSends one or more events to Inngest to trigger background functions. Events are the primary mechanism for invoking async workflows.

Function, 1 operation

list_app_functionsList app functionsGETLists all Inngest functions for a specific app. Returns function configurations, triggers, and settings.

Use Inngest from Claude Code, Cursor or Codex

Connect Inngest in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Inngest operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Inngest

Create your workspace
Sign up free. Nothing to install.
Connect Inngest once
Add your Inngest connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Inngest integration FAQ

What can you do with the Inngest integration?

LiveContext exposes 11 operations on Inngest, covering run, cancellation, event and function. Common uses include performance analysis, auditing event flow and debugging step failures.