Inngest MCP server
Inngest's official Dev Server MCP: send events, invoke functions, monitor runs, and search the docs against your local Inngest dev server from your agent.
Inngest is a durable execution platform for event-driven functions and workflows — you write functions that react to events or run on a schedule, and Inngest handles queuing, retries, state, and step orchestration. The official Inngest Dev Server MCP is built into the Inngest CLI: when you run `inngest dev`, the local dev server exposes a Streamable HTTP MCP endpoint at http://127.0.0.1:8288/mcp, letting an agent drive your local development loop directly — fire test events, invoke functions, watch runs complete, and look up documentation without leaving the conversation.
The server exposes eight tools across three areas. Event management: send_event triggers functions with a test event and returns the run IDs created, list_functions discovers every registered function with its triggers, and invoke_function executes a function synchronously and returns its result. Execution monitoring: get_run_status returns detailed status and step-by-step trace information for a run, and poll_run_status watches multiple runs until they complete — useful for integration tests. Documentation: grep_docs searches the embedded Inngest docs by pattern, read_doc reads a full doc file, and list_docs browses the available documentation by category. The dev server runs entirely locally, with docs embedded in the CLI binary, so no API key or network connection is required.
Quick install
Copy-paste configs are provided for all 8 supported clients. Pick your client below.
Available tools
| Tool | Description |
|---|---|
| send_event | Send an event to trigger functions and get immediate feedback on which runs were created. |
| list_functions | Discover all registered functions with their names, IDs, and event-trigger information. |
| invoke_function | Directly execute a function and wait for its complete result. |
| get_run_status | Get detailed status and trace information for a specific function run, including step-by-step execution details. |
| poll_run_status | Monitor multiple function runs until they complete — useful for integration testing. |
| grep_docs | Search the embedded Inngest documentation using pattern matching. |
| read_doc | Read the complete content of a specific documentation file. |
| list_docs | Get an overview of all available documentation with a category breakdown. |
What you can do with it
Test functions without writing curl
Ask the agent to fire an event at your local functions: send_event returns the run IDs, then get_run_status and poll_run_status follow each run's steps until completion, so you can verify a workflow end to end while you iterate on the code.
Invoke and inspect a single function
Use list_functions to see what's registered, invoke_function to run one synchronously and get its return value, and grep_docs or read_doc to pull the exact Inngest API reference you need — all inside the assistant.
FAQ
- Is it free?
- Yes. The Dev Server MCP is part of the free, open-source Inngest CLI and runs entirely on your machine with no API key. Inngest Cloud is a separate paid product, but this MCP targets local development.
- Does it support remote/OAuth?
- It is served over Streamable HTTP at http://127.0.0.1:8288/mcp once you run `inngest dev`. There is no OAuth — the endpoint is local and unauthenticated because it controls your local dev server only.