mcpbeat Sign in

Inngest MCP by usefulapi MCP Server

answering

Inngest MCP by usefulapi is answering right now. Last checked 8 min ago. It exposes 11 tools. Last commit 10 Oct 2026.

Trace events to function runs to the failing step, and bulk-cancel runs.

Uptime history 13 days of history
13 days agonow
100.0%
Uptime 24h
92 of 92 checks
11
Tools
read from the server
82 ms
Response time
average over 24h
0
Stars
last commit 10 Oct 2026

What changed 7

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 30 September 2026. No other catalogue keeps this.

9 Oct a tool changed version4 times that day
8 Oct a tool changed version
7 Oct a tool changed version
30 Sep a tool changed version
and 3 more, back to 30 September 2026

Nothing serious here today

Today is the operative word: we check Inngest MCP by usefulapi every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

run in your terminal
claude mcp add inngest --transport http https://inngest.usefulapi.io/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "inngest": {
      "url": "https://inngest.usefulapi.io/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.inngest]
url = "https://inngest.usefulapi.io/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "inngest": {
      "url": "https://inngest.usefulapi.io/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "inngest": {
      "url": "https://inngest.usefulapi.io/mcp"
    }
  }
}

Available tools 11

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

inngest
inngest_create_cancellation
Cancel every run of one function that started within a time window, optionally narrowed by an event expression. This STOPS IN-FLIGHT WORK across your production functions — scope the window tightly. Runs already finished are unaffected. Inngest: POST /v1/cancellations.
inngest_delete_cancellation
Delete a bulk-cancellation job so it stops cancelling further runs. Runs it already cancelled stay cancelled. Inngest: DELETE /v1/cancellations/{cancellationId}.
inngest_delete_webhook
Remove a webhook ingress. The external source stops producing events immediately. Inngest: DELETE /v1/webhooks/{webhookId}.
inngest_get_event
Fetch a single event with its name, payload and timestamp. Inngest: GET /v1/events/{eventId}.
inngest_get_run
Fetch a single function run — its status, output and error. Inngest: GET /v1/runs/{runId}.
inngest_get_webhook
Fetch a single webhook ingress with its URL and transform. Inngest: GET /v1/webhooks/{webhookId}.
inngest_list_cancellations
List bulk-cancellation jobs and their progress. Inngest: GET /v1/cancellations.
inngest_list_event_runs
List every function run one event triggered, with each run's status. This is the hop from 'this event arrived' to 'and here is what it did'. Inngest: GET /v1/events/{eventId}/runs.
inngest_list_events
List the events received in the key's environment, newest first. Events are what start functions, so this is where an investigation begins. Inngest: GET /v1/events.
inngest_list_run_jobs
List the individual steps (jobs) of one run, with their status and timing — how you find which step of a durable function failed. Inngest: GET /v1/runs/{runId}/jobs.
inngest_list_webhooks
List the webhook ingresses configured for the environment — the external sources that turn into events. Inngest: GET /v1/webhooks.

Endpoints

URLTransportStateLatencyChecked
https://inngest.usefulapi.io/mcp streamable-http answering 84 ms 8 min ago

Alternatives to Inngest MCP by usefulapi

same job, measured the same way
Depot MCP by usefulapi
by usefulapi

Inspect Depot builds, CI runs, job logs and Actions runners; retry or cancel CI runs.

22 tools answering
Bloomerang MCP by usefulapi
by usefulapi

Search Bloomerang constituents and donations; log interactions, notes and tasks.

20 tools answering
Clockify MCP by usefulapi
by usefulapi

Track time in Clockify: time entries, projects, clients, tags and reports; start, stop and log time.

21 tools answering
Trigger.dev MCP by usefulapi
by usefulapi

Debug background jobs — runs, traces, spans, schedules, queues and deployments.

22 tools answering
Harvest MCP by usefulapi
by usefulapi

Read time entries, projects, clients, tasks and invoices; log and update tracked time.

20 tools answering
Instatus MCP by usefulapi
by usefulapi

Manage status pages: components, incidents and maintenances; set live component status.

14 tools answering
Spike.sh MCP by usefulapi
by usefulapi

Read Spike.sh incidents, on-call, escalations and services; acknowledge, resolve, set priority.

16 tools answering
All Quiet MCP by usefulapi
by usefulapi

Manage incidents and on-call: list/create/update incidents, who is on call, on-call overrides.

11 tools answering

Inngest MCP by usefulapi — questions

Answers built from our own checks of this server.

What can Inngest MCP by usefulapi do?
It exposes 11 tools, read directly from the server on our last check. Among them: inngest_create_cancellation, inngest_delete_cancellation, inngest_delete_webhook, inngest_get_event, inngest_get_run, inngest_get_webhook and 5 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Inngest MCP by usefulapi working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 82 ms. The bar chart above shows every period we have measured.
How do I connect Inngest MCP by usefulapi?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Inngest MCP by usefulapi need an API key?
No. Inngest MCP by usefulapi completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 11 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Inngest MCP by usefulapi?
It answers our handshake in 82 ms on average, which is faster than 89% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Inngest MCP by usefulapi open source?
Yes — it is published under the MIT licence, written in JavaScript, 0 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.