by trycourier
Official MCP server for Courier's notification API, providing 60 tools to send messages, manage user profiles, configure
Official MCP server for Courier's notification API, providing 60 tools to send messages, manage user profiles, configure lists, debug deliveries, and handle notification workflows.
courier-mcp is a community-built MCP server published by trycourier that provides AI assistants with tools and capabilities via the Model Context Protocol. Official MCP server for Courier's notification API, providing 60 tools to send messages, manage user profiles, configure It is categorized under communication. This server exposes 20 tools that AI clients can invoke during conversations and coding sessions.
You can install courier-mcp in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
MIT
courier-mcp is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
Useful MCP listing: courier-mcp is the kind of server we cite when onboarding engineers to host + tool permissions.
We wired courier-mcp into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
courier-mcp reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
Useful MCP listing: courier-mcp is the kind of server we cite when onboarding engineers to host + tool permissions.
courier-mcp reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
courier-mcp is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
Strong directory entry: courier-mcp surfaces stars and publisher context so we could sanity-check maintenance before adopting.
I recommend courier-mcp for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
courier-mcp has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
We evaluated courier-mcp against two servers with overlapping tools; this profile had the clearer scope statement.
showing 1-10 of 31
The official Model Context Protocol (MCP) server for the Courier notification API. It gives AI agents full access to the Courier API — send messages, manage profiles, debug deliveries, configure lists, and more — through 60 tools backed by the @trycourier/courier Node SDK.
Courier runs a hosted MCP server at https://mcp.courier.com. No local setup required.
<a href="https://cursor.com/en/install-mcp?name=courier&config=eyJ1cmwiOiAiaHR0cHM6Ly9tY3AuY291cmllci5jb20iLCAiaGVhZGVycyI6IHsiYXBpX2tleSI6ICJZb3VyIEFQSSBLZXkifX0="><img src="https://cursor.com/deeplink/mcp-install-dark.svg" alt="Install in Cursor" height="32" /></a>
Cursor — add to .cursor/mcp.json:
{
"mcpServers": {
"courier": {
"url": "https://mcp.courier.com",
"headers": {
"api_key": "YOUR_COURIER_API_KEY"
}
}
}
}
Claude Code:
claude mcp add courier --transport http --url https://mcp.courier.com --header "api_key: YOUR_COURIER_API_KEY"
Claude Desktop — add to claude_desktop_config.json:
{
"mcpServers": {
"courier": {
"url": "https://mcp.courier.com",
"headers": {
"api_key": "YOUR_COURIER_API_KEY"
}
}
}
}
git clone https://github.com/trycourier/courier-mcp.git
cd courier-mcp
sh dev.sh
Then point your IDE at http://localhost:3000 with the same config format above.
59 default tools organized by API resource, plus 1 diagnostic tool available in local installs.
| Category | Tools |
|---|---|
| Send | send_message, send_message_template, send_message_to_list, send_message_to_list_template |
| Messages | list_messages, get_message, get_message_content, get_message_history, cancel_message |
| Profiles | get_user_profile_by_id, create_or_merge_user, replace_profile, delete_profile, get_user_list_subscriptions, subscribe_user_to_lists, delete_user_list_subscriptions |
| Lists | list_lists, get_list, get_list_subscribers, create_list, subscribe_user_to_list, unsubscribe_user_from_list |
| Audiences | get_audience, list_audience_members, list_audiences, update_audience, delete_audience |
| Notifications | list_notifications, get_notification_content, get_notification_draft_content |
| Brands | create_brand, get_brand, list_brands |
| Auth | generate_jwt_for_user |
| User Tokens | list_user_push_tokens, get_user_push_token, create_or_replace_user_push_token |
| Docs | courier_installation_guide |
| Automations | invoke_automation_template, invoke_ad_hoc_automation |
| Bulk | create_bulk_job, add_bulk_users, run_bulk_job, get_bulk_job, list_bulk_users |
| Audit Events | get_audit_event, list_audit_events |
| Inbound | track_inbound_event |
| Tenants | get_tenant, create_or_update_tenant, list_tenants, delete_tenant |
| Users | get_user_preferences, update_user_preference_topic, list_user_tenants, add_user_to_tenant, remove_user_from_tenant |
| Translations | get_translation, update_translation |
| Category | Tools |
|---|---|
| Config | get_environment_config — check which API key, base URL, and package version the MCP session is using |
courier-mcp/
├── mcp/ # MCP package (@trycourier/courier-mcp on npm)
│ └── src/
│ ├── index.ts # CourierMcp server class
│ ├── tools/ # Tool definitions (one file per API resource)
│ └── utils/ # Config, error handling, registry
├── server/ # Express server (hosts the MCP package via HTTP)
│ └── src/index.ts # Stateless HTTP handler
└── dev.sh # Local development launcher
The MCP package uses the official @trycourier/courier Node SDK (Stainless-generated) for all API calls. The SDK stays in sync with the Courier API spec automatically, so tool implementations are thin wrappers with proper error handling.
| Header | Required | Description |
|---|---|---|
api_key | Yes | Your Courier API key. Get one at app.courier.com/settings/api-keys. |
base_url | No | Override the API base URL. Defaults to https://api.courier.com. |
# Install dependencies
cd mcp && npm install && cd ../server && npm install && cd ..
# Start development server
sh dev.sh
# Run tests
cd mcp && npm test
# Build
cd mcp && npm run build
The @trycourier/courier SDK dependency in mcp/ is updated automatically via Dependabot. Dependabot checks npm daily and opens a PR when a new SDK version is available.
breaking-review): check whether any tool input schemas or error handling need updates before merging.After merging a Dependabot PR, the full pipeline runs automatically:
auto-version-bump.yml bumps the MCP package patch version and pushes to main.publish-npm.yml publishes the new version to npm.bump-services.yml opens a PR in trycourier/services to update the hosted MCP server.Secrets required (set in repo Settings > Secrets and variables > Actions):
REPO_TOKEN — PAT with Contents: Read and write on this repo. Used by auto-version-bump.yml to push to main and trigger downstream workflows.SERVICES_REPO_TOKEN — PAT with Contents: Read and write + Pull requests: Read and write on trycourier/services. Used by bump-services.yml to open dependency bump PRs.NPM_TOKEN — npm publish token. Used by publish-npm.yml.Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.