inngest-cloud

From README

Inngest Cloud Use the connected Inngest Cloud MCP server at https://api.inngest.com/mcp. Read the tools and input schemas exposed by the current connection before constructing calls. Tool names below omit host-specific prefixes. Connection and target Use the host's OAuth sign-in or reconnect flow. Do not request tokens or API keys in chat. A plugin connection does not authenticate a separate CLI. Resolve the account with fetchaccount when account context is missing. Use listenvs and the user's task to resolve the environment. Carry the selected env through environment-specific calls; do not infer production from an omitted value or switch environments after an access error. Use getapps and listfunctions to discover identifiers. Don't ask the user for an ID the tools can find. Ask when multiple accounts, environments, apps, or functions fit the request. A 401 needs reconnection; a scope or permission error needs the appropriate grant. Neither means that a resource is absent.