Nuntly MCP Server

MCP server for [Nuntly](https://nuntly.com), the developer-first email platform. Exposes tools for sending emails, managing domains, webhooks

Local serverstdioTypeScript

What is the Nuntly MCP MCP server?

Most team communication work still happens through a UI a human drives. Nuntly MCP MCP server moves it into the conversation instead. MCP server for Nuntly, the developer-first email platform. Exposes tools for sending emails, managing domains, webhooks, inboxes, and more.

The tools it exposes

The server publishes 1 tool. What each one is for:

  • Cursor — The Cursor tool exposed by this server

What it needs from you

Configuration is passed through the environment: NUNTLY_API_KEY, NUNTLY_BASE_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

  • Node.js 20 or later (or Bun) - A Nuntly API key from https://nuntly.com/auth/sign-up - An MCP-aware client: Claude Desktop, Claude Code, Cursor, Continue, or any custom integration based on the Model Context Protocol

Getting it running

Installation goes through your MCP client rather than a global install: point it at @nuntly/sdk-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

How it compares

Among the team communication options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Nuntly MCP's toolset — Cursor — is a fair guide to whether it matches your workflow. It is maintained by nuntly; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Nuntly MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
CursorThe Cursor tool exposed by this server.

How to install the Nuntly MCP MCP server

{
  "mcpServers": {
    "nuntly": {
      "command": "npx",
      "args": ["@nuntly/sdk-mcp"],
      "env": {
        "NUNTLY_API_KEY": "your-api-key"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

  • Node.js 20 or later (or Bun) - A Nuntly API key from https://nuntly.com/auth/sign-up - An MCP-aware client: Claude Desktop, Claude Code, Cursor, Continue, or any custom integration based on the Model Context Protocol
VariableDescriptionRequired
NUNTLY_API_KEYCredential the server authenticates with.Yes
NUNTLY_BASE_URLEndpoint or connection string the server talks to.Yes

Example prompts to try

  • Use Nuntly MCP to Cursor.

Frequently asked questions

It connects Nuntly MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 1 tool (Cursor) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Nuntly MCP directly.