Courier
Send notifications, manage templates, and configure integrations with Courier
Reviews
No review yet. Used Courier? Be the first to help others choose.What it does
Courier is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.
No capability identified yet from its description.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 15h ago (live check)Hosted endpoint
https://mcp.courier.comstreamable-http
Required: api_key (get it from the publisher)
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"courier-1": {
"url": "https://mcp.courier.com",
"headers": {
"api_key": "<your api_key>"
}
}
}
}Replace the values in <angle brackets>.
Live check
Electra Index connected to the hosted endpoint 15h agoONLINE Courier answered an MCP connection on 16 Nov 2026 and introduced itself as @trycourier/courier-mcp 1.3.7 (MCP protocol 2025-06-18).
173 tools offered to AI assistants
list_messages· List messages you've previously sent. Filter by status, recipient, notification, provider, tags, or tenant.get_message· Get the full details and status of a single message by its ID.get_message_content· Get the rendered content (HTML, text, subject) of a previously sent message.get_message_history· Get the event history for a message, showing each step in the delivery pipeline (enqueued, sent, delivered, etc.).list_notifications· List notification templates, newest first. Pass tags to return only templates carrying ALL of the given tags. Page through the rest with cursor.get_notification_content· Get the published content blocks of a notification template.get_notification_draft_content· Get the draft (unpublished) content blocks of a notification template.create_notification· Create a V2 notification template. name is required. Content may be provided inline or set separately afterwards. A newly created template is a draft; making it live is a separate step this tool cannot perform. Link a routing strategy via nget_notification· Retrieve a notification template by ID. Optionally request draft, published, or a version such as v001.replace_notification· Replace a notification template entirely (full document PUT). The template stays a draft; making it live is a separate step this tool cannot perform.put_notification_content· Replace the elemental content of a V2 notification template. Overwrites all elements. Use channel elements to target specific channels. Multi-channel example: elements: [{ type: "channel", channel: "email", elements: [{ type: "meta", title:put_notification_element· Update a single element within a V2 notification template. The template stays a draft; making it live is a separate step this tool cannot perform.
Show 88 more
put_notification_locale· Set locale-specific content overrides for a V2 notification template. Each element override must reference an existing element by its id. Example for Spanish locale: { notification_id: "nt_01abc", locale_id: "es", elements: [{ id: "elem_metlist_notification_versions· List the version history of a notification template — each published version with when it was created. Use this to say what changed and when, or to find the version string get_notification accepts.list_notification_checks· List the checks recorded against one notification submission. Checks are the gates a submission has to clear before it goes out, so a failing check here is the reason a template is stuck rather than live.list_providers· List configured provider integrations for the workspace.get_provider· Fetch a single provider configuration by ID.list_provider_catalog· List the provider integrations Courier supports and the configuration each one expects. This is the catalog of what COULD be connected, not what this workspace has configured — use list_providers for that. Answers "what can I connect Courieget_routing_strategy· Retrieve a routing strategy by ID. Returns the full entity including routing, channels, and providers.list_routing_strategies· List the workspace's routing strategies, returning metadata only. A routing strategy decides which channel a notification takes and in what order. Use this to find the rs_-prefixed strategy ID that get_routing_strategy needs for the full delist_preference_sections· List the workspace's preference sections, each with the topics inside it. One call returns the whole opt-in surface: everything a user could subscribe to or opt out of. This is what the workspace DEFINES — use get_user_preferences for whatget_preference_section· Get one preference section by ID, including its topics. Use this when you already know which section you need; list_preference_sections returns every section with its topics in one call.list_preference_topics· List the subscription topics inside one preference section. A topic is the individual thing a user opts in or out of, and its ID is what get_user_preference_topic takes.get_preference_topic· Get one subscription topic within a section, including its default opt-in state. Returns 404 if the section or topic does not exist, or if the topic belongs to a different section — so a 404 here can mean the pairing is wrong rather than thcreate_journey· Create a new journey. Always created as a draft; making it live is a separate step this tool cannot perform. Send two nodes: the trigger, and an exit node last. Both are required — a create with no exit node is rejected, and the API reportsget_journey· Get a journey by ID. Pass version=draft to retrieve the working draft, or version=vN for a historical version. Defaults to published.replace_journey· Replace (update) a journey draft. Full document replacement — include all nodes and properties in the body, the trigger included; anything omitted is deleted. The journey stays a draft; making the change live is a separate step this tool cacreate_journey_template· Create a notification template scoped to a journey. Always created as a draft; making it live is a separate step this tool cannot perform. The template can then be referenced in journey send nodes. content.elements must be wrapped in a chanput_journey_template_content· Replace the elemental content of a journey-scoped notification template. Overwrites all elements. The template stays a draft; making it live is a separate step this tool cannot perform.put_journey_template_locale· Set locale-specific content overrides for a journey-scoped notification template. Each element override must reference an existing element by its id. The template stays a draft; making it live is a separate step this tool cannot perform.list_journeys· List journey templates in the workspace, returning the journey IDs and version state of each. Optionally filter by version (published or draft).list_journey_templates· List notification templates scoped to a journey. Journey-scoped templates can only be used by send nodes within the same journey. Call this to discover template IDs before wiring send nodes in replace_journey.get_journey_template· Get a journey-scoped notification template by notification ID. Pass version=draft to retrieve the working draft (required before the template has been published). Defaults to published.get_journey_template_content· Fetch the elemental content of a journey-scoped notification template. Pass version=draft for the working draft, or vN for a historical version. Defaults to published.get_notification_metrics· Delivery funnel for ONE notification template over time: sent, delivered, opened, clicked, errors and undeliverable, per provider and channel, in time buckets. Choosing the window — supply EITHER `lookback` OR `start` and `end` together, NEget_tenant· Get a tenant by its ID.list_tenants· List the workspace's tenants. A tenant is a customer or organisation whose users, branding and preferences are scoped separately; this answers "what tenants do I have" and gives you the tenant IDs get_tenant needs.list_tenant_users· List the users associated with one tenant. Use this to confirm whether someone actually belongs to the tenant whose branding or preferences you are reasoning about.get_user_profile_by_id· Get a user profile by their ID. Returns profile data including email, phone, and custom properties.get_user_list_subscriptions· List the lists one user is subscribed to. Use this when explaining why a user received something — a subscription here is the reason a list-addressed send reached them, and its absence rules that path out.get_user_preferences· Get a user's notification preferences (subscriptions, opt-outs, channel preferences).get_user_preference_topic· Get one user's choice for a single subscription topic — whether they opted in or out, and per channel. Use this when you already know which topic is in question; get_user_preferences returns all of them at once.list_user_tenants· List the tenants a user belongs to. Preferences and branding can be scoped per tenant, so this tells you which tenant-scoped settings could apply to this user at all before you go looking for them.list_brands· List the workspace's brands. A brand is the reusable logo, colors and email styling a notification template renders with; this gives you the brand IDs a template's brand reference points at.get_brand· Get one brand by ID, including its colors, logo and styling settings. Read this to describe what a template referencing this brand will actually look like.courier_installation_guide· Get the Courier SDK installation guide for one platform: the install command, a quick-start code sample and the relevant doc links. This is the answer to "how do I integrate Courier" or "how do I get started". Client-side platforms need a Jlist_automations· List the workspace's automation templates, each with its template ID and whether it has a published or draft version. Answers "what automations already exist here" — this only reads the catalog, it never runs one.list_audiences· List the workspace's audiences. An audience is a saved filter over user profiles — a dynamic segment — so this answers "who can I target" and gives you the audience IDs that journey audience triggers and send requests refer to.get_audience· Get one audience by ID, including the filter that defines its membership. Read this to explain why someone is or is not in an audience — the filter is the rule, not a stored member list. Use list_audience_members for who currently matches.list_audience_members· List the users who currently match an audience's filter. Membership is computed, so this reflects profiles as they are right now — a profile change can move someone in or out without the audience itself being edited.list_lists· List the workspace's lists. A list is an explicit, subscription-based group of users — someone is on it because they were subscribed, not because they match a rule. Optionally filter by an id pattern such as "example.list.*".get_list· Get one list by its ID, including its name and current state.get_list_subscribers· List the users subscribed to a list. Use this to confirm whether someone was actually on a list at all — a subscription here is the reason a list-addressed send reached them.list_digest_instances· List the digest instances for a digest schedule. Each instance is the events accumulated so far for one user against that schedule, so this shows what is waiting to go out and answers why a digest has not arrived yet — it is still accumulatupdate_audience· Create or update an audience with a filter definition.delete_audience· Delete an audience by its ID.get_audit_event· Get a specific audit event by its ID.list_audit_events· List audit events in the workspace. Useful for tracking API usage and changes.generate_jwt_for_user· Generate a JWT authentication token for a user. Used for client-side SDK auth (Inbox, Preferences, etc.).invoke_automation_template· Invoke an automation run from an existing automation template. template_id refers to an existing automation template in the workspace. Example: { template_id: "auto-onboarding", recipient: "user-123", data: { plan: "pro" } }.invoke_ad_hoc_automation· Invoke an ad-hoc automation with inline steps. Valid step actions: send, send-list, delay, cancel, update-profile, invoke, fetch-data. To cancel a previously started automation, use the cancel_automation tool instead.cancel_automation· Cancel a running automation by its cancelation_token. This invokes a second ad-hoc automation with a single cancel step. The token must match the cancelation_token set when the original automation was started. Note: spelling is "cancelationlist_automation_runs· List automation runs, newest first. Filter by automation template, status, or a created_at window to find a run that stalled or errored, then read its steps with list_automation_run_steps. Journey runs are listed by list_journey_runs instealist_automation_run_steps· List the steps of an automation run in order, with what happened at each. Send steps carry a message_id to follow with get_message.create_brand· Create a new brand. The API requires settings — omitting it returns a 400. If you do not have specific brand colors, omit settings and a safe default will be used automatically (black primary, white secondary). Example: { name: "Acme", settupdate_brand· Replace an existing brand with new values.delete_brand· Delete a brand by its ID.create_bulk_job· Create a new bulk job for sending messages to multiple recipients. Workflow: create_bulk_job → add_bulk_users → run_bulk_job.add_bulk_users· Add users to an existing bulk job.run_bulk_job· Run a bulk job, triggering delivery to all added users.get_bulk_job· Get the status of a bulk job.list_bulk_users· List the users in a bulk job.track_inbound_event· Track an inbound event that can trigger automations. Requires event name, messageId (for deduplication), and properties.create_list· Create or update a list by list ID.subscribe_user_to_list· Subscribe a user to a list. Creates the list if it doesn't exist.unsubscribe_user_from_list· Unsubscribe a user from a list.delete_list· Delete a list by its ID.restore_list· Restore a previously deleted list.bulk_subscribe_to_list· Replace all subscribers on a list with the given recipients.add_subscribers_to_list· Append subscribers to a list without removing existing subscribers.cancel_message· Cancel a message that is currently being delivered. Returns the message details with updated status.resend_message· Resend a previously sent message. Loads the original send request and enqueues a brand-new send to the same recipient with the same content, producing a new messageId; the original message is unchanged. Rate limited per message (429 on rapitrace_message· Trace delivery in one call. Give EXACTLY ONE of message_id (a single message) or trace_id (the metadata.trace_id set on a send, which can span several messages). Returns each matching message with its event history, which carries the statusarchive_notification· Archive a notification template by ID.publish_notification· Publish a notification template, making it available for sending. Must be called before send_message_template unless the template was created with state: 'PUBLISHED'. Publishes the current draft by default; pass version (e.g. 'v001') to pubupdate_notification_checks· Update check statuses for a notification submission.cancel_notification_submission· Cancel a notification template submission.create_or_merge_user· Create a new user profile or merge supplied values into an existing profile (POST). Existing fields not included are preserved.replace_profile· Fully replace a user profile (PUT). All existing data is overwritten; include every field you want to keep.patch_profile· Partially update a user profile via JSON Patch (RFC 6902). Use add/replace/remove operations on specific profile paths.delete_profile· Delete a user profile permanently.subscribe_user_to_lists· Subscribe a user to one or more lists. Creates lists that do not exist.delete_user_list_subscriptions· Delete all list subscriptions for a user.send_message· Send a message to a user using inline title and body content (no template). Optionally specify routing channels. API reference: https://www.courier.com/docs/api-reference/send/send-a-message.send_message_template· Send a message to a user using a published notification template. Only published templates can be sent; publishing a draft is a separate operation. Example: { user_id: "user-123", template: "nt_01abc123", data: { name: "Alex", resetUrl: "htsend_message_to_list· Send a message to all subscribers of a list using inline title and body content. API reference: https://www.courier.com/docs/api-reference/send/send-a-message.send_message_to_list_template· Send a message to all subscribers of a list using a notification template.create_or_update_tenant· Create or replace a tenant. Tenants represent organizations or groups that users belong to.delete_tenant· Delete a tenant by its ID.update_tenant_preference· Set the default notification preference for a subscription topic on a tenant. This controls tenant-level defaults — it does NOT set per-user preferences (use the user preferences API for that). The topic_id must already exist as a subscript
The first 100 are shown.
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Hosted endpoint | https://mcp.courier.com | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Local install (package) | no | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Website | https://courier.com | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Repository | https://github.com/trycourier/courier-mcp | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Version | 1.3.7 | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 1d ago |
Change history
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is Courier still online?
Free alerts · no account▲ 0Do you run Courier? Know when it stops answering
For publishers · optionalIts hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.
Monitoring never changes a score or a rank.
Questions about Courier
How do I connect Courier?
Use the hosted endpoint https://mcp.courier.com in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
Does Courier need an API key or token?
Yes. The registry entry lists a required value: api_key. Get it from the publisher.
What tools does Courier offer?
When Electra Index connected on 16 Nov 2026, it listed 173 tools: list_messages, get_message, get_message_content, get_message_history, list_notifications, get_notification_content, get_notification_draft_content, create_notification and more. The full list is in "Live check" above.
Is Courier online?
Yes. Its hosted endpoint answered an MCP connection from Electra Index 15h ago.