Skip to main content
Watch: I Built an AI App Without Leaving Databricks

Automation - official Inngest server

Inngest Cloud MCP server

Hosted MCP server for Inngest Cloud that lets coding agents inspect and operate deployed apps, functions, events, runs, traces, environments, Insights, sessions, webhooks and experiments. Tools are generated from the Inngest REST API v2. Inngest hosts it at https://api.inngest.com/mcp with OAuth or API key auth.

Last verified 15 tools2 sources

Install

Terminal
claude mcp add --transport http inngest-cloud https://api.inngest.com/mcp
Terminal
codex mcp add inngest-cloud --url https://api.inngest.com/mcp
codex mcp login inngest-cloud
JSON
{
  "mcpServers": {
    "inngest-cloud": {
      "url": "https://api.inngest.com/mcp",
      "auth": {
        "CLIENT_ID": "inngest-mcp-static"
      }
    }
  }
}

Tools

list_runs
List runs, with optional app, function, status, and time filters.
get_run
Get the summary and optional output for one run.
get_run_trace
Get the trace tree and optional span output for one run.
send_event
Send an event and return its event ID.
invoke_function
Invoke a function and return its run details.
rerun
Rerun a function from the start or from a selected step.
cancel_run
Cancel an in-progress function run.
get_apps
List active or archived apps.
list_functions
List the functions in one app.
get_event_runs
List the function runs triggered by an event.
list_envs
List custom environments.
create_env
Create a custom environment.
query_insights
Run an Insights SQL query.
sync_app
Sync an app from its Inngest endpoint URL.
create_webhook
Create an incoming webhook.

As documented on October 17, 2026. A running server reports its current list through tools/list.

Notes and caveats

  • OAuth is recommended (choose account, environment access, permissions and session duration in the browser); an Inngest API key (not a signing key) works as a bearer token for clients without OAuth.
  • OAuth sessions cannot call credential-management tools such as fetch_account_event_keys.
  • Some tools change data (send events, invoke, rerun or cancel runs, sync apps, manage environments and webhooks).
  • Also bundled in the Inngest Claude Code plugin (claude plugin install inngest@anthropic-plugin-directory); a Codex plugin is described as coming soon.

FAQ

What does the Inngest Cloud MCP server do?

Hosted MCP server for Inngest Cloud that lets coding agents inspect and operate deployed apps, functions, events, runs, traces, environments, Insights, sessions, webhooks and experiments. Tools are generated from the Inngest REST API v2. The vendor documents 15 tools, including list_runs, get_run, get_run_trace and send_event.

How do I add the Inngest Cloud MCP server to Claude Code?

Run claude mcp add --transport http inngest-cloud https://api.inngest.com/mcp, copied from Inngest's docs. This page also has snippets for Codex and Cursor.

Does the Inngest Cloud MCP server need authentication?

Yes, OAuth or API key. Transport: Streamable HTTP. Status: Unlabelled, last checked October 17, 2026.

Sources

Last verified against 2 Inngest pages, then re-checked independently.

Newsletter

New MCP servers, the week they ship

One email per week. New official MCP servers, the coding tools that support them and how developers wire them up.