# Inngest

> Built-in MCP for Inngest functions, events, runs, and docs — zero auth, zero config.

[Canonical HTML page](https://top-mcps.com/mcp/inngest) · [server.json](https://top-mcps.com/mcp/inngest.json) · [methodology](https://top-mcps.com/about/methodology)

## Install

### Claude Desktop — `claude_desktop_config.json`

Paste under mcpServers. Fully quit and reopen Claude after editing.

```json
{
  "mcpServers": {
    "inngest": {
      "command": "inngest",
      "args": [
        "dev"
      ]
    }
  }
}
```

### Claude Code — `CLI or .mcp.json`

Run from your repo. Commit .mcp.json to share with your team.

```shell
claude mcp add inngest -- inngest dev
```

### Cursor — `.cursor/mcp.json`

Global path: ~/.cursor/mcp.json. Reload window after editing.

```json
{
  "mcpServers": {
    "inngest": {
      "command": "inngest",
      "args": [
        "dev"
      ]
    }
  }
}
```

### VS Code — `.vscode/mcp.json`

VS Code uses the "servers" key (not "mcpServers").

```jsonc
{
  "servers": {
    "inngest": {
      "command": "inngest",
      "args": [
        "dev"
      ]
    }
  }
}
```

### Windsurf — `~/.codeium/windsurf/mcp_config.json`

Open via Cascade → hammer icon → Configure.

```json
{
  "mcpServers": {
    "inngest": {
      "command": "inngest",
      "args": [
        "dev"
      ]
    }
  }
}
```

### Cline — `cline_mcp_settings.json`

Open via the Cline sidebar → MCP Servers → Edit.

```json
{
  "mcpServers": {
    "inngest": {
      "command": "inngest",
      "args": [
        "dev"
      ]
    }
  }
}
```

### Continue — `~/.continue/config.json`

Continue uses modelContextProtocolServers with a transport block.

```json
{
  "experimental": {
    "modelContextProtocolServers": [
      {
        "transport": {
          "type": "stdio",
          "command": "inngest",
          "args": [
            "dev"
          ]
        }
      }
    ]
  }
}
```

### Codex CLI — `~/.codex/config.toml`

Codex uses TOML. Each server is a [mcp_servers.<name>] subtable.

```shell
# ~/.codex/config.toml
[mcp_servers.inngest]
command = "inngest"
args = [
  "dev",
]
```

### Zed — `~/.config/zed/settings.json`

Zed calls them "context_servers". Settings live-reload on save.

```jsonc
{
  "context_servers": {
    "inngest": {
      "command": {
        "path": "inngest",
        "args": [
          "dev"
        ]
      }
    }
  }
}
```

### ChatGPT — `ChatGPT → Settings → Connectors (remote URL)`

Paste this into Settings → Connectors → Add custom connector. Requires ChatGPT Pro / Team / Enterprise / Edu with Developer mode enabled. ChatGPT supports remote HTTPS MCP servers only — stdio servers must be hosted on a public HTTPS endpoint first.

```json
{
  "name": "Inngest",
  "transport": "http",
  "url": "http://127.0.0.1:8288/mcp"
}
```

## At a glance

- **Maintainer:** Inngest
- **Transport:** Streamable HTTP
- **Auth model:** None
- **Required secrets:** None
- **Supported clients:** Claude, Cursor, Any MCP-compatible client, Inngest dev server
- **Latest version:** latest
- **Last verified:** 2026-05-27
- **Score:** 59/100 (rubric 2026-04 — see https://top-mcps.com/about/methodology)
- **Homepage:** https://www.inngest.com/docs/ai-dev-tools/mcp

## Quick answer

**What it does.** Exposes Inngest dev-server operations as MCP tools: send_event, list_functions, invoke_function, get_run_status, poll_run_status, grep_docs, read_doc, list_docs.

**Best for:**
- Local Inngest dev workflows
- Sending test events from chat
- Monitoring runs while debugging
- Searching Inngest docs inline
- Zero-config setup

**Not for:**
- Production Inngest Cloud operations
- Workflows requiring auth or remote access
- Use cases where `inngest dev` is not already running

## Description

The Inngest MCP is bundled into the Inngest dev server. Run `inngest dev` and the MCP is live at 127.0.0.1:8288/mcp — no API keys, no install, no external dependencies. Surfaces 8 tools across event management, run monitoring, and docs.

## Why it matters

Inngest is the developer-tier event/workflow engine. Bundling the MCP in the dev server means there is literally no setup — `inngest dev` and the agent can manage everything.

## Key features

- Built into `inngest dev` — no install
- HTTP transport at 127.0.0.1:8288/mcp
- Zero auth, zero external deps
- 8 tools across events, runs, docs
- No API keys required

## FAQ

### Auth?

None — the MCP runs locally inside `inngest dev` with no API keys or external dependencies.

### Production use?

No — this is the local dev-server MCP. Production Inngest Cloud uses the SDK directly.

### How do I wire it into Claude?

Add an HTTP MCP entry pointing at http://127.0.0.1:8288/mcp while `inngest dev` is running.

## Changelog

- **2026-05-27** — Refreshed install snippets and fact sheet; verified for 2026.
- **2025-08-15** — Initial directory listing.