Webhooks, MCP, Ask Nodus and email notifications
Four ways for Nodus to reach you and your tools.
- Webhooks. Create as many
WebhookEndpointobjects as you need, each with its own URL, event types and projects. Deliveries are signed with the Standard Webhooks scheme, retried with backoff for 3 days, and kept in a 7-day log you can replay from. Rotate a signing secret without a gap: both secrets sign for up to 7 days. - MCP.
nodus mcpand the hosted server at/mcpgive Claude Code, Cursor and Codex generic tools over every resource. Creating anything returns a dry-run first and needs your confirmation.nodus mcp install CLIENTwrites the client’s configuration. - Ask Nodus (Beta). An assistant in the console that explains failures and costs, drafts manifests that have passed a server dry-run, and cites the docs. It cannot change anything until you confirm.
- Email notifications. Low balance, Budget thresholds, stops, pool events and invites go to the right people once per condition, and you can switch off the optional ones.
See Webhooks, MCP, Ask Nodus and Notifications.