Courier MCP. Track message delivery, manage users, and send alerts.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Courier MCP Server lets your AI agent send and track notifications across multiple channels (email, SMS, push, chat). Use it to trigger complex communication workflows, monitor real-time delivery status (sent, delivered, opened), and manage user profiles and templates all from a single chat interface.
What your AI agents can do
Get message details
Retrieves specific metadata, provider responses, and delivery logs for a single message ID.
Get message history
Gets the full sequence of delivery events (SENT, DELIVERED, etc.) and detailed provider logs for a message.
Get user profile
Fetches a user's contact details (email, phone) and their preferred channels for receiving notifications.
Your agent sends a notification to a recipient using a specific template, routing the message through the best available channel (email, SMS, etc.).
Your agent checks the delivery logs of a specific message ID to see if it was sent, delivered, or opened, and retrieves the full event history.
Your agent fetches a user's contact information (email, phone) and their specific channel delivery preferences.
Your agent retrieves saved audience IDs and lists subscription groups to target notifications to specific segments.
Your agent browses all available notification templates and lists configured brand assets for white-labeling.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
Courier MCP Server: 10 Tools for Messaging & Status
These tools let your AI client manage every stage of communication: listing users, sending alerts, and checking the real-time delivery status of every message.
019d757dget message details
Retrieves specific metadata, provider responses, and delivery logs for a single message ID.
019d757dget message history
Gets the full sequence of delivery events (SENT, DELIVERED, etc.) and detailed provider logs for a message.
019d757dget user profile
Fetches a user's contact details (email, phone) and their preferred channels for receiving notifications.
019d757dlist audiences
Lists saved audience groups and the filter criteria used for targeted notifications.
019d757dlist brands
Lists custom brand names, colors, and logo settings used for white-labeling notifications.
019d757dlist messages
Lists all sent messages, showing the recipient, current status (DELIVERED, OPENED, CLICKED), and timestamps.
019d757dlist subscription lists
Lists the subscription groups and their current subscriber counts for managing recipients.
019d757dlist templates
Lists all available notification templates and the channels they support.
019d757dlist users
Lists all user accounts registered in the Courier workspace, including roles and association details.
019d757dsend notification
Sends a new notification to a specific recipient using a chosen template and multi-channel routing.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Courier, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
Listen up. The Courier MCP Server lets your AI agent send and track messages across multiple channels—email, SMS, push, and chat. You'll use this thing to run complex communication workflows, monitor exactly when a message was delivered or opened, and even manage user profiles and templates, all right from your chat interface.
Want to send a notification? You'll use send_notification to push a message to a specific recipient, picking a template and routing it through the best channel available.
Need to know who you're talking to? You can use get_user_profile to grab a user's contact details—like their email or phone number—and see which channels they prefer. You'll also use list_audiences to pull up saved audience groups and see the filter criteria you used for targeted alerts.
Got a list of people? list_subscription_lists shows your subscription groups and how many subscribers are in each. For templates, you'll use list_templates to see all the notification designs you've set up and what channels they support. You'll also check out list_brands to see your custom brand names, colors, and logo settings for white-labeling.
Want to track down a specific message? You'll use list_messages to get a list of everything that went out, showing the recipient, the current status (DELIVERED, OPENED, CLICKED), and the timestamps. If you need the deep dive, get_message_history gives you the full sequence of delivery events (SENT, DELIVERED, etc.) along with detailed provider logs.
To see specific metadata or provider responses for one message, you'll use get_message_details with a single message ID.
Finally, you'll use list_users to see every account registered in the Courier workspace, including their roles and how they're associated.
How Courier MCP Works
- 1 Connect the Courier integration to your AI client and authorize it with your Auth Token.
- 2 Use your agent to call a specific tool, like
list_templates, specifying what you need (e.g., 'list all welcome templates'). - 3 The agent executes the tool, retrieves the list of available templates, and presents the structured data back to you for the next action.
The bottom line is, your agent handles the connection and tool calls so you can talk about notification management in plain English.
Who Is Courier MCP For?
The Product Manager who needs to confirm if a critical system alert actually got through. The Developer who needs to audit message history and troubleshoot delivery issues. Customer Support agents who must quickly check a user's profile and recent notification history to provide better help.
Verifies if critical system notifications are being delivered correctly and checks audience segmentation status.
Audits message history and tracks delivery status to troubleshoot bugs and verify message flow.
Checks a user's profile and recent notification history to give a customer a complete picture of their account status.
What Changes When You Connect
- See exactly which channels a user prefers by calling
get_user_profile. You immediately know if an SMS alert or an email is better, preventing notification failures. - Verify the status of critical messages by using
get_message_history. You don't just know if it was sent; you see if it was opened and when, which is key for marketing campaigns. - Stop guessing about audience segmentation.
list_audienceslets you see exactly which groups exist and what criteria they use, so you can target your alerts accurately. - Manage brand consistency effortlessly.
list_brandslets you pull up all configured logos and colors, ensuring every notification you send looks like your brand. - Quickly check the overall message status with
list_messages. You get a simple list of every alert sent, its recipient, and its current state (e.g., OPENED or CLICKED). - Orchestrate complex communications using
send_notification. You give the agent a recipient and a template, and it handles the multi-channel routing automatically.
Real-World Use Cases
Troubleshooting a failed system alert
A developer notices a critical system alert failed. They ask their agent to run get_message_history for the alert ID. The agent returns the full provider logs, showing exactly why the delivery failed (e.g., invalid recipient format). The developer fixes the source data and resends the alert.
Onboarding a new high-value client
A support agent needs to welcome a new client. They first use get_user_profile to get the client's preferred contact method. Then, they call send_notification, specifying the 'Welcome' template and the best channel (SMS). The agent sends the alert and confirms the delivery status.
Running a targeted campaign
A marketing manager wants to send a promotion only to users in California who signed up last month. They use list_audiences to find the correct segment ID, then use send_notification to push the message to that group.
Auditing message sends for compliance
A compliance officer needs to prove that all user notifications include a required footer. They use list_templates to check if the footer field is mandatory, and then use list_messages to audit the history of the last 100 messages sent.
The Tradeoffs
Checking user details manually
Copying a user's email from the CRM, checking it against a spreadsheet, and then manually entering it into the notification tool. This is slow and prone to copy/paste errors.
→
Use get_user_profile. Your agent fetches the user's contact details and channel preferences automatically, ensuring you always use the most accurate, system-verified data.
Sending messages without knowing the channel
Guessing if a user prefers SMS or email, and sending it to both. This wastes credits and might annoy the user if the message is redundant.
→
Use get_user_profile first. The tool returns the user's channel-specific delivery preferences, so you only send the notification via the required channel.
Ignoring message status after sending
Calling send_notification and assuming the message was delivered. If the message was blocked or failed, you won't know until days later.
→
Always follow up by calling get_message_history with the returned message ID. This tracks the real-time status, letting you know if the message was delivered, opened, or bounced.
When It Fits, When It Doesn't
Use this server if your primary need is managing complex, multi-channel communication workflows. You need to know why a message failed, not just that it failed. You rely on accurate user data (phone numbers, emails) and need to track engagement (opened/clicked).
Don't use this if you just need to send a simple, single-channel 'hello' message. For that, a dedicated messaging tool might be simpler. If your need is purely analytics (e.g., 'How many users signed up last month?'), use a dedicated user database API instead of list_users.
When in doubt, check get_user_profile first. It provides the foundational data required for almost every other tool call.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Courier. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 10 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Manual communication tracking is a nightmare.
Today, if a client says, 'Did the welcome email go out?' you open the CRM, find the user's ID. Then you switch tabs to the email marketing dashboard. You search for the user, copy the message ID, and paste it into a separate logging tool. You repeat this process for SMS and push notifications, trying to stitch together a single timeline. It's a mess of tabs and copy-pasting.
With the Courier MCP Server, you just ask your agent: 'What's the status of the welcome alert for user 123?' The agent runs the necessary tools (`list_messages`, `get_message_history`) and gives you one clean answer: 'Delivered via email, opened 5 minutes ago.' The whole process takes seconds.
Courier MCP Server: Get full message status and history.
You used to send a notification and then wait for a manual status report—maybe an email days later—to know if it worked. You couldn't verify if the recipient actually opened the message or clicked the link. The status was a black box.
Now, after calling `send_notification` and getting the message ID, you immediately run `get_message_history`. You get a full, time-stamped log of every event: sent, delivered, opened, clicked. You know exactly what happened, minute by minute.
Common Questions About Courier MCP
How do I check the delivery status of a specific message using get_message_details? +
You use get_message_details by providing the message ID. This tool returns specific metadata, provider responses, and the rendering metadata for that single message.
Can I list all users and their notification preferences with get_user_profile? +
No, get_user_profile fetches the details for one specific user ID. To see a list of users, you must use the list_users tool first.
What is the difference between list_messages and list_templates? +
list_messages gives you a list of alerts that were actually sent (with status and time). list_templates shows you the available message formats (like 'Welcome' or 'Password Reset') that you can use.
How do I send a notification to a whole group of people? +
First, use list_audiences to find the correct segment ID. Then, use send_notification, passing the audience ID to ensure the message hits the right group.
If I need to know what channels are available, which tool should I use? +
Use list_templates. This tool lists all available notification templates and specifies which channels (email, SMS, etc.) each template supports.
When I need to know the full history of a message, should I use get_message_history or list_messages? +
You must use get_message_history. This tool resolves event types (SENT, DELIVERED, OPENED, etc.) and gives you detailed provider logs for a single message ID. list_messages only provides a summary of status and timestamps.
How do I ensure my notifications look branded when I send a message using send_notification? +
You use the list_brands tool to retrieve the configured brand names and colors. Then, when calling send_notification, you reference the appropriate brand ID to white-label the message for your users.
If I want to send a notification to a specific segment of users, which tool helps me manage the recipient list? +
Use list_audiences to retrieve the audience IDs and names. This allows you to target notifications to predefined groups, ensuring your message reaches the correct segment of users.
How do I get a Courier Auth Token? +
Log in to your Courier dashboard, navigate to Settings > API Keys, and you will find your Auth Token there. Use the 'Published' key for production environments.
What channels are supported? +
Courier supports dozens of providers for Email (SendGrid, Mailgun), SMS (Twilio, MessageBird), Push (Firebase, OneSignal), and Chat (Slack, Discord).
Can I track if a message was opened? +
Yes, the agent can use the get_message_details tool to check the status of a specific message, which includes tracking events like 'OPENED' or 'CLICKED' if supported by the provider.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
Cobot
Manage coworking spaces via Cobot — track memberships, monitor bookings, and manage resources directly from any AI agent.
RandomUser API
Generate random user data — audit personas and locations via AI.
Vocabulary Forge
AI detectors don't scan for bad grammar — they scan for vocabulary. "Delve", "leverage", "furthermore" are fingerprints. Vocabulary Forge makes the agent build a complete voice profile: define the person, map tonal shifts, purge signal words, add human roughness, commit to a signature. Any language.
You might also like
Height (Project Management)
Manage projects and tasks via Height — track activities, list tasks, and manage workspace lists.
eSign (e签宝)
Leading digital signature and contract platform in China — manage sign flows, templates, and documents via AI.
ShowAPI / 易源数据
Massive API data marketplace — access weather, translation, stock info, and utilities via AI.