inngest-cloud-mcp
Related Servers
Alternatives to inngest-cloud-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceMCP server for Langfuse that lets Claude Code create projects, manage API keys, and query traces without touching the web UI. Designed to work with a self-hosted Langfuse v3 stack running locally via Docker Compose.20MIT
- AlicenseCqualityAmaintenanceMCP server for Langfuse observability. Query traces, debug exceptions, analyze sessions, and manage prompts and datasets for your LLM applications.481,065 PyPI106MIT
- AlicenseAqualityBmaintenanceMCP server exposing Cursor's HTTP APIs for managing Cloud Agents, Team/Org Admin, Analytics, Bugbot, AI Code Tracking, and Fleet with read-only and read-write modes.61MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for Dify Console API that enables managing apps, workflows, knowledge bases, models, plugins, and MCP servers programmatically from Claude Code or any MCP client.5 npm7MIT
- AlicenseBqualityCmaintenanceMCP server for OpenRouter's management API, enabling programmatic control of credits, inference keys, guardrails, and usage analytics from MCP-compatible clients.16121 npmMIT

nahook-mcpofficial
AlicenseAqualityCmaintenanceThe official MCP server for Nahook. Manage webhook endpoints, inspect deliveries and delivery attempts, retry failed deliveries, and list environments — directly from Claude, Cursor, Cline, or any MCP-compatible client.121MIT
TDQS
Scored across 8 tools
Each tool targets a distinct resource and action: listing functions vs events, getting an event vs its runs, getting a run vs cancelling it, and creating vs listing cancellations. Descriptions clearly differentiate the cancellation tools, so an agent can select correctly.
All tool names follow a consistent snake_case verb_noun pattern: list_functions, list_events, get_event, get_event_runs, get_run, cancel_run, create_cancellation, list_cancellations. No deviations or mixed conventions.
Eight tools is well-scoped for an Inngest cloud management server covering functions, events, runs, and cancellations. Each tool earns its place without redundancy.
Core read and cancellation operations are present, but there are notable gaps: no tool to delete or update a bulk cancellation rule after creation, no way to list all runs independent of an event, and no get_function details. These missing lifecycle operations could force agents into dead ends.