Skip to content

Novu MCP Server

Describe a notification flow in plain English and let your AI build, trigger, and debug it against your live Novu environment. 20+ tools, one Bearer token, live in two minutes.

Cover image for Novu MCP Server
Contributors
  • Emil Pearce

    Emil Pearce

Details

Describe a notification flow in plain English and let your AI build, trigger, and debug it against your live Novu environment.

No SDK. No dashboard clicking. No guessing at workflow IDs.

AI prompt describing a multi-channel notification flow being turned into a Novu Workflow that ships across In-App, Email, Push, SMS and Slack

The Novu MCP Server is now generally available.

We first shipped it as a preview last July, then kept adding to it quietly. It now exposes 20+ tools - roughly ten more than launch day - covering subscriber CRUD, bulk triggering, event cancellation, and integration management.

If you've been meaning to connect your AI to Novu, this is the version to try. The model stops generating code from training data and starts reading your actual environment.

Build workflows in plain English

Instead of scaffolding a workflow in the dashboard and wiring each channel step by hand, describe the outcome. The AI reads your environment, picks real providers, and stitches the steps together. Ask it to iterate and it edits the same workflow in place.

"Create a workflow called order-shipped that sends an in-app notification when an order ships, then follows up with an email after 24 hours if the user hasn't seen it."
Novu Workflow built from an AI prompt, fanning out across Email, Push, SMS, Slack and In-App on the free tier's 10k events per month

Debug, inspect, and bulk-operate from chat

Once a workflow is live, keep the assistant in the loop. Because it reads live delivery data and subscriber state, routine investigation, maintenance, and triage stop requiring a second tab:

"Why didn't the order-confirmation notification reach subscriber user_123?"
"Find subscriber user_789 and mute their Slack notifications, but keep email and push active."
"Bulk trigger the re-engagement workflow for these 500 subscribers."
"List my active integrations and tell me which are primary for each channel."

The last two hit tools we shipped in this release. Bulk triggering, event cancellation, integration inspection, and primary-provider management all came online after the original preview.

Connect your tool in two minutes

Copy a Secret Key from dashboard.novu.co/settings/api-keys and point your AI tool at the Novu server. Claude Code is one command:

claude mcp add --transport http novu https://mcp.novu.co/ \
  --header "Authorization: Bearer your-novu-api-key"

Cursor uses Settings > Tools & Integrations. Codex reads ~/.codex/config.toml. Claude Desktop connects through npx mcp-remote (Node.js 18+). EU environments use https://mcp.novu.co/?region=eu. Any other MCP-compatible client works with the same URL and Bearer auth pattern.

Novu MCP authorize dialog - one-time consent to let an AI client act on a Novu workspace

Missing a tool? Request it

The server is a living product. If there's an action you want to drive from your AI client that isn't covered yet, request it on the Novu roadmap and we'll prioritize based on demand.

Available on every plan, cloud and open-source. Explore Novu MCP.