Skip to content

Summary

Inngest's official MCP servers for Cloud and the local Dev Server — inspect functions, replay runs, send test events and query Insights from a coding agent.

Features

  • Two endpoints: unauthenticated local Dev Server and API-key-authenticated Cloud
  • 14 shared tools — list apps, functions and runs, read run traces, send events, invoke, rerun, cancel
  • 19 Cloud-only tools — environments, webhooks, signing keys, experiments, scores, sessions
  • query_insights exposes Inngest's SQL Insights engine to the agent
  • Dev Server ships list_docs / grep_docs / read_doc for in-session documentation lookup
  • One-line setup for Claude Code, Codex, Cursor and VS Code
  • Cursor config uses ${env:INNGEST_API_KEY} so the key stays out of version control

Installation

Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.

Any MCP-compatible agent

Most agents (Claude, Cursor, Windsurf, VS Code, and more) read a standard mcpServers configuration.

  1. Open your agent's MCP configuration file.
  2. Merge the snippet below into it.
  3. Restart the agent — the "Inngest MCP Server" tools will be available.
{
  "mcpServers": {
    "inngest-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "http://127.0.0.1:8288/mcp"
      ]
    }
  }
}

Description

Inngest is a durable-execution platform for background jobs, queues and step functions. Its official Model Context Protocol integration ships as two endpoints, and the split is the useful part: http://127.0.0.1:8288/mcp on the local Dev Server needs no authentication at all, while https://api.inngest.com/mcp reaches production and requires an Inngest API key as a bearer token.

Fourteen shared tools work against either endpoint: list_apps, get_app, list_functions, get_function, list_runs, list_function_runs, get_event_runs, get_run, get_run_trace, send_event, invoke_function, rerun, cancel_run and health. That set is enough for the loop a coding agent actually needs — write a function, send it a test event, read the trace when it fails, fix it, rerun.

Nineteen Cloud-only tools cover the things that only exist on a real account: environment management (create_env, list_envs, patch_env), webhooks and signing keys, event schemas, experiments and scores for A/B-testing code variants against live traffic, session inspection, and — notably — query_insights and query_insights_prompt, which expose Inngest's SQL-based Insights engine so an agent can ask "which function has the highest failure rate this week" instead of clicking through a dashboard.

Three Dev Server-only tools are documentation retrieval: list_docs, grep_docs and read_doc. They let an agent look up Inngest's own API surface without leaving the session or burning a web search.

Setup is one command. Claude Code: claude mcp add --transport http inngest-dev http://127.0.0.1:8288/mcp for local work, or the Cloud URL with an Authorization: Bearer $INNGEST_API_KEY header. Codex takes codex mcp add ... --bearer-token-env-var INNGEST_API_KEY. Cursor takes a short JSON block with ${env:INNGEST_API_KEY} interpolation, so the key stays out of the committed config.

Related MCP Servers

MCP: Dagster+ MCP Server

by Dagster Labs

Dagster Labs' official remote MCP server for Dagster+: inspect assets, runs, run logs and Insights metrics, and launch runs from an AI session.

MCP: Sentry

by Sentry

Sentry's official MCP server — investigate errors and issues, inspect events, and use Seer for root-cause analysis.

MCP: Cloudflare

by Cloudflare

Cloudflare's catalogue of managed remote MCP servers — docs, Workers bindings and builds, observability, Radar, Browser Run, AI Gateway, CASB and more, each on its own OAuth endpoint.

Trigger.dev's official MCP server — trigger and monitor background jobs, deploy to any environment, and query runs with TRQL from your coding agent.

Browse all MCP servers →