Skip to main content
hc
Submit
mcpSource-backedReview first Safety ✓ Privacy ✓

Inngest MCP Server for Claude

Connect Claude to your local Inngest Dev Server — list functions, send events, invoke functions, monitor run status, and search Inngest documentation — with the built-in Inngest Model Context Protocol server that ships with the Inngest dev environment.

by Inngest·added 2026-06-18·
Claude CodeCodexCursorClaude Desktop
HarnessClaude CodeCodexCursorClaude Desktop
Review first — review before installing

Open the source and read safety notes before installing.

Safety notes

  • The MCP server runs locally alongside your Inngest dev server — it has no network access and cannot affect production environments.
  • `send_event` and `invoke_function` trigger real function executions in your local dev environment; confirm before running functions with external side effects.

Privacy notes

  • Function definitions, event payloads, run logs, and Inngest documentation content from your local dev server are surfaced in Claude's context.
  • No API keys or credentials are required — the MCP server runs entirely on localhost without sending data to Inngest's servers.

Prerequisites

  • Node.js installed — run `npx inngest-cli@latest dev` to start the Inngest Dev Server before connecting.
  • The Inngest Dev Server must be running at `http://localhost:8288` for the MCP endpoint to be available.
  • An MCP client such as Claude Code or Claude Desktop.

Schema details

Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
5 minutes
Difficulty
beginner
Tool listing metadata
Full copyable content
{
  "mcpServers": {
    "inngest-dev": {
      "type": "http",
      "url": "http://127.0.0.1:8288/mcp"
    }
  }
}

About this resource

Overview

The Inngest MCP Server is built directly into the Inngest Dev Server. When you run npx inngest-cli@latest dev, the MCP endpoint is automatically available at http://127.0.0.1:8288/mcp — no additional install or API key required. It gives Claude direct access to your registered Inngest functions, event system, run monitoring, and documentation, enabling AI-assisted development for durable functions, workflows, and background jobs.

The Inngest server is Apache-2.0 (SDKs) and SSPL (server/CLI).

Key capabilities

  • Function discovery — list all functions registered with the local dev server.
  • Event triggering — send arbitrary events to trigger functions and test workflows.
  • Direct invocation — invoke functions synchronously and get immediate results.
  • Run monitoring — fetch run status and poll for completion on asynchronous workflows.
  • Documentation access — search and read Inngest documentation without leaving your IDE.

Tools

Tool Category Purpose
list_functions Event Management List all registered Inngest functions
send_event Event Management Trigger a function via an Inngest event
invoke_function Event Management Directly invoke a function and get its result
get_run_status Execution Monitoring Fetch the status of a specific run
poll_run_status Execution Monitoring Wait for a run to complete and return result
grep_docs Documentation Search Inngest documentation offline
read_doc Documentation Read a specific Inngest documentation page
list_docs Documentation List available Inngest documentation pages

How it compares

Server Function listing Event triggering Run monitoring Docs search Auth
Inngest MCP Yes Yes Yes Yes None (local)
Temporal MCP Yes Limited Yes No API key
Trigger.dev MCP Yes Yes Limited No CLI session
BullMQ MCP Limited Yes Limited No Redis creds

Inngest's MCP is the only background-job/workflow server that ships with offline documentation search, requires zero authentication, and runs entirely on localhost with no external dependencies.

Installation

Step 1: Start the Inngest Dev Server

npx inngest-cli@latest dev

The MCP endpoint becomes available at http://127.0.0.1:8288/mcp automatically.

Step 2: Connect Claude Code

claude mcp add --transport http inngest-dev http://127.0.0.1:8288/mcp

Step 2 (alternative): Claude Desktop

{
  "mcpServers": {
    "inngest-dev": {
      "type": "http",
      "url": "http://127.0.0.1:8288/mcp"
    }
  }
}

Requirements

  • Node.js (for npx inngest-cli) or the Inngest binary from GitHub Releases.
  • The Inngest Dev Server running at http://localhost:8288.
  • An MCP client (Claude Code or Claude Desktop).

Security

  • Entirely local — no API keys, no network traffic to Inngest's servers.
  • send_event and invoke_function run against your local dev server only.
  • For production Inngest workflows, use the Inngest Cloud dashboard separately.

Source Verification Notes

Verified on 2026-06-18:

  • Official Inngest documentation MDX source at raw.githubusercontent.com/inngest/website/main/pages/docs/ai-dev-tools/mcp.mdx documents the MCP endpoint at http://127.0.0.1:8288/mcp, all eight tools (send_event, list_functions, invoke_function, get_run_status, poll_run_status, grep_docs, read_doc, list_docs), the zero-authentication local model, and the Claude Code install command.
  • Main Inngest repository inngest/inngest README confirms npx inngest-cli@latest dev as the command to start the dev server.
  • Claude Code MCP documentation at code.claude.com/docs/en/mcp describes the --transport http connection pattern used above.
#inngest#durable-functions#background-jobs#workflows#event-driven#devtools#local-dev

Source citations

Add this badge to your README

