Novu MCP Server for Claude

Overview

Novu MCP is Novu's official remote Model Context Protocol server for connecting AI tools to notification infrastructure. It lets Claude work with subscribers, notification preferences, workflows, triggered events, delivery logs, environments, and integrations through a hosted HTTP endpoint at https://mcp.novu.co/.

The server is useful when Claude needs to inspect or operate notification systems without manually translating every request into direct API calls. A typical session can search subscriber records, inspect workflows, update preferences, trigger a test workflow, or debug failed notifications.

Key Capabilities

• Subscriber management - create, inspect, update, delete, and search subscribers.
• Notification preferences - read and update how subscribers receive notifications.
• Workflow management - create, inspect, update, list, and delete notification workflows.
• Triggering - trigger individual or bulk workflow events.
• Delivery operations - inspect notification records, debug failures, and cancel pending triggered events.
• Integrations - list channel integrations and mark primary integrations.
• Environment awareness - check API key status and list Novu environments.

Tools

Novu documents 23 MCP tools across these areas:

Installation

Claude Code

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

For a user-scoped install:

claude mcp add --scope user --transport http novu https://mcp.novu.co/ \
  --header "Authorization: Bearer YOUR_NOVU_API_KEY"

Use the EU endpoint when your dashboard is eu.dashboard.novu.co:

claude mcp add --transport http novu "https://mcp.novu.co/?region=eu" \
  --header "Authorization: Bearer YOUR_NOVU_API_KEY"

Claude Desktop

Claude Desktop uses mcp-remote for remote MCP servers:

{
  "mcpServers": {
    "novu": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.novu.co/",
        "--header",
        "Authorization: Bearer ${NOVU_API_KEY}"
      ],
      "env": {
        "NOVU_API_KEY": "YOUR_NOVU_API_KEY"
      }
    }
  }
}

Codex

Add the API key to your shell environment:

export NOVU_API_KEY="YOUR_NOVU_API_KEY"

Then configure the remote MCP server:

[mcp_servers.novu]
url = "https://mcp.novu.co/"
bearer_token_env_var = "NOVU_API_KEY"

Use Cases

• Check whether a subscriber exists before triggering a lifecycle notification.
• Inspect workflow definitions before changing message copy or channel routing.
• Debug failed deliveries and compare channel-provider state across email, SMS, push, in-app, or chat.
• Update subscriber notification preferences from a support or operations workflow.
• Send controlled test notifications during release verification.

Safety and Privacy

Novu MCP operates against live notification infrastructure. Treat workflow triggers, bulk sends, subscriber deletion, integration changes, and preference updates as production-impacting actions unless you are connected to a dedicated development environment.

Notification systems often contain direct contact details and behavioral metadata. Keep API keys out of chat, use the right region endpoint, avoid sending sensitive subscriber data unless needed, and review Claude-generated workflow or delivery changes before applying them.

Source Verification Notes

Verified on 2026-06-18:

• Novu's official MCP documentation at https://docs.novu.co/platform/build-with-ai/mcp documents the hosted MCP URL, US and EU region variants, API-key authentication, Claude Code, Claude Desktop, Cursor, and Codex setup paths, plus the available tool groups.
• Claude Code MCP documentation at https://code.claude.com/docs/en/mcp documents the claude mcp add --transport http pattern used above.
• No repoUrl is declared because the earlier resubmission pointed at https://github.com/novuhq/smithery-mcp, which returned 404 during gate review. This entry uses reachable Novu documentation and website sources instead of a placeholder repository URL.