Skip to main content
Glama
doctone

inngest-cloud-mcp

by doctone
README.md
# inngest-cloud-mcp

MCP server for the [Inngest](https://www.inngest.com/) Cloud REST API — inspect functions, runs, and events in production from Claude Code, Cursor, or any MCP client.

## Setup

### Claude Code

```bash
claude mcp add inngest-cloud -- npx inngest-cloud-mcp
```

Then set the `INNGEST_SIGNING_KEY` environment variable. Find yours at [app.inngest.com](https://app.inngest.com/env/production/manage/signing-key).

### Manual (`.mcp.json`)

```json
{
  "mcpServers": {
    "inngest-cloud": {
      "command": "npx",
      "args": ["inngest-cloud-mcp"],
      "env": {
        "INNGEST_SIGNING_KEY": "your-signing-key"
      }
    }
  }
}
```

## Tools

| Tool | Description |
| --- | --- |
| `list_events` | List recent events with optional name/time filters |
| `get_event` | Get a single event by ID |
| `get_event_runs` | List function runs triggered by an event |
| `get_run` | Get status and output of a function run |
| `cancel_run` | Cancel a specific function run |
| `list_functions` | List all functions for an app |
| `create_cancellation` | Bulk cancel runs matching criteria |
| `list_cancellations` | List active bulk cancellation rules |

## Development

```bash
pnpm install
pnpm run dev        # Run with tsx
pnpm run build      # Build with tsup
pnpm run typecheck  # Type check
```

## License

MIT

TDQS

B3.4/5.0

Scored across 8 tools

Disambiguation5/5

Each tool targets a distinct resource and action: listing functions vs events, getting an event vs its runs, getting a run vs cancelling it, and creating vs listing cancellations. Descriptions clearly differentiate the cancellation tools, so an agent can select correctly.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern: list_functions, list_events, get_event, get_event_runs, get_run, cancel_run, create_cancellation, list_cancellations. No deviations or mixed conventions.

Tool Count5/5

Eight tools is well-scoped for an Inngest cloud management server covering functions, events, runs, and cancellations. Each tool earns its place without redundancy.

Completeness3/5

Core read and cancellation operations are present, but there are notable gaps: no tool to delete or update a bulk cancellation rule after creation, no way to list all runs independent of an event, and no get_function details. These missing lifecycle operations could force agents into dead ends.

Maintenance

ActivityInactive
ResponsivenessNo issues