Skip to main content
hc
Submit
mcpSource-backedReview first Safety ✓ Privacy ✓

Courier MCP Server for Claude

Manage Courier notifications from Claude — send messages and templates, manage user profiles and preferences, configure notification routing, handle automations and journeys, and manage subscriber lists — with the official Courier remote MCP server.

by Courier·added 2026-06-18·
Claude CodeCursorClaude Desktop
HarnessClaude CodeCursorClaude Desktop
Review first — review before installing

Open the source and read safety notes before installing.

Safety notes

  • The server is hosted by Courier and authenticated via API key — it can send real notifications to real users and modify account data.
  • With 109 tools covering sends, user data, and automations, the blast radius is significant — scope your API key to the minimum required permissions and test in a Courier sandbox environment first.
  • Bulk operations and automation invocations are available — review Claude's proposed actions before executing in production.

Privacy notes

  • User profile data, notification content, recipient identifiers, and audience lists are sent to Courier's servers when executing tools.
  • Courier API keys are secrets — store them in your environment or MCP client config headers, never in repositories.

Prerequisites

  • A Courier account and an API key from app.courier.com/settings/api-keys.
  • An MCP client such as Claude Code or Claude Desktop.

Schema details

Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
5 minutes
Difficulty
beginner
Tool listing metadata
Full copyable content
{
  "mcpServers": {
    "courier": {
      "type": "http",
      "url": "https://mcp.courier.com",
      "headers": {
        "api_key": "YOUR_COURIER_API_KEY"
      }
    }
  }
}

About this resource

Overview

The Courier MCP Server is the official Model Context Protocol server from Courier. It exposes the full Courier notification platform to Claude — sending messages, managing user profiles and preferences, configuring routing and brands, invoking automations and journeys, and handling subscriber lists — through 109 tools via an HTTP-hosted endpoint at https://mcp.courier.com. Authentication requires a Courier API key. The server is MIT-licensed and wraps the official @trycourier/courier Node SDK.

Key capabilities

The server provides 109 tools across these categories:

  • Messaging — send notifications and templates; manage sent messages and their status.
  • User profiles — create, update, and retrieve user profiles and preferences.
  • Lists & audiences — manage subscriber lists and audience segments.
  • Notification templates — configure templates and campaigns.
  • Brands — manage notification brands and styling.
  • Routing strategies — configure how notifications are dispatched across channels.
  • Automations & journeys — invoke automations and manage multi-step journeys.
  • Bulk operations — send messages to large recipient sets.
  • Tenants — multi-tenant account management.
  • Audit events — inspect inbound and audit events.

How it compares

Server Multi-channel Automations User profiles Template management Auth
Courier MCP Email, push, SMS, in-app Yes Yes Yes API key
Knock MCP Email, push, SMS, in-app Yes (workflows) Yes Yes OAuth
SendGrid MCP Email only Limited Limited Yes API key
Twilio MCP SMS, voice No Limited No API key

Courier's MCP is notable for its breadth — 109 tools covering the full notification lifecycle, including routing strategies and journey management — all through a single hosted HTTP endpoint.

Installation

Claude Code

claude mcp add Courier --transport http \
  --header "api_key: YOUR_COURIER_API_KEY" \
  https://mcp.courier.com

Claude Desktop

{
  "mcpServers": {
    "courier": {
      "type": "http",
      "url": "https://mcp.courier.com",
      "headers": {
        "api_key": "YOUR_COURIER_API_KEY"
      }
    }
  }
}

Replace YOUR_COURIER_API_KEY with your key from app.courier.com/settings/api-keys.

Requirements

  • A Courier account and API key.
  • An MCP client (Claude Code or Claude Desktop).

Security

  • Test in Courier's sandbox/test mode before using the MCP server against your production environment — sending tools will dispatch real notifications.
  • Scope API keys to the minimum required permissions.
  • Treat Courier API keys as secrets.

Source Verification Notes

Verified on 2026-06-18:

  • The official repository github.com/trycourier/courier-mcp (MIT, v1.3.0 released March 2026) documents the hosted endpoint https://mcp.courier.com, the api_key header authentication, the Claude Code installation command, and the 109-tool catalog.
  • Courier's blog post on the MCP server explains the architecture (Stainless-generated SDK wrapper, HTTP transport) and the design goal of being safe to hand to an AI agent.
  • Claude Code's MCP documentation describes the --transport http and --header patterns used above.
#courier#notifications#email#push#sms#transactional#multi-channel

Source citations

Add this badge to your README

Show that Courier MCP Server for Claude is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/courier-mcp-server.svg)](https://heyclau.de/entry/mcp/courier-mcp-server)

How it compares

Courier MCP Server for Claude side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

FieldCourier MCP Server for Claude

Manage Courier notifications from Claude — send messages and templates, manage user profiles and preferences, configure notification routing, handle automations and journeys, and manage subscriber lists — with the official Courier remote MCP server.

Open dossier 		Knock MCP Server for Claude

Manage your Knock notification infrastructure from Claude — create and edit workflows, channels, templates, and email layouts, manage users and tenants, commit changes across environments, and debug message logs — with the official Knock remote MCP server.

Open dossier 		Postmark MCP Server for Claude

Connect Claude to Postmark — send transactional email, manage templates, search messages, and diagnose delivery, bounces, and suppressions — with the official ActiveCampaign Postmark MCP server.

Open dossier 		Customer.io MCP Server for Claude

Manage Customer.io from Claude — create segments, inspect customer profiles, send broadcasts and campaigns, work with journeys, and access the full Journeys UI and CDP Data Pipelines APIs — with the official Customer.io remote MCP server.

Open dossier
Trust
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
Categorymcpmcpmcpmcp
Sourcesource-backedsource-backedsource-backedsource-backed
AuthorCourierKnockActiveCampaignCustomer.io
Added2026-06-182026-06-182026-06-172026-06-18
Platforms
Claude CodeCursorClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Source repo————
Safety notes✓The server is hosted by Courier and authenticated via API key — it can send real notifications to real users and modify account data. With 109 tools covering sends, user data, and automations, the blast radius is significant — scope your API key to the minimum required permissions and test in a Courier sandbox environment first. Bulk operations and automation invocations are available — review Claude's proposed actions before executing in production.✓The server is hosted by Knock on Cloudflare Workers and authenticated via OAuth 2.1 + PKCE — no API keys required, but write access to your Knock environment is granted after login. Knock's MCP server has no deletion tools by design, reducing destructive-action risk; all changes are staged and require explicit commit/promote steps. Committing and promoting changes across environments is irreversible — review diffs before asking Claude to promote to production.✓Send tools dispatch real transactional email; restrict the server token and confirm recipients before sending through Claude. Template, webhook, and suppression tools change live Postmark configuration; review before running them.✓The server exposes three tool categories: read (GET), write (POST/PUT/PATCH), and delete (DELETE) — approve each independently. By default, the MCP server cannot delete customer profiles or modify live active campaigns — only create new items — reducing accidental audience impact. Write and delete tools can trigger real sends and modify live data; review Claude's proposed actions before confirming.
Privacy notes✓User profile data, notification content, recipient identifiers, and audience lists are sent to Courier's servers when executing tools. Courier API keys are secrets — store them in your environment or MCP client config headers, never in repositories.✓Requests include your notification workflow definitions, template content, user/tenant identifiers, and message logs — all processed by Knock's servers. Knock's OAuth flow stores session credentials securely; avoid sharing MCP session tokens.✓Email content, recipient addresses, message search results, and delivery stats enter the MCP client context and the model's prompt. The POSTMARK_SERVER_TOKEN is a secret — keep it in the client config or environment, never in shared repositories.✓Customer profiles, segment definitions, journey configurations, and campaign data from your Customer.io workspace are surfaced in Claude's context. Customer.io's MCP server is authenticated via OAuth — no API keys are stored in your MCP config.
Prerequisites
  • A Courier account and an API key from app.courier.com/settings/api-keys.
  • An MCP client such as Claude Code or Claude Desktop.
  • A Knock account — authenticate via OAuth when prompted on first tool use.
  • Node.js 18+ for `mcp-remote` (Claude Desktop); Claude Code supports `--transport http` natively.
  • An MCP client such as Claude Code or Claude Desktop.
  • A Postmark account and a server API token (POSTMARK_SERVER_TOKEN).
  • A verified sender signature/email (DEFAULT_SENDER_EMAIL) and a message stream (DEFAULT_MESSAGE_STREAM).
  • Node.js to clone and run the server.
  • An MCP client such as Claude Code or Claude Desktop.
  • A Customer.io account — authenticate via OAuth when prompted on first tool use.
  • EU customers should use `https://mcp-eu.customer.io/mcp` instead of the US endpoint.
  • An MCP client such as Claude Code or Claude Desktop (MCP requires a paid Claude plan).
Install
claude mcp add Courier --transport http --header "api_key: YOUR_COURIER_API_KEY" https://mcp.courier.com
claude mcp add --transport http knock https://mcp.knock.app/mcp
git clone https://github.com/ActiveCampaign/postmark-mcp && cd postmark-mcp && npm install
claude mcp add --transport http customerio https://mcp.customer.io/mcp
Config
{
  "mcpServers": {
    "courier": {
      "type": "http",
      "url": "https://mcp.courier.com",
      "headers": {
        "api_key": "YOUR_COURIER_API_KEY"
      }
    }
  }
}
{
  "mcpServers": {
    "knock": {
      "command": "npx",
      "args": ["mcp-remote", "https://mcp.knock.app/mcp"]
    }
  }
}
{
  "mcpServers": {
    "postmark": {
      "command": "node",
      "args": ["path/to/postmark-mcp/index.js"],
      "env": {
        "POSTMARK_SERVER_TOKEN": "<your-server-token>",
        "DEFAULT_SENDER_EMAIL": "<your-sender@example.com>",
        "DEFAULT_MESSAGE_STREAM": "outbound"
      }
    }
  }
}
{
  "mcpServers": {
    "customerio": {
      "type": "http",
      "url": "https://mcp.customer.io/mcp"
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.