Show that Inngest MCP Server for Claude is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/inngest-mcp-server.svg)](https://heyclau.de/entry/mcp/inngest-mcp-server)

How it compares

Inngest MCP Server for Claude side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

FieldInngest MCP Server for Claude

Connect Claude to your local Inngest Dev Server — list functions, send events, invoke functions, monitor run status, and search Inngest documentation — with the built-in Inngest Model Context Protocol server that ships with the Inngest dev environment.

Open dossier 		Android Skills MCP Server for Claude

Access AI-optimized Android development guides from Claude — search and retrieve SKILL.md content covering Jetpack Compose, Navigation 3, CameraX, AGP 9, App Functions, Edge-to-Edge, Android Profilers, XR, Google Play, and the Android CLI — with the Android Skills MCP server.

Open dossier 		MCP SQLite Server for Claude

Read and write any local SQLite database from Claude — get database info, list tables, inspect schemas, create/read/update/delete records, and run raw SQL queries — with the MCP SQLite server that connects to any `.db` file you specify.

Open dossier 		Appwrite MCP Server for Claude

Connect Claude to the full Appwrite backend platform — databases, authentication, serverless functions, teams, messaging, and storage — with the official Appwrite MCP server using dynamic dispatch across the entire Appwrite API surface.

Open dossier
Trust
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
Categorymcpmcpmcpmcp
Sourcesource-backedsource-backedsource-backedsource-backed
AuthorInngestJaewoong Eum (skydoves)jparkerwebAppwrite
Added2026-06-182026-06-182026-06-182026-06-18
Platforms
Claude CodeCodexCursorClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Source repo————
Safety notes✓The MCP server runs locally alongside your Inngest dev server — it has no network access and cannot affect production environments. `send_event` and `invoke_function` trigger real function executions in your local dev environment; confirm before running functions with external side effects.✓The server runs entirely offline — no network requests are made during queries. All skill content is bundled with the npm package.✓The `query` tool executes arbitrary SQL including INSERT, UPDATE, and DELETE statements — it is not read-only. Point the server at a copy or test database to avoid accidental data loss before trusting it with production data.✓Mutation operations (write, update, delete) require `confirm_write=true` to be passed explicitly, adding a confirmation step before any destructive action. The API key scope determines what operations are available — use least-privilege scopes for your use case.
Privacy notes✓Function definitions, event payloads, run logs, and Inngest documentation content from your local dev server are surfaced in Claude's context. No API keys or credentials are required — the MCP server runs entirely on localhost without sending data to Inngest's servers.✓No API keys, user data, or query content is sent to any external service. All lookups happen locally against the bundled skill snapshot.✓All database content including table schemas, record data, and query results are surfaced in Claude's context — do not connect databases containing sensitive personal or credential data unless you intend to share it with the model. No credentials are required and no data is sent to external services — the server operates entirely locally.✓User records, database documents, function logs, team memberships, and messaging data from your Appwrite project are surfaced in Claude's context. Your `APPWRITE_API_KEY` grants project-level access — keep it in the MCP config env and never commit it to version control.
Prerequisites
  • Node.js installed — run `npx inngest-cli@latest dev` to start the Inngest Dev Server before connecting.
  • The Inngest Dev Server must be running at `http://localhost:8288` for the MCP endpoint to be available.
  • An MCP client such as Claude Code or Claude Desktop.
  • Node.js with `npx` available.
  • An MCP client such as Claude Code or Claude Desktop.
  • A local SQLite database file (`.db`) you want to connect to.
  • Node.js with `npx` available.
  • An MCP client such as Claude Code or Claude Desktop.
  • An Appwrite account — log in at cloud.appwrite.io or self-hosted.
  • An Appwrite project with an API key that has the required scopes for your use case.
  • Python with `uvx` available.
  • An MCP client such as Claude Code or Claude Desktop.
Install
claude mcp add --transport http inngest-dev http://127.0.0.1:8288/mcp
claude mcp add android-skills -- npx -y android-skills-mcp
claude mcp add sqlite -- npx -y mcp-sqlite /path/to/database.db
claude mcp add appwrite -e APPWRITE_PROJECT_ID=<project-id> -e APPWRITE_API_KEY=<api-key> -- uvx mcp-server-appwrite
Config
{
  "mcpServers": {
    "inngest-dev": {
      "type": "http",
      "url": "http://127.0.0.1:8288/mcp"
    }
  }
}
{
  "mcpServers": {
    "android-skills": {
      "command": "npx",
      "args": ["-y", "android-skills-mcp"]
    }
  }
}
{
  "mcpServers": {
    "sqlite": {
      "command": "npx",
      "args": ["-y", "mcp-sqlite", "/path/to/database.db"]
    }
  }
}
{
  "mcpServers": {
    "appwrite": {
      "command": "uvx",
      "args": ["mcp-server-appwrite"],
      "env": {
        "APPWRITE_PROJECT_ID": "<project-id>",
        "APPWRITE_API_KEY": "<api-key>",
        "APPWRITE_ENDPOINT": "https://cloud.appwrite.io/v1"
      }
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.