Novu MCP server

What the model can do

Novu notification infrastructure: the activity feed of triggered workflows with each step's status, messages sent per channel with delivery state and errors, subscribers by id, workflows with status and when last triggered, and topics with their subscribers; when you ask, can trigger a workflow to named subscribers or a topic, cancel a pending one, create, update or delete subscribers, create or delete topics and add or remove their subscribers, switch a workflow on or off, mark an inbox notification read or archived, and delete a message.

Reads

• novu_list_eventsNovu's activity feed: triggered workflow events, newest first as Novu returns them, with the workflow, the subscriber id, channels, topics…
• novu_get_eventOne triggered Novu event in full: workflow, subscriber id, and for each step its type, status, provider and the latest execution detail…
• novu_list_messagesMessages Novu sent, one per channel per subscriber: channel, status, workflow, subscriber id, provider, when created and delivered…
• novu_list_subscribersFind Novu subscribers by exact email, exact phone, subscriber id or name.
• novu_get_subscriberOne Novu subscriber by subscriber id: locale, timezone, whether an email and phone are on file, online state, topic count, created and updated.
• novu_list_workflowsNovu workflows: identifier (the trigger name), name, status (ACTIVE, INACTIVE, ERROR), tags, step types, and when last triggered…
• novu_list_topicsNovu topics (named groups of subscribers a workflow can be sent to): key, name, created and updated.
• novu_topic_subscribersWho is subscribed to a Novu topic: each subscription's subscriber id and when it was made.

Acts, when you ask

These change something in Novu. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• novu_trigger_workflowTriggers a Novu workflow, which sends its real notifications (email, SMS, push, chat, in-app, whatever its steps are) to the subscribers named…
• novu_cancel_eventCancels a triggered Novu workflow by its transaction id: its pending digests, delays and unsent steps do not go out.
• novu_create_subscriberCreates a Novu subscriber with the subscriber id the product uses for this person, so workflows can reach them; nobody is notified.
• novu_update_subscriberChanges a Novu subscriber's name, email, phone, locale or timezone; only the fields passed change.
• novu_delete_subscriberPermanently deletes a Novu subscriber together with their messages, preferences and topic subscriptions; they stop receiving notifications.
• novu_create_topicCreates a Novu topic (a named group of subscribers to send to).
• novu_add_topic_subscribersSubscribes the named subscribers (at most 100) to a Novu topic, so they receive what is sent to it; the topic is created if it does not exist.
• novu_remove_topic_subscribersUnsubscribes the named subscribers (at most 100) from a Novu topic; they stop receiving what is sent to it.
• novu_delete_topicPermanently deletes a Novu topic and every subscription to it; workflows sent to that topic reach nobody.
• novu_set_workflow_activeSwitches a Novu workflow on (active true) or off (false).
• novu_mark_inbox_notificationMarks one of a subscriber's in-app inbox notifications read, unread, archived or unarchived, as if they had done it…
• novu_delete_messagePermanently deletes one message from Novu by its id (novu_list_messages gives it).

Connect it

First connect Novu on Dashboard → Connections, then add Memtro to your client once. The Novu tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Novu connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Which messages failed to send today, and why?
• › Did the password reset email reach subscriber 4821?
• › When was the weekly digest workflow last triggered?
• › Who is subscribed to the release-notes topic?
• › Switch off the onboarding reminder workflow.

Questions

Is this an official Novu MCP server?

No. It is Memtro's MCP server with Memtro's Novu connector behind it: the connector reads Novu through its API with the credentials you connect on Dashboard → Connections, and Novu publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Novu?

Only when you ask, and only what it has been granted: trigger a workflow, sending its notifications to named subscribers or a topic; cancel a triggered workflow's pending digests and delays; create a subscriber; update a subscriber's name, email, phone, locale or timezone; delete a subscriber with their messages, preferences and topic subscriptions; create a topic; add subscribers to a topic; remove subscribers from a topic; delete a topic; switch a workflow on or off; mark a subscriber's inbox notification read, unread, archived or unarchived; delete a message. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Email, calendar and chat

• AgentMail MCP server
• Gmail MCP server
• Google Calendar MCP server
• Slack MCP server
• Outlook Mail MCP server
• Outlook Calendar MCP server