Inngest MCP by usefulapi
Server Details
Trace events to function runs to the failing step, and bulk-cancel runs.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 0.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- m190/usefulapi-mcp
- GitHub Stars
- 0
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 11 tools
Each tool targets a distinct resource and action: event retrieval vs. event listing vs. event-run listing, run retrieval vs. run-job listing, and cancellation create/delete/list are clearly separated. The webhook tools (get/list/delete) also have unambiguous boundaries. No overlapping purposes that would cause misselection.
Every tool follows the identical `inngest_verb_noun` snake_case pattern: create_cancellation, delete_webhook, get_event, list_events, etc. The prefix is used consistently across all 11 tools. There are no mixed conventions or vague verbs.
11 tools is within the well-scoped 3–15 range, and each tool covers a distinct operation for Inngest events, runs, cancellations, or webhooks. No tool feels redundant or out of place for the surface presented.
The surface is read-heavy and misses critical Inngest operations: there is no way to send/create an event (the primary trigger for functions), no create/update webhook, and no list/get functions. While cancellation and webhook deletion are covered, these gaps will block common agent workflows like triggering or configuring Inngest resources.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Catch AI agent loops: halt runs that repeat the same failing step or tool call.
You cancelled the run — did the work actually stop?
Triage failing GitHub Actions jobs and see what self-heal repaired, in natural language.
Read-only triage for n8n, MCP, webhook, and AI agent workflow production failures.
Related MCP Servers
- AlicenseAqualityBmaintenanceEnables diagnosing long AI-agent traces by identifying the most likely root-cause steps, so users can quickly find where an agent run went wrong.1MIT
- AlicenseNot gradedqualityAmaintenanceFind the step that caused an AI agent’s failure. Ask your assistant why a run failed, see the evidence, and check whether a suggested fix works.16Apache 2.0
- FlicenseNot gradedqualityBmaintenanceEnables automated analysis of test suite traces to identify timing races and state pollution, helping detect flaky test non-determinism in CI/CD workflows such as Datadog CI or Trunk.8-
- FlicenseAqualityBmaintenanceEnables CI/CD failure triage for GitHub Actions by inspecting failed runs, classifying root causes with LLM assistance, retrieving relevant runbook guidance, estimating flakiness, and either preparing dry-run fix PRs or publishing structured diagnoses to Discord for human review.2-
Glama MCP Gateway
Add one secure layer between your agents and this server.