Novu MCP

MCP开发工具

提供方 novuhq · 包名 mcp-remote

开发工具 HTTP · 远程 OAuth 授权 社区 / 第三方 ClaudeCursorWindsurfCodex
查看接入方式

Notification and agent communication infrastructure for AI agents and coding tools. Trigger multi-channel notification workflows (email, SMS, push, in-app, chat), manage subscribers and preferences, and create, connect,

一句话选型结论

按资料字段整理

Novu MCP 属于开发工具类 MCP 服务器,HTTP · 远程,OAuth 授权,可直接接入 Claude、Cursor、Windsurf 等,有可直接复制的远程端点配置。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类开发工具 传输方式HTTP · 远程 鉴权OAuth 授权 部署方式远程部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

开发工具
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

notifications ai agents slack whatsapp telegram email sms push

支持客户端

适用场景

notificationsai agentsslack

安装与配置

HTTP · 远程 OAuth 授权
连远程 HTTPS 端点,通常为 Streamable HTTP
npx mcp-remote https://mcp.novu.co/ --header Authorization:Bearer your-novu-api-key

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    确认你的客户端支持远程端点,并拿到服务地址。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
代码与仓库操作

在对话里直接查代码、提 issue、走 PR,省掉来回切工具。

本地命令与脚本

把构建、测试、格式化这类重复命令交给模型执行。

接口联调与测试

让模型调你的接口、跑一遍用例,快速定位问题。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude、Cursor、Windsurf,换客户端不用重新研究配置。

先想清楚的地方

  • 远程端点依赖网络与服务方可用性,注意密钥与调用额度。
  • 使用前要准备好OAuth 授权对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在开发工具场景里让模型直接调用外部能力的人。
  • 已经在用 Claude、Cursor 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Novu MCP当前 未标注 HTTP · 远程 远程部署 有 未标注
Git 838e2ec1 12 stdio · 本地进程 本地部署 有 2026-05-17
Markitdown MCP 2c653a5f 1 stdio · 本地进程 本地部署 有 2026-05-17
JavaGuide 未标注 stdio · 本地进程 本地部署 有 2026-04-11
awesome-claude-skills 未标注 stdio · 本地进程 本地部署 有 2026-04-26
Context7 831acf40 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

开发工具
字段来自项目仓库与公开索引,中文说明由本站标注
提供方novuhq上游标注的维护方 novuhq
分类开发工具本站按上游分类展示
连接方式HTTP · 远程连远程 HTTPS 端点,通常为 Streamable HTTP
鉴权方式OAuth 授权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时mcp-remote · node本地安装时用到的包标识与运行时
部署类型远程部署上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

13.3 KB
来自项目仓库与上游目录的原文,未做删改

Novu MCP Server

The Model Context Protocol (MCP) server for Novu — bring AI assistants directly into your notification workflows. Manage subscribers, trigger workflows, inspect events, and tune preferences from any MCP-compatible client.

Visit our main GitHub Repository »

✨ Features

A single MCP server that unlocks your entire Novu workspace for AI agents:

  • Agents — create, list, inspect, update Novu agents, and hand off channel connect to the Novu CLI playbook
  • Conversations — list agent threads and inspect activity timelines (messages, approvals, MCP connections)
  • Notifications — fetch and filter events with full execution logs and delivery status
  • Subscribers — search and manage recipients by email, phone, name, or ID
  • Workflows — list, inspect, create, update, and trigger notification workflows
  • Preferences — read and update subscriber channel preferences (email, SMS, in-app, push, chat)
  • Environments — view environments and their configuration
  • Integrations — manage provider integrations across channels
  • Auth & Identity — whoami verifies your credential (OAuth or API key) and reports the active region

🚀 Quick Start

You don't need to host anything — the server is fully managed. Pick the endpoint
for your Novu Cloud region and point your MCP client at it:

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

Each host is a dedicated deployment pinned to its region — there is no ?region=
query param anymore. (For backward compatibility, a ?region= that doesn't match
the host's region returns a 400 pointing you at the correct endpoint.)

Authentication

The server supports two ways to authenticate, and both work identically on either
regional endpoint:

1. OAuth (recommended) — No API key to copy/paste. When your MCP client first
connects, the server responds with a 401 and an OAuth discovery document
(/.well-known/oauth-protected-resource) that points the client at Novu's
authorization server (Clerk). Your client opens the Novu sign-in + consent screen,
you pick an organization, and the client receives an access token automatically.

Any MCP client that supports remote OAuth (Cursor, Claude, ChatGPT, Windsurf, …)
handles this flow for you — just add the server URL with no header.

> Note: the client must request the user:org:read scope (advertised in the
> discovery document) so the Novu API can resolve your organization. If your Novu
> account belongs to multiple organizations, you'll be asked to select one during
> consent.

2. API key — Provide your key from the Novu Dashboard as a bearer token:```text
Authorization: Bearer <your-novu-api-key>


When you present an API key, the server treats the session as API-key mode and
will **not** trigger the OAuth sign-in flow — even on the hosted endpoints. The
key is bound to a single environment (and thus region), so no extra configuration
is needed; just connect to the endpoint for the region your account lives in.

&gt; **Self-hosted Novu?** OAuth is only available for **Novu Cloud** (US/EU) — the
&gt; flow runs against Novu Cloud&#x27;s authorization server, which a self-hosted
&gt; deployment has no access to. Self-hosted deployments **always** authenticate
&gt; with an API key. See Deploying your own instance
&gt; and Local Development.

## 🎯 Environments

How requests map to a Novu environment depends on how you authenticate:

- **API key** — the key itself is bound to a single environment; requests always
  run against that environment.
- **OAuth** — the token is bound to your **organization**, and the Novu API
  defaults to the **Development** environment.

For OAuth sessions, every tool accepts an optional `environmentId` parameter to
target a specific environment (forwarded to the Novu API as the
`Novu-Environment-Id` header). Call `get_environments` first to list your
environments, then pass the `_id` of the one you want — for example, to inspect
Production notifications. The Novu API validates that the environment belongs
to your organization. With an API key the parameter is ignored — the key
already pins the environment.

**Local / self-hosted API** — to point this MCP server at a Novu API running
elsewhere (for example a self-hosted instance on `http://localhost:3000`), set
`NOVU_API_URL` in `.dev.vars` and run the server locally (see
Local Development). This replaces the old `?region=local`
query param. Self-hosted always uses an API key — OAuth is Novu Cloud only.

## 🛠️ Usage

The server speaks the Streamable HTTP MCP transport at `https://mcp.novu.co/`
(US) and `https://eu.mcp.novu.co/` (EU).

### Cursor, Windsurf, Claude &amp; other OAuth-capable clients

Any client that supports remote MCP servers with OAuth can connect with **no header** —
the client runs the sign-in flow for you:

- **URL (US):** `https://mcp.novu.co/`
- **URL (EU):** `https://eu.mcp.novu.co/`

On first connection the client opens the Novu sign-in + consent screen. Approve it,
select your organization, and the tools appear automatically.

### API key (mcp-remote / stdio clients, self-hosted Novu)

For clients that only support stdio transports, if you prefer a static API key,
or if you run a **self-hosted Novu** instance (where OAuth is not available),
use the `mcp-remote` proxy with an
`Authorization` header. Presenting an API key keeps the client from launching the
OAuth flow:```json
{
  &quot;mcpServers&quot;: {
    &quot;novu&quot;: {
      &quot;command&quot;: &quot;npx&quot;,
      &quot;args&quot;: [
        &quot;mcp-remote&quot;,
        &quot;https://mcp.novu.co/&quot;,
        &quot;--header&quot;,
        &quot;Authorization:Bearer your-novu-api-key&quot;
      ]
    }
  }
}

For the EU region, swap the URL for https://eu.mcp.novu.co/.

📦 Available Tools

Tool Description
whoami Show who is authenticated (verifies the credential against the Novu API) and the active region
create_agent Create an agent (defaults to managed demo Claude; no API key needed)
connect_agent Return CLI playbook instructions to connect a channel to an existing agent
get_agents List agents with cursor pagination
get_agent Retrieve a single agent by identifier
update_agent Update an agent's name, status, bridge URL, or behavior
get_conversations List agent conversations with optional filters (agent, subscriber, status, provider)
get_conversation_activities Inspect a conversation timeline (compact debug digest; verbose for raw JSON)
get_environments List all environments with their details and API keys
get_notifications Fetch events with filtering by channel, template, subscriber, date, and more
get_notification Get a specific notification with detailed execution logs
find_subscribers Search subscribers by email, name, phone, or ID
get_subscriber_preferences Get a subscriber's preferences across all channels and workflows
update_subscriber_preferences Update a subscriber's channel preferences globally or per workflow
get_workflows List all workflows with their basic information
get_workflow Get a workflow's full definition, steps, and payload schema
trigger_workflow Trigger a workflow for a subscriber with a custom payload
get_integrations List configured provider integrations across channels

💻 Local Development

Prerequisites: Node.js 20+ and pnpm.```bash

Clone and install

git clone https://github.com/novuhq/novu-mcp-server.git
cd novu-mcp-server
pnpm install

Start the local worker

pnpm dev


The server runs at http://localhost:8787. Point your MCP client at it the same way you would the hosted version:```json
{
  &quot;mcpServers&quot;: {
    &quot;novu&quot;: {
      &quot;command&quot;: &quot;npx&quot;,
      &quot;args&quot;: [
        &quot;mcp-remote&quot;,
        &quot;http://localhost:8787/&quot;,
        &quot;--header&quot;,
        &quot;Authorization:Bearer your-novu-api-key&quot;
      ]
    }
  }
}

Configuration is read from .dev.vars (gitignored) — copy
.dev.vars.example to get started. The key variables are:

  • NOVU_API_URL — the Novu API this server proxies to (e.g. http://localhost:3000
    for a self-hosted API, or https://api.novu.co / https://eu.api.novu.co for cloud).
  • NOVU_REGION — the display label surfaced by whoami.
  • CLERK_OAUTH_ISSUER — the Clerk authorization server for OAuth. Leave empty to
    disable OAuth entirely and run API-key-only (the self-hosted mode).

For local development against a self-hosted Novu API on http://localhost:3000,
set NOVU_API_URL=&quot;http://localhost:3000&quot; in .dev.vars and use your instance's
API key (OAuth is Novu Cloud only):```json
{
"mcpServers": {
"novu-local": {
"command": "npx",
"args": [
"mcp-remote",
"http://localhost:8787/",
"--header",
"Authorization:Bearer your-local-novu-api-key"
]
}
}
}


### OAuth in local development

To exercise OAuth locally, set `CLERK_OAUTH_ISSUER` in `.dev.vars` to a Clerk
authorization server your Novu API trusts (e.g. `https://clerk.dashboard.novu.co`
for US). The MCP endpoint origin is derived from the request URL, so run the dev
server and point your MCP client at the same URL (e.g. `http://localhost:8787/`).
RFC 9728 requires the PRM `resource` field to exactly match the MCP endpoint URL;
connecting via a different host/port than the server is bound to causes clients
like Cursor to discard the metadata and register without the `user:org:read` scope.

When `CLERK_OAUTH_ISSUER` is empty, the OAuth discovery endpoints return `404` and
`401` responses omit the OAuth metadata, so clients fall back to API-key auth.

### Deploying your own instance

The server is a standard Cloudflare Worker. `wrangler.jsonc` is organized so the
**top-level config is local-dev-only** (no `routes`, so `wrangler dev` serves on
localhost and OAuth discovery advertises the localhost origin), while real
deployments live under named environments:

- `pnpm deploy` → `--env us` (binds `mcp.novu.co`, `NOVU_API_URL=https://api.novu.co`)
- `pnpm deploy:eu` → `--env eu` (binds `eu.mcp.novu.co`, `NOVU_API_URL=https://eu.api.novu.co`)

To deploy your own instance, fork the repo and add an environment under `env`
(or edit an existing one) with your own `routes`, `NOVU_API_URL`, and
`NOVU_REGION`, then deploy it with `wrangler deploy --env `. A self-deployed
instance works out of the box with API-key authentication against whatever
`NOVU_API_URL` points at — including a self-hosted Novu API. OAuth on your own
deployment requires setting the `CLERK_OAUTH_ISSUER` secret
(`wrangler secret put CLERK_OAUTH_ISSUER --env `) to an authorization
server that your Novu API trusts; leave it unset for API-key-only.

### Scripts

- `pnpm dev` — Run the worker locally via Wrangler (top-level, route-free config)
- `pnpm deploy` — Deploy the US worker (`mcp.novu.co`, `--env us`)
- `pnpm deploy:eu` — Deploy the EU worker (`eu.mcp.novu.co`, `--env eu`)
- `pnpm type-check` — Run TypeScript type checking
- `pnpm lint:fix` — Fix linter issues with Biome
- `pnpm format` — Format the codebase with Biome

### Project structure```text
src/
├── index.ts            # Worker entry — auth extraction and routing
├── oauth.ts            # OAuth discovery, 401 bootstrap, initialize-time probe
├── server/NovuMCP.ts   # Durable Object hosting the MCP agent
├── tools/              # One file per tool group (workflows, subscribers, …)
├── utils/              # API client, validation, tool factory
└── types/              # Shared TypeScript types

Add new tools by creating a register*Tools function under src/tools/ and wiring it in src/server/NovuMCP.ts.

🔒 Security

  • The server is a pure OAuth pass-through: it does not mint, exchange, or
    re-sign tokens. It never validates tokens itself — it advertises Novu's Clerk
    authorization server and forwards the caller's Authorization header verbatim
    to the Novu API, which validates it and resolves the org/permissions.
  • OAuth access tokens (Clerk opaque oat_… tokens) are short-lived and revocable
    from the Novu side, so they are far safer than a long-lived API key.
  • Whether OAuth token or legacy API key, the credential is scoped to your MCP
    session: it is handed to the session's Durable Object via the runtime's props
    channel — never placed in URLs, where it would leak into request logs — and is
    discarded with the session. The server holds no ambient credentials.
  • Never commit API keys or issuer config. Use .dev.vars for local values
    (already gitignored).
  • Treat your Novu API key like a password — rotate it from the dashboard if you
    suspect it has been exposed.

🤝 Contributing

  1. Make Changesbash git checkout -b feat/your-change pnpm dev # Test locally pnpm type-check # Verify types git commit -m &quot;feat: your change&quot; git push origin feat/your-change

  2. Open a Pull Request
    - Use a descriptive title with feat:, fix:, docs:, or chore: prefix
    - Include a short description of the change and, where relevant, a sample tool call

Guidelines:

  • Keep tool descriptions concise — they are surfaced verbatim to LLMs
  • Validate inputs with Zod schemas in src/utils/
  • Prefer the ToolFactory helpers for standard CRUD endpoints
  • Something missing? Open a GitHub issue

Need help? Email us at support@novu.co or join the Discord.


Thank you for contributing! 🙏

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
Novu MCP 怎么安装?

在客户端按下面的安装命令接入:npx mcp-remote https://mcp.novu.co/ --header Authorization:Bearer your-novu-api-key。对应的包名是 mcp-remote。装完在客户端配置里引用同一个包或端点。

Novu MCP 怎么在 Claude、Cursor、Windsurf 里配置?

它的传输方式是HTTP · 远程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Novu MCP 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Novu MCP 需要 API Key 吗?

资料标注需要OAuth 授权认证,使用前准备好对应凭据,并按最小权限配置。

Novu MCP 支持哪些客户端?

资料标注支持 Claude、Cursor、Windsurf、Codex、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Novu MCP 能提供哪些能力?

资料显示能力标签包括 notifications、ai agents、slack、whatsapp、telegram、email。具体工具清单以官方文档为准。

Novu MCP 需要什么运行环境?

运行时为 node;属于远程端点,不需要在本地装运行时。

Novu MCP 是本地还是远程?

它是远程端点,连服务地址即可。传输方式为HTTP · 远程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。