Inngest

Docs › Introduction › Local development › AI and MCP

Overview

Give your coding agent current Inngest knowledge and direct access to your functions and runs.

Plugins and skills teach your agent how to write Inngest code. MCP and the CLI let it run that code, send test events, and inspect runs, so it can build and debug in one loop.

Inngest MCP

Connect Claude Code, Codex, Cursor, and other MCP clients to Inngest Cloud or your local Dev Server to inspect and operate functions and runs.

inngest-kb.zunoywork.com
Agent plugins and skills

Install the published Claude Code plugin for coding skills and Cloud MCP, or use portable skills in other agents. The Codex plugin is coming soon.

inngest-kb.zunoywork.com
CLI for coding agents

Use the Inngest CLI from an agent session to start the Dev Server, trigger events, inspect runs, and keep local debugging grounded in real execution.

inngest-kb.zunoywork.com
LLM Docs

Give AI tools compact or full-text documentation context with llms.txt and llms-full.txt.

/#llm-docs

  1. Install the plugin or skills

    Install the published Claude Code plugin, or use portable skills in Codex and other agents while the Codex plugin is in review. See Agent plugins and skills.

  2. Connect Inngest MCP

    Sign in to the Claude plugin's bundled Cloud connection, or configure standalone Cloud MCP in other clients. Add Dev Server MCP for local work. See Inngest MCP.

  3. Build against the Dev Server

    Start the Dev Server, then ask your agent to send a test event and inspect the run it starts.

LLM Docs

An LLM-friendly version of the Inngest docs is available in two formats:

Next steps

Local development

Run the Dev Server and test your functions on your machine.

inngest-kb.zunoywork.com
Get started

Build your first durable function in TypeScript, Python, or Go.

inngest-kb.zunoywork.com

Updated Nov 10, 2026

Powered byZunoy