Novu MCP Server已验证已精选

What is the Novu MCP Server?

Novu is the open-source communication infrastructure between software and the people it serves. The Novu MCP Server is the official, fully managed MCP endpoint for it. Point any MCP client at https://mcp.novu.co/ and your agent can trigger notification workflows, manage the people who receive them, and create agents that hold real two-way conversations with users on the chat channels they already use.

MCP connects agents to tools. A2A connects agents to each other. ACI, Agent Communication Infrastructure, connects agents to people. ACI is the layer that lets an agent hold a real, two-way conversation with the humans it works for, across the channels those humans already use. Novu is that layer, and this MCP server is how your agent reaches it.

Two directions in one server:

• Software to people. Trigger multi-channel notification workflows (email, SMS, push, in-app, chat), inspect delivery, and tune per-subscriber preferences.
• Agents with people. Create a Novu agent, connect it to Slack, Microsoft Teams, WhatsApp, Telegram, or email, and inspect the conversation threads it holds.

Novu never runs your agent's brain. The reasoning stays yours, in your own code or on a model platform you bring. Novu owns the delivery rails: identity resolution, OAuth and credential management, conversation threading, and per-channel content formatting. We never run your brain. That is the whole point.

How to use the Novu MCP Server

Nothing to host. Add the remote server URL for your region and let the client run the sign-in flow.

Region	Endpoint
US	https://mcp.novu.co/
EU	https://eu.mcp.novu.co/

OAuth (recommended). Add the URL with no header. On first connection the client opens the Novu sign-in and consent screen, you pick an organization, and the tools appear. Works in any client with remote OAuth support: Claude, Cursor, ChatGPT, Windsurf, and others.

{
  "mcpServers": {
    "novu": {
      "url": "https://mcp.novu.co/"
    }
  }
}

API key (stdio clients, self-hosted Novu). Use the mcp-remote proxy with a bearer token from the Novu dashboard. Presenting a key keeps the client from launching the OAuth flow.

{
  "mcpServers": {
    "novu": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.novu.co/",
        "--header",
        "Authorization:Bearer your-novu-api-key"
      ]
    }
  }
}

Run whoami first to confirm the credential and the active region.

Key features

• Agents. create_agent, get_agents, get_agent, update_agent, and connect_agent, which returns the CLI playbook for wiring a channel to an existing agent.
• Conversations. get_conversations lists agent threads; get_conversation_activities replays a timeline of messages, approvals, and MCP connections as a compact debug digest.
• Notifications. get_notifications and get_notification fetch events with full execution logs and delivery status, filtered by channel, workflow, subscriber, or date.
• Subscribers and preferences. find_subscribers searches by email, name, phone, or ID. get_subscriber_preferences and update_subscriber_preferences read and set channel preferences globally or per workflow.
• Workflows. get_workflows, get_workflow, and trigger_workflow list, inspect, and fire notification workflows with a custom payload.
• Environments and integrations. get_environments lists environments and their configuration; get_integrations lists provider integrations across channels. OAuth sessions can target any environment with an optional environmentId.
• Hosted and regional. Dedicated US and EU deployments, Streamable HTTP transport, OAuth or API key, and an optional environmentId on every tool.

Open source, and yours to build on

Novu is open source, and so is this server. Nothing here is a black box you rent.

• The MCP server is public. Read it, fork it, run it yourself. Point it at a self-hosted Novu API with NOVU_API_URL and it works the same way.
• Novu itself is open source, with roughly 40,000 stars and four years of notification infrastructure behind it. Self-host the whole stack if you want to.
• The agent is yours. Start on a managed agent for speed, then swap in your own code and your own models without changing a channel, a conversation, or a line of delivery logic. Same rails the whole way up.
• Bring your own tools. An agent built on Novu can call any MCP server you give it. Novu does not curate your tool list or sit between your agent and its reasoning.
• No lock-in by design. Own the rails, never the business logic. Your agent keeps working if you take it somewhere else.

Use cases

• Give your agent a voice. Create an agent from your MCP client, connect it to Slack, Microsoft Teams, WhatsApp, Telegram, or email, and let it talk with users in one thread that follows them across channels.
• Ship notifications from the editor. Ask your coding agent to build and trigger a workflow instead of hand-writing the API calls.
• Debug a delivery. "Why did this user not get the invoice email?" resolves through find_subscribers, get_notifications, and the execution logs, without opening the dashboard.
• Fix preferences on request. Read and update a subscriber's channel preferences during a support conversation.
• Audit what an agent did. Replay a conversation timeline, including approvals and tool connections, when reviewing an agent's behavior.