Courier MCP Server (Official)
Official Courier MCP server enabling AI agents to send multi-channel notifications through Courier's notification infrastructure platform — sending emails, SMS, push notifications, Slack messages, and in-app notifications through a single unified API with routing logic, preferences, and delivery tracking.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
HTTPS enforced. Single workspace token — no scopes. Separate prod/test tokens. SOC 2, GDPR. Official Courier MCP server.
⚡ Reliability
Best When
An agent needs to send notifications across multiple channels (email, SMS, push, Slack) through a single API with user preference management.
Avoid When
You only need a single notification channel — use a dedicated provider (SendGrid, Twilio) instead.
Use Cases
- • Sending multi-channel notifications from alert and monitoring agents
- • Delivering personalized notifications through preferred user channels from engagement agents
- • Triggering transactional messages (receipts, confirmations) from commerce agents
- • Managing notification templates and routing rules from content agents
- • Tracking notification delivery and engagement from analytics agents
- • Orchestrating complex notification workflows from automation agents
Not For
- • Teams using a single-channel solution (Sendgrid for email-only, Twilio for SMS-only)
- • High-volume marketing email blasts (consider dedicated ESP for bulk email)
- • Teams without multi-channel notification needs
Interface
Authentication
Courier Auth Token from dashboard. Single token per workspace. Production and test tokens are separate environments. No scope granularity.
Pricing
Generous free tier for development. Pricing based on notification volume. Channel costs vary (SMS costs more than email). MCP server is open source official.
Agent Metadata
Known Gotchas
- ⚠ Template IDs vs event names — notification routing uses event names that map to templates
- ⚠ Production vs test environments require different auth tokens
- ⚠ Channel provider configuration required in dashboard before sending via that channel
- ⚠ Recipient profiles can be pre-stored or passed inline — use consistent approach
- ⚠ Delivery tracking requires webhook setup — send API response doesn't confirm delivery
- ⚠ SMS and push notifications require additional provider configuration (Twilio, FCM, etc.)
Alternatives
Full Evaluation Report
Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for Courier MCP Server (Official).
Scores are editorial opinions as of 2026-03-06.