Inngest MCP Logo

About Inngest MCP

Inngest MCP connects a coding agent to Inngest, the durable execution platform used to run background jobs, queues, scheduled tasks, and multi-step event-driven workflows. The integration is served by the Inngest Dev Server that developers already run alongside their application, so the agent talks to the same environment being tested rather than to a separate copy of the code. Once connected, the agent can enumerate the functions an app has registered along with the events that trigger them, send test events into the system, invoke a function directly and wait for its result, and read back the resulting run: which steps executed, what each step returned, where a retry happened, and what error ended a failed attempt. Inngest documentation is reachable through the same connection, so concepts like step primitives, concurrency controls, or flow control can be looked up without leaving the session. It is aimed at engineering teams building on Inngest who want an assistant that can close the write, trigger, inspect, fix loop on its own. The practical value is debugging. Instead of a developer copying stack traces out of a dashboard, the agent triggers the workflow, reads the step-level trace, and proposes a change against the function source in the same repository.