Inngest Model Context Protocol (MCP)

Inngest provides Model Context Protocol (MCP) servers for both Inngest Cloud and the local Dev Server. Connect Claude Code, Codex, Cursor, or another MCP client to inspect and operate Inngest from your coding agent.

Inngest MCP tools match the REST API v2 and Inngest CLI commands.

Choose an MCP server

You can configure both servers in the same MCP client. Use the Dev Server while you build and test locally, then use Cloud MCP to inspect deployed environments and production data.

MCP server	Use it for	Endpoint	Authentication
Inngest Cloud	Deployed apps, functions, events, runs, traces, environments, Insights, sessions, webhooks, and experiments	`https://api.inngest.com/mcp`	Inngest API key
Dev Server	Apps, functions, events, and runs on your local machine, plus embedded Inngest docs	`http://127.0.0.1:8288/mcp`	None

Some Cloud MCP tools change data, including tools that send events, invoke functions, rerun or cancel runs, sync apps, and manage environments or webhooks. Review a tool call before you approve it, especially in production.

Connect to Inngest Cloud

1. Create an API key

Create an Inngest API key in the Cloud dashboard, then make it available to your MCP client:

export INNGEST_API_KEY=sk-inn-api-...

Cloud MCP accepts API keys, not signing keys. Keep the key out of source control and use the narrowest access that your work needs.

2. Add Cloud MCP to your client

claude mcp add --transport http inngest-cloud https://api.inngest.com/mcp \
  --header "Authorization: Bearer $INNGEST_API_KEY"

You can also open the Cloud MCP setup page to copy client configuration and see the live tool list.

3. Try Cloud MCP

Ask your coding agent to complete a task such as:

List my Inngest environments, then show the apps in production.

Find recent failed runs for my billing app and explain the first failed step.

Show the available Insights tables, then query event volume for the past 24 hours.

Connect to the Dev Server

1. Start the Dev Server

The local MCP endpoint starts with the Inngest Dev Server:

inngest dev

The default endpoint is http://127.0.0.1:8288/mcp.

2. Add Dev Server MCP to your client

claude mcp add --transport http inngest-dev http://127.0.0.1:8288/mcp

The Dev Server dashboard also has an MCP setup page with client configuration and the live tool list.

3. Try Dev Server MCP

List my local apps, then list the functions in the checkout app.

Send an app/order.created event and inspect every run it triggers.

Inspect the trace for the latest failed run and explain the error.

Search the Inngest docs for rate limiting examples.

Available MCP tools

MCP clients receive the live tool list and each tool's input schema when they connect. The tables below summarize the current tools. Because eligible REST API v2 endpoints become MCP tools automatically, your client's tool list is the source of truth if it differs from this page.

Tools available in Cloud and the Dev Server

Tool	What it does
`cancel_run`	Cancel an in-progress function run.
`get_app`	Get one app, including sync metadata and function count.
`get_apps`	List active or archived apps.
`get_event_runs`	List the function runs triggered by an event.
`get_function`	Get one function's configuration and status.
`get_run`	Get the summary and optional output for one run.
`get_run_trace`	Get the trace tree and optional span output for one run.
`health`	Check the API service health.
`invoke_function`	Invoke a function and return its run details.
`list_function_runs`	List runs for one function.
`list_functions`	List the functions in one app.
`list_runs`	List runs, with optional app, function, status, and time filters.
`rerun`	Rerun a function from the start or from a selected step.
`send_event`	Send an event and return its event ID.

Cloud-only tools

Tool	What it does
`create_env`	Create a custom environment.
`create_score`	Add scores to a run or its steps.
`create_webhook`	Create an incoming webhook.
`fetch_account`	Get the authenticated account.
`fetch_account_event_keys`	List account event keys, optionally for one environment.
`fetch_account_signing_keys`	List account signing keys, optionally for one environment.
`get_experiment`	Get run counts and score aggregates for an experiment.
`list_envs`	List custom environments.
`list_experiments`	List observed experiments.
`list_insights_event_schemas`	List event schemas observed by Insights.
`list_insights_tables`	List tables available to Insights queries.
`list_session_keys`	List session keys observed in an environment.
`list_session_runs`	List runs for one session.
`list_sessions`	List session IDs for one session key.
`list_webhooks`	List incoming webhooks.
`patch_env`	Archive or unarchive an environment.
`query_insights`	Run an Insights SQL query.
`query_insights_prompt`	Turn a natural-language prompt into an Insights SQL query.
`sync_app`	Sync an app from its Inngest endpoint URL.

Dev Server-only tools

Tool	What it does
`grep_docs`	Search the docs embedded in the Dev Server.
`list_docs`	List embedded documentation categories and counts.
`read_doc`	Read one embedded documentation file.

For exact parameters and response shapes, inspect the schema shown by your MCP client or use the REST API v2 reference.

Target a Cloud environment

Cloud tools accept an optional env argument. Your agent sends it when it calls a tool; it is not part of the MCP server setup. With account-scoped credentials, omit env to use the production environment or pass an environment slug to select another environment. An environment-scoped API key can only access its assigned environment.

Be explicit in prompts that might affect data:

In the staging environment, send an app/order.created event with orderId test-123.

Common workflows

Inspect a failed run

Use list_runs or list_function_runs with a failed status filter.
Use get_run to inspect the run summary and output.
Use get_run_trace to find the failed step and its error.

Test an event-driven workflow

Use get_apps and list_functions to confirm the app and its triggers.
Use send_event with a test payload.
Use get_event_runs with the returned event ID.
Use get_run and get_run_trace to inspect each run.

Find implementation guidance locally

Use grep_docs in the Dev Server to find a term or API name.
Use read_doc with a matching path to read the full source.
Apply the guidance, send a test event, and inspect the resulting run.

Troubleshooting

Cloud MCP returns 401 Unauthorized

Confirm the client sends Authorization: Bearer $INNGEST_API_KEY.
Use an Inngest API key that starts with sk-inn-api-; signing keys are not supported.
Restart the MCP client after changing its environment variables.

The Dev Server MCP endpoint is not found

Confirm inngest dev is running.
Confirm the client uses http://127.0.0.1:8288/mcp, or update the port if you changed it.
Restart the client after changing its MCP configuration.

Functions are not listed

Call get_apps first and pass the returned app ID to list_functions.
Confirm the app has synced to the selected Cloud environment or local Dev Server.
Check app and Dev Server logs for registration errors.

Runs or events appear to be missing

Confirm the Cloud tool call targeted the expected env.
Check that the event name matches the function trigger.
Allow a moment for event and run data to become available, then retry the read tool.

Resources

AI Development Tools

Choose among Inngest MCP, agent plugins and skills, CLI workflows, and LLM-ready docs.

Agent Plugins and Skills

Install current Inngest guidance for Claude Code, Codex, Cursor, Windsurf, and other agents.

API Keys

Create and manage API keys for Cloud MCP and the REST API.

Local Development

Run Inngest functions and the Dev Server MCP endpoint on your machine.

REST API v2 Reference

See the endpoints and schemas that power generated MCP tools.

Model Context Protocol

Learn about MCP transports, tools, and client capabilities.