Give AI assistants local access to functions, events, and docs
Visit WebsiteFreemiumVisit Website
What is Inngest MCP?
Inngest's MCP server is built into the Inngest dev server, giving AI assistants local access to functions, events, and docs.
Preview
Key Features
List and inspect registered functionsSend events to trigger functionsInvoke functions synchronouslyGet and poll run statusSearch and read docs offline
Pricing Plans
Pricing checked Jul 31, 2026
Hobby
$0/mo
- 50k executions
- 5 concurrent executions
- 500 MB span data ingested
- 10K scores
- 500k events ingested
- 100k queue depth
- 50 realtime connections
- Basic tracing, metrics, and alerts
Pro
Starting at $99/mo
- 1M+ executions
- 100+ concurrent executions
- 5 GB span data ingested
- 50K scores
- 5M+ events ingested
- 1M+ queue depth
- 1000 realtime connections
- Granular tracing, metrics, alerts + 7 day trace retention
- Increased throughput
Enterprise
Contact us
- Custom executions
- Custom concurrent executions
- Custom span data ingested
- Custom scores
- Custom events ingested
- Custom queue depth
- Custom realtime connections
- Advanced tracing, metrics, alerts + 90 day trace retention
- Dedicated Slack channel
- SAML, RBAC, audit trails
Reviews
Be the first to review Inngest MCP
Your take helps the next buyer. Verified LinkedIn reviewers get a badge.
Write a reviewBest Inngest MCP Alternatives
Top alternatives based on features, pricing, and user needs.
TabnineFreemium
AI code completion for any IDE
LM StudioFree
Run local LLMs with a beautiful interface
LlamaIndexFreemium
Data framework for LLM applications
Sourcegraph CodyFreemium
AI coding assistant with codebase context
OllamaFree
Run open-source LLMs locally with one command
Hugging Face MCPFreemium
Connect to Hugging Face Hub for search, retrieval, and Gradio Spaces
SourcebotFreemium
Understand your entire codebase with AI-powered search and agentic capabilities.
Explore More
Inngest MCP FAQ
How does Inngest MCP help developers debug Inngest functions?
Inngest MCP gives AI assistants local access to functions, events, and docs, allowing them to inspect function definitions, event payloads, and documentation directly from the Inngest dev server. This enables AI assistants to provide context-aware help during debugging without requiring manual lookup.
How does Inngest MCP differ from Sourcegraph Cody?
Inngest MCP is built into the Inngest dev server and provides AI assistants with local access to Inngest-specific functions, events, and documentation. Sourcegraph Cody is a general-purpose code AI assistant that works across repositories and editors, not limited to a single platform like Inngest.
What are the main limitations or trade-offs of using Inngest MCP?
Inngest MCP requires running the Inngest dev server locally, so it is only useful for developers who already use Inngest for background jobs and events. It does not provide access to external codebases or general development tasks beyond the Inngest ecosystem.
How is Inngest MCP priced?
Inngest MCP is available on a free tier, with paid plans that offer more usage and additional features. The pricing model scales with usage, making it accessible for individual developers and teams with higher demands.
What kind of user benefits most from Inngest MCP?
Developers who build and manage background jobs, functions, and event-driven workflows using Inngest benefit most from Inngest MCP. It gives their AI assistants direct access to their Inngest project’s functions, events, and documentation for more efficient development and troubleshooting.
Can Inngest MCP retrieve function documentation?
Yes, Inngest MCP provides AI assistants with local access to documentation associated with your Inngest functions. This allows the AI to answer questions about function usage, parameters, and behavior directly from your project’s docs.
Does Inngest MCP work with any AI assistant that supports MCP?
Yes, Inngest MCP implements the Model Context Protocol (MCP), so it can be used with any AI assistant or client that supports MCP. This includes popular tools like Claude, VS Code extensions, or custom MCP clients.
How does Inngest MCP provide local access to events?
Inngest MCP is built into the Inngest dev server, which processes events locally. The MCP server exposes endpoints that AI assistants can query to retrieve event data, such as event names, payloads, and histories, directly from the local development environment.
Source: inngest.com