Agent plugins and skills
Teach your coding agent to write current, correct Inngest code.
Inngest provides official plugins and agent skills for AI coding agents like Claude Code, Codex, Cursor, and Windsurf. They give your agent current guidance for building reliable applications with Inngest — from initial setup to advanced flow control and realtime updates.
The Claude Code plugin is available now from Anthropic's directory. It includes coding skills and an Inngest Cloud MCP connection with OAuth. The Codex plugin is coming soon and is currently in review.
To compare skills, MCP, the CLI, and LLM-ready docs, see AI and MCP.
What to install
| AI tool | Recommended install | What it includes |
|---|---|---|
| Claude Code | Inngest Claude Code plugin | Coding skills, Cloud MCP with OAuth, and commands for connection recovery, run debugging, and codebase audits |
| Codex | Coming soon | Plugin in review; portable skills and standalone MCP are available today |
| Cursor, Windsurf, and other agents | Standalone inngest-skills repository | The core skill content in a portable format |
Why use Inngest plugins?
A model's training data can be outdated or incomplete. Inngest plugins give your agent:
- Current APIs: accurate function signatures, configuration options, and best practices.
- Proven patterns: templates for background jobs, scheduled tasks, webhook handlers, and durable AI agents.
- Step-by-step guidance: structured instructions for setup, steps, flow control, and realtime.
- Repository audits: guidance for finding durability gaps in an existing codebase before changing it.
Claude Code plugin
Install in the CLI
Run this in your terminal to install the published plugin from Anthropic's directory:
claude plugin install inngest@anthropic-plugin-directory
Start a new Claude Code session, run /mcp, and select plugin:inngest:inngest-cloud to sign in. Complete OAuth in your browser with the Inngest account and permissions you want Claude to use.
Install in Claude desktop
In Claude's directory, find and add Inngest. Open the plugin's Connectors tab, add the Inngest connector if needed, then connect your Inngest account.
On Team and Enterprise plans, an Owner must add the connector for the organization before members can connect. See Claude's bundled connector guide.
Plugins added through Claude's directory also sync to Claude Code when you sign in with the same Claude account. Use either that synced install or the CLI install above; a separate local install can take precedence over the synced copy.
Try the plugin
Use the Inngest plugin to show my account and environments.
The plugin also includes these Claude Code commands:
| Command | Use it to |
|---|---|
/inngest:connect | Diagnose the connection, recover sign-in, and verify your account and environments |
/inngest:debug-run | Investigate a run by ID and explain the failing step |
/inngest:audit | Find durability gaps in an existing codebase |
If Cloud tools are unavailable in Claude Code, run /inngest:connect and follow its recovery steps. In Claude chat, use the plugin's Connectors tab to sign in.
The plugin already includes Cloud MCP. Avoid adding a second manual Cloud connection. For local development, add the optional Dev Server MCP connection.
Codex plugin (coming soon)
The Inngest Codex plugin is currently in review. Directory installation instructions will be available here once it is published.
In the meantime, use portable skills and standalone Inngest MCP with Codex.
Portable skills
For agents that support skills, install the shared Inngest skills directly:
npx skills add inngest/inngest-skills
For other agents, reference the standalone skills repository directly or clone it to your agent's skills directory. Each skill is self-contained with full documentation in its SKILL.md file.
Core skills
| Skill | Description | What it covers |
|---|---|---|
| inngest-setup | Set up Inngest in a TypeScript project | SDK installation, client config, environment variables, dev server |
| inngest-events | Design and send Inngest events | Event schema, naming conventions, idempotency, fan-out patterns, system events |
| inngest-durable-functions | Create and configure durable functions | Triggers, step execution, memoization, cancellation, error handling, retries |
| inngest-steps | Use step methods to build durable workflows | step.run, step.sleep, step.waitForEvent, loops, parallel execution |
| inngest-flow-control | Configure flow control for functions | Concurrency limits, throttling, rate limiting, debounce, priority, batching |
| inngest-middleware | Create middleware for cross-cutting concerns | Middleware lifecycle, dependency injection, built-in middleware |
| inngest-realtime | Stream workflow updates to users | Realtime channels, subscription tokens, React hooks, SSE consumers |
Additional skills
The Claude Code plugin also includes skills for Cloud operations and working with existing codebases:
| Skill | Description | What it covers |
|---|---|---|
| inngest-brownfield-audit | Audit an existing codebase before changing it | Framework detection, existing Inngest usage, webhooks, cron jobs, queues, long-running routes, polling loops, AI agents, and safe first integration slices |
| inngest-agents | Build durable AI agents with Inngest and AgentKit | Model calls, tool calls, human approval, realtime progress, retries, and provider flow control |
| inngest-v3-v4-migration | Upgrade TypeScript SDK v3 projects to v4 | Trigger syntax, typed events, serve options, step.invoke, native realtime, local dev mode, and mixed v3/v4 cleanup |
| inngest-cloud | Inspect and operate Inngest Cloud through OAuth MCP | Environments, apps, functions, events, runs, traces, and Insights |
| inngest-cli | Run the CLI and local Dev Server | Local development, testing, MCP setup, and self-hosted workflows |
| inngest-api-cli | Operate Inngest through the API CLI | Account, environment, webhook, app sync, function invocation, run, and trace operations |
| inngest-api | Use the REST API v2 directly | OpenAPI discovery, authentication, and raw HTTP requests |
Language support
These plugins and skills are currently focused on TypeScript. Core concepts like events, steps, flow control, and realtime updates apply across all Inngest SDKs, but code examples and setup instructions are TypeScript-specific.
For Python or Go, refer to the Inngest documentation and llms.txt for language-specific guidance.
Combine with Inngest MCP
For the best AI development experience, use agent skills alongside Inngest MCP. Together they provide:
- Skills give your agent knowledge of how to write correct Inngest code
- Dev Server MCP lets your agent test and debug functions running on your machine
- Cloud MCP lets your agent inspect and operate deployed environments, functions, events, and runs
This enables a complete write, test, and debug loop powered by your coding agent.
Resources
The plugins share their core skills with inngest/inngest-skills.