Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Courier

REMOTE · MCP.COURIER.COM

Send notifications, manage templates, and configure integrations with Courier.

Available components

−43 this week 36 Trust /100

Last scanned (15 hours ago)

Scores higher than 19% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Communication

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security89
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
  • Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
  • Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified

Unverified: 6 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.

What we tested

Checks we ran (5)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC

Checks we could not complete (6)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Transport in Transport & Reachability (scores 0 for this)Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema blocked by authentication: the endpoint requires auth we don't have to read it.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
  • Capabilities in Capabilities (scores 0 for this)Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Nov 26 −43
    • Endpoint reachability: reachable → behind authorisation ▼ security
    • Tool safety: fail → unverified ▼ security
    • Stability: pass → unverified ▼ security
    • Transport: pass → unverified ▼ security
    • Authorization: The endpoint enforces authorisation, but returns a challenge with no valid RFC 9728 metadata, so a client cannot discover where to get a token. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 19 Nov 26 0
    • Tool “bulk_add_user_tenants” rewrote its description, which is the text the model reads security
    • Tool “bulk_add_user_tokens” rewrote its description, which is the text the model reads security
    • “add_bulk_users” added an optional parameter “idempotency_key” cosmetic
    • “create_brand” added an optional parameter “idempotency_key” cosmetic
    • “create_broadcast” added an optional parameter “idempotency_key” cosmetic
    • “create_bulk_job” added an optional parameter “idempotency_key” cosmetic
    • “create_journey” added an optional parameter “idempotency_key” cosmetic
    • “create_journey_template” added an optional parameter “idempotency_key” cosmetic
    • “create_notification” added an optional parameter “idempotency_key” cosmetic
    • “create_preference_section” added an optional parameter “idempotency_key” cosmetic
    • “create_preference_topic” added an optional parameter “idempotency_key” cosmetic
    • “create_preview_device_set” added an optional parameter “idempotency_key” cosmetic
    • “create_preview_run” added an optional parameter “idempotency_key” cosmetic
    • “create_provider” added an optional parameter “idempotency_key” cosmetic
    • “create_routing_strategy” added an optional parameter “idempotency_key” cosmetic
    • “duplicate_broadcast” added an optional parameter “idempotency_key” cosmetic
    • “invoke_ad_hoc_automation” added an optional parameter “idempotency_key” cosmetic
    • “invoke_automation_template” added an optional parameter “idempotency_key” cosmetic
    • “invoke_journey” added an optional parameter “idempotency_key” cosmetic
    • “publish_journey” added an optional parameter “idempotency_key” cosmetic
    • “publish_journey_template” added an optional parameter “idempotency_key” cosmetic
    • “publish_notification” added an optional parameter “idempotency_key” cosmetic
    • “publish_preferences” added an optional parameter “idempotency_key” cosmetic
    • “release_user_digest” added an optional parameter “idempotency_key” cosmetic
    • “run_bulk_job” added an optional parameter “idempotency_key” cosmetic
    • “schedule_broadcast” added an optional parameter “idempotency_key” cosmetic
    • “send_broadcast” added an optional parameter “idempotency_key” cosmetic
    • “send_message” added an optional parameter “idempotency_key” cosmetic
    • “send_message_template” added an optional parameter “idempotency_key” cosmetic
    • “send_message_to_list” added an optional parameter “idempotency_key” cosmetic
    • “send_message_to_list_template” added an optional parameter “idempotency_key” cosmetic
  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 4 Oct 26 0
    • Stability: fail → pass ▲ security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://mcp.courier.com

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.courier.com CN=WE1,O=Google Trust Services,C=US 7 Oct 2026 5 Jan 2027 ECDSA 256 ECDSA-SHA256 cc8e45d17eefa38c135221f5b38531b2
SANs: mcp.courier.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.courier.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
courier.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result Challenged, unverified
Enforced On connection
HTTP status 401
Header Value
strict-transport-security max-age=15552000; includeSubDomains
content-security-policy default-src 'self';base-uri 'self';font-src 'self' https: data:;form-action 'self';frame-ancestors 'self';img-src 'self' data:;object-src 'none';script-src 'self';script-src-attr 'none';style-src 'self' https: 'unsafe-inline';upgrade-insecure-requests
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy no-referrer

Protected resource metadata

Retrieved No
Problem No resource metadata

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.courier.com Auth required 401
http (plaintext) http://mcp.courier.com HTTPS enforced 301 https://mcp.courier.com/
MCP tools · 173 exposed · ~18,718 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
list_journey_runs ~167

List journey runs, newest first. Filter by journey, status, or a created_at window to find a run that stalled or errored, then read its steps with list_journey_run_steps.

NameTypeReqDescription
cursorstring–next_cursor from a previous response
end_datestring–Inclusive upper bound on created_at, ISO 8601 date or timestamp
limitinteger–Runs per page, 1 to 50. Defaults to 20.
start_datestring–Inclusive lower bound on created_at, ISO 8601 date or timestamp
statusstring–Comma-separated run statuses to filter on, e.g. PROCESSED,ERROR
template_idstring–Comma-separated journey ids to filter on

No output schema declared.

No examples provided.

list_journey_template_versions ~55

List published versions of a journey-scoped notification template, ordered most recent first.

NameTypeReqDescription
journey_idstringyesThe journey template ID that owns this notification
notification_idstringyesThe notification template ID

No output schema declared.

No examples provided.

list_journey_templates ~193

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.

NameTypeReqDescription
cursorstring–Check the response's paging.more before calling again — false means every template already came back, and calling again with the same arguments returns the same page, not new data. This is an opaque…
journey_idstringyesThe journey template ID. Copy it exactly, character for character, from the response that returned it — never retype it from memory or reconstruct it.
limitnumber–Page size (1–100)

No output schema declared.

No examples provided.

list_journey_versions ~34

List published versions of a journey, ordered most recent first.

NameTypeReqDescription
journey_idstringyesThe journey template ID

No output schema declared.

No examples provided.

list_journeys ~187

List journey templates in the workspace, returning the journey IDs and version state of each. Optionally filter by version (published or draft).

NameTypeReqDescription
cursorstring–If a response has no cursor, every journey already came back — calling this again with the same arguments returns the same page, not new data. This is an opaque token — never decode it, edit it, or r…
versionstring–Filter by version state. Defaults to published, and the two are never combined in one call. If you don't know whether the journey you want is published or still a draft, calling this twice — once per…

No output schema declared.

No examples provided.

list_lists ~154

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.*".

NameTypeReqDescription
cursorstring–For fetching the next page. This is an opaque token — never decode it, edit it, or rebuild it. Pass it back exactly as it appeared in the previous response's cursor field, byte for byte. Omit this en…
patternstring–Filter by list id pattern, where * matches a segment — for example "example.list.*". Omit to return every list.

No output schema declared.

No examples provided.

list_messages ~332

List messages you've previously sent. Filter by status, recipient, notification, provider, tags, or tenant.

NameTypeReqDescription
archivedboolean–This NARROWS, it does not widen: true returns ONLY archived messages, excluding every active one. Omit it entirely to search active messages — the default view for a normal delivery question. Setting…
cursorstring–For fetching the next page. This is an opaque token — never decode it, edit it, or rebuild it. Pass it back exactly as it appeared in the previous response's cursor field, byte for byte. Omit this en…
enqueued_afterstring–ISO 8601 timestamp; only return messages enqueued after this time
eventstring–Filter by event ID
liststring–Filter by list ID
messageIdstring–Filter by message ID
notificationstring–Filter by notification ID
providerarray–Filter by provider key (e.g. sendgrid, twilio)
recipientstring–Filter by recipient user ID
statusarray–Filter by status (e.g. DELIVERED, UNDELIVERABLE)
tagarray–Filter by metadata tags
tagsstring–Comma-delimited list of tags
tenant_idstring–Filter by tenant ID
traceIdstring–Filter by trace ID

No output schema declared.

No examples provided.

list_notification_checks ~75

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.

NameTypeReqDescription
notification_idstringyesThe notification template ID
submission_idstringyesThe submission ID whose checks to list

No output schema declared.

No examples provided.

list_notification_versions ~148

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.

NameTypeReqDescription
cursorstring–For fetching the next page. This is an opaque token — never decode it, edit it, or rebuild it. Pass it back exactly as it appeared in the previous response's cursor field, byte for byte. Omit this en…
limitnumber–Maximum versions to return per page. Defaults to 10, which is also the maximum.
notification_idstringyesThe notification template ID

No output schema declared.

No examples provided.

list_notifications ~142

List notification templates, newest first. Pass tags to return only templates carrying ALL of the given tags. Page through the rest with cursor.

NameTypeReqDescription
cursorstring–This is an opaque token — never decode it, edit it, or rebuild it. Pass it back exactly as it appeared in the previous response's cursor field, byte for byte. Omit this entirely when you don't have o…
tagsarray–Only return templates carrying ALL of these tags, matched case-insensitively on the tag name shown in a template's tags field (e.g. ["onboarding"]). Omit to list every template.

No output schema declared.

No examples provided.

list_preference_logs ~193

List preference changes, newest first. Each entry is one change a user made to one subscription topic, with the value before it where there was one. Pass user_id to answer "when did this user opt out, and of what?"; omit it to read the whole environment. Page with paging.cursor while paging.more is true.

NameTypeReqDescription
cursorstring–paging.cursor from a previous response
limitinteger–Entries per page, 1 to 100. Defaults to 25.
sincestring–Only changes at or after this time, as an ISO 8601 date or date-time. A date alone is the start of that day in UTC.
tenant_idstring–Narrow to the changes the user made in one tenant context. Requires user_id.
user_idstring–Return only this user's changes. Omit to read every change in the environment.

No output schema declared.

No examples provided.

list_preference_sections ~64

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 what a particular person actually chose.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_preference_topics ~58

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.

NameTypeReqDescription
section_idstringyesId of the preference section

No output schema declared.

No examples provided.

list_preview_device_sets ~35

List saved preview device sets. Every workspace has a read-only Courier Recommended set that runs can use without creating a set first.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_preview_devices ~64

List the email clients a preview can render on. Each device has a pvd_ id, a display name, and fields to filter by: category, app, platform, os, os_version and theme. Use these ids in a device set or in create_preview_run.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_preview_runs ~58

List a template's preview runs, newest first.

NameTypeReqDescription
cursorstring–Pagination cursor from a previous response
limitinteger–Max runs per page
template_idstringyesThe notification template id (nt_...)

No output schema declared.

No examples provided.

list_provider_catalog ~130

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 Courier to" and "what do I need in order to set up this provider".

NameTypeReqDescription
channelstring–Return only providers serving this channel, for example email, sms or push.
keysstring–Comma-separated provider keys to return, for example "sendgrid,twilio".
namestring–Substring match against the provider's display name.

No output schema declared.

No examples provided.

list_providers ~77

List configured provider integrations for the workspace.

NameTypeReqDescription
cursorstring–This is an opaque token — never decode it, edit it, or rebuild it. Pass it back exactly as it appeared in the previous response's cursor field, byte for byte. Omit this entirely when you don't have o…

No output schema declared.

No examples provided.

list_routing_strategies ~151

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 definition.

NameTypeReqDescription
cursorstring–For fetching the next page. This is an opaque token — never decode it, edit it, or rebuild it. Pass it back exactly as it appeared in the previous response's cursor field, byte for byte. Omit this en…
limitnumber–Maximum strategies to return per page. Defaults to 20; the API caps this at 100.

No output schema declared.

No examples provided.

list_routing_strategy_notifications ~74

List notification templates associated with a routing strategy. Useful for checking linked templates before archiving.

NameTypeReqDescription
cursorstring–Pagination cursor
limitnumber–Max results per page (default 20, max 100)
routing_strategy_idstringyesThe routing strategy ID (rs_ prefix)

No output schema declared.

No examples provided.

list_tenant_templates ~57

List notification templates configured for a tenant.

NameTypeReqDescription
cursorstring–Pagination cursor
limitnumber–Max results per page (default 20, max 100)
tenant_idstringyesThe tenant ID

No output schema declared.

No examples provided.

list_tenant_users ~141

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.

NameTypeReqDescription
cursorstring–For fetching the next page. This is an opaque token — never decode it, edit it, or rebuild it. Pass it back exactly as it appeared in the previous response's cursor field, byte for byte. Omit this en…
limitnumber–Maximum users to return per page. Defaults to 20; the API caps this at 100.
tenant_idstringyesThe tenant ID

No output schema declared.

No examples provided.

list_tenants ~131

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.

NameTypeReqDescription
cursorstring–For fetching the next page. This is an opaque token — never decode it, edit it, or rebuild it. Pass it back exactly as it appeared in the previous response's cursor field, byte for byte. Omit this en…
limitnumber–Maximum tenants to return per page.

No output schema declared.

No examples provided.

list_user_push_tokens ~30

List all push/device tokens for a user.

NameTypeReqDescription
user_idstringyesThe user ID

No output schema declared.

No examples provided.

list_user_tenants ~140

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.

NameTypeReqDescription
cursorstring–For fetching the next page. This is an opaque token — never decode it, edit it, or rebuild it. Pass it back exactly as it appeared in the previous response's cursor field, byte for byte. Omit this en…
limitnumber–Maximum tenants to return per page.
user_idstringyesThe user ID

No output schema declared.

No examples provided.

patch_profile ~62

Partially update a user profile via JSON Patch (RFC 6902). Use add/replace/remove operations on specific profile paths.

NameTypeReqDescription
patcharrayyesArray of JSON Patch operations to apply to the profile
user_idstringyesThe user ID

No output schema declared.

No examples provided.

patch_user_token ~58

Apply a JSON Patch (RFC 6902) to a specific push token.

NameTypeReqDescription
patcharrayyesArray of JSON Patch operations
tokenstringyesThe token identifier
user_idstringyesThe user ID

No output schema declared.

No examples provided.

publish_journey ~136

Publish the current draft of a journey, making it live and invokable. Pass version to roll back to a prior published version instead of publishing the draft. Returns 404 if there is no draft to publish.

NameTypeReqDescription
idempotency_keystring–Optional. Pass the same key when you retry this exact call, and Courier returns the first result instead of doing it again. A key is kept for 25 hours.
journey_idstringyesThe journey template ID to publish
versionstring–Historical version to roll back to (e.g. "v001"). Omit to publish the current draft.

No output schema declared.

No examples provided.

publish_journey_template ~131

Publish the current draft of a journey-scoped notification template. Optionally pass version to roll back to a prior version.

NameTypeReqDescription
idempotency_keystring–Optional. Pass the same key when you retry this exact call, and Courier returns the first result instead of doing it again. A key is kept for 25 hours.
journey_idstringyesThe journey template ID that owns this notification
notification_idstringyesThe notification template ID
versionstring–Version to roll back to (e.g. "v1"). Omit to publish current draft.

No output schema declared.

No examples provided.

publish_notification ~149

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 publish a specific historical version. Returns 204 on success.

NameTypeReqDescription
idempotency_keystring–Optional. Pass the same key when you retry this exact call, and Courier returns the first result instead of doing it again. A key is kept for 25 hours.
notification_idstringyesThe notification template ID to publish
versionstring–Historical version to publish (e.g. v001); omit to publish current draft

No output schema declared.

No examples provided.

publish_preferences ~84

Publish the workspace's preferences page. Takes a snapshot of every section with its topics under a new published version, making the current state visible on the hosted preferences page.

NameTypeReqDescription
idempotency_keystring–Optional. Pass the same key when you retry this exact call, and Courier returns the first result instead of doing it again. A key is kept for 25 hours.

No output schema declared.

No examples provided.

publish_tenant_template ~65

Publish a version of a tenant notification template.

NameTypeReqDescription
template_idstringyesThe template ID
tenant_idstringyesThe tenant ID
versionstring–Version to publish (e.g. v1, latest); defaults to latest if omitted

No output schema declared.

No examples provided.

put_broadcast_content ~91

Replace a broadcast's content with an Elemental document. Saved as a draft unless state is PUBLISHED.

NameTypeReqDescription
broadcast_idstringyesThe broadcast id
contentobjectyesElemental content, e.g. { "version": "2022-01-01", "elements": [...] }. version defaults when omitted.
statestring–Template state. Defaults to DRAFT.

No output schema declared.

No examples provided.

put_journey_template_content ~248

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.

NameTypeReqDescription
elementsarrayyesArray of elemental content nodes. Likely must be wrapped in a channel block, the same way create_journey_template's content requires — not independently confirmed for this call, but they write the sa…
journey_idstringyesThe journey template ID that owns this notification. Copy it exactly, character for character, from the response that returned it — never retype it from memory or reconstruct it.
notification_idstringyesThe notification template ID. Copy it exactly, character for character, from the response that returned it — never retype it from memory or reconstruct it.
statestring–Template state after update. Must be "DRAFT". These tools cannot publish.
versionstring–Content version string (e.g. "2022-01-01"). Server defaults when omitted.

No output schema declared.

No examples provided.

put_journey_template_locale ~192

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.

NameTypeReqDescription
elementsarrayyesArray of element overrides with id and locale-specific content
journey_idstringyesThe journey template ID that owns this notification. Copy it exactly, character for character, from the response that returned it — never retype it from memory or reconstruct it.
locale_idstringyesLocale identifier (e.g. es, fr, pt-BR)
notification_idstringyesThe notification template ID. Copy it exactly, character for character, from the response that returned it — never retype it from memory or reconstruct it.
statestring–Template state after update. Must be "DRAFT". These tools cannot publish.

No output schema declared.

No examples provided.

put_notification_content ~262

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: "Hello" }, { type: "text", content: "Email body" }] }, { type: "channel", channel: "push", elements: [{ type: "meta", title: "Hello" }, { type: "text", content: "Push body" }] }, { type: "channel", channel: "inbox", elements: [{ type: "text", content: "Inbox plain text only" }] }]. The template stays a draft; making it live is a separate step this tool cannot perform.

NameTypeReqDescription
elementsarrayyesArray of elemental content nodes
notification_idstringyesThe notification template ID (nt_ prefix). Copy it exactly, character for character, from the response that returned it — never retype it from memory or reconstruct it.
statestring–Must be "DRAFT". These tools cannot publish.
versionstring–Content version string (e.g. "2022-01-01"). Server defaults when omitted.

No output schema declared.

No examples provided.

put_notification_element ~224

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.

NameTypeReqDescription
channelsarray–Channels this element applies to
dataobject–Element data payload
element_idstringyesThe element ID to update, from a prior get_notification or get_notification_draft_content response. Copy it exactly, character for character, from the response that returned it — never retype it from…
ifstring–Conditional expression for element visibility
loopstring–Loop expression for repeating elements
notification_idstringyesThe notification template ID (nt_ prefix). Copy it exactly, character for character, from the response that returned it — never retype it from memory or reconstruct it.
refstring–Reference identifier
statestring–Must be "DRAFT". These tools cannot publish.
typestringyesElement type (e.g. text, action, image, divider, meta)

No output schema declared.

No examples provided.

put_notification_locale ~215

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_meta_1", title: "Restablecer contraseña" }, { id: "elem_text_1", content: "Haga clic en el enlace para restablecer su contraseña." }] }. The template stays a draft; making it live is a separate step this tool cannot perform.

NameTypeReqDescription
elementsarrayyesArray of element overrides with id and locale-specific content
locale_idstringyesLocale identifier (e.g. es, fr, pt-BR)
notification_idstringyesThe notification template ID (nt_ prefix). Copy it exactly, character for character, from the response that returned it — never retype it from memory or reconstruct it.
statestring–Must be "DRAFT". These tools cannot publish.

No output schema declared.

No examples provided.

release_digest ~67

Release a digest schedule early — send what users have collected so far now instead of waiting for the scheduled time. A 204 is also returned when the schedule has no in-progress instances to release.

NameTypeReqDescription
schedule_idstringyesThe digest schedule id, in the form "sch/{uuid}"

No output schema declared.

No examples provided.

release_user_digest ~182

Release one recipient's held digest for a topic now, instead of waiting for its schedule. Use it to preview a digest, or to let a user flush their own, without releasing everyone else on the schedule. There is no release-everyone form of this call; use release_digest with a schedule id for that.

NameTypeReqDescription
idempotency_keystring–Optional. Pass the same key when you retry this exact call, and Courier returns the first result instead of doing it again. A key is kept for 25 hours.
section_idstringyesId of the preference section the topic belongs to
tenant_idstring–The recipient's tenant, when they were sent to as part of one
topic_idstringyesId of the digest topic
user_idstringyesThe recipient whose digest to release

No output schema declared.

No examples provided.

remove_all_user_tenants ~29

Remove a user from all tenants.

NameTypeReqDescription
user_idstringyesThe user ID

No output schema declared.

No examples provided.

remove_user_from_tenant ~40

Remove a user from a tenant.

NameTypeReqDescription
tenant_idstringyesThe tenant ID
user_idstringyesThe user ID

No output schema declared.

No examples provided.

rename_broadcast ~40

Rename a broadcast. Content and channel are unchanged.

NameTypeReqDescription
broadcast_idstringyesThe broadcast id
namestringyesThe new name

No output schema declared.

No examples provided.

replace_journey ~725

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 cannot perform. This is where send, delay, branch and exit nodes are added, and send node template IDs must already be scoped to this journey. The result carries a "verification" object read back from the server after the write — check it every time. verified:true means what you asked for is what saved. verified:false names what did not: "fieldMismatches" for node fields that failed to land, "nodeCountMismatch" for a node dropped or added, and "unknownTemplateReferences" for a send node pointing at a template id this journey does not have — almost always a mistyped id, so re-copy it from the create_journey_template or get_journey response it came from. Fix the specific thing named and send the corrected document. Re-sending an identical call changes nothing, and every replace_journey overwrites the whole draft again. An "errorKind" of "unauthorized" means the write itself succeeded and only the read-back was refused: report that as unconfirmed, never as a failed write.

NameTypeReqDescription
enabledboolean–Whether the journey is active.
journey_idstringyesThe journey template ID to update. Copy it exactly, character for character, from the response that returned it — never retype it from memory or reconstruct it.
namestringyesJourney display name
nodesarrayyesComplete array of journey nodes: the trigger first, a terminal exit last, and everything else between them. Use server-assigned node ids from get_journey — do NOT invent new ids. Send node example: {…
statestring–Must be "DRAFT". These tools cannot publish.

No output schema declared.

No examples provided.

replace_journey_template ~91

Replace the draft of a journey-scoped notification template. Full document replacement. Call publish_journey_template afterwards to make it live.

NameTypeReqDescription
journey_idstringyesThe journey template ID that owns this notification
notificationobjectyesFull notification template definition
notification_idstringyesThe notification template ID
statestring–"PUBLISHED" to publish immediately after replace

No output schema declared.

No examples provided.

replace_notification ~103

Replace a notification template entirely (full document PUT). The template stays a draft; making it live is a separate step this tool cannot perform.

NameTypeReqDescription
notificationobjectyesFull notification template payload
notification_idstringyesThe notification template ID to replace. Copy it exactly, character for character, from the response that returned it — never retype it from memory or reconstruct it.
statestring–Must be "DRAFT". These tools cannot publish.

No output schema declared.

No examples provided.

replace_preference_section ~96

Replace a preference section. Full document replacement; missing optional fields are cleared. Topics attached to the section are unaffected.

NameTypeReqDescription
has_custom_routingboolean–Whether the section defines custom routing for its topics
namestringyesHuman-readable name for the section
routing_optionsarray–Default channels for the section. Omit to clear.
section_idstringyesId of the preference section

No output schema declared.

No examples provided.

replace_preference_topic ~222

Replace a topic within a section. Full document replacement: omitted optional fields are cleared, except `digest`, which is left untouched when omitted. Pass `digest: null` to turn a digest off.

NameTypeReqDescription
allowed_preferencesarray–Preference controls a recipient may customize. Omit to clear.
default_statusstringyesDefault subscription status applied when a recipient has not set their own
digest––Batch this topic's notifications into a scheduled digest. Omit to leave any existing digest untouched; pass null to turn it off.
include_unsubscribe_headerboolean–Whether to include a list-unsubscribe header on emails for this topic
namestringyesHuman-readable name for the preference topic
routing_optionsarray–Default channels delivered for this topic. Omit to clear.
section_idstringyesId of the preference section
topic_dataobject–Arbitrary metadata associated with the topic. Omit to clear.
topic_idstringyesId of the subscription preference topic

No output schema declared.

No examples provided.

replace_preview_device_set ~99

Replace a preview device set's name and devices. This is a full replace, so send every device the set should keep. The Courier Recommended set cannot be changed.

NameTypeReqDescription
device_idsarrayyesDevice ids (pvd_...) from list_preview_devices. An id the catalog does not list is rejected.
device_set_idstringyesThe device set id (pvs_...)
namestringyesThe new name

No output schema declared.

No examples provided.

replace_profile ~54

Fully replace a user profile (PUT). All existing data is overwritten; include every field you want to keep.

NameTypeReqDescription
profileobjectyesComplete profile data to replace with
user_idstringyesThe user ID

No output schema declared.

No examples provided.

Install

How do I install the Courier MCP server?

Courier is a hosted endpoint at https://mcp.courier.com/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.courier.com

# add to Claude Code
claude mcp add --transport http trycourier-courier 'https://mcp.courier.com/'
Common questions

What is the Courier MCP server?

Courier is an MCP server listed in the public MCP registry as io.github.trycourier/courier. Send notifications, manage templates, and configure integrations with Courier. This page covers its hosted endpoint (https://mcp.courier.com).

Is the Courier MCP server safe to use?

Courier scores 36 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Courier MCP server expose?

Courier exposes 173 tools: list_messages, get_message, get_message_content, get_message_history, list_notifications, and 168 more. Their descriptions and schemas cost roughly 18,718 tokens of context every time the server is loaded.

Does the Courier MCP server require authentication?

Yes. Courier asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the Courier MCP server still maintained?

Courier is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Courier MCP server?

VerifyMCP ran 5 checks on Courier, covering TLS certificate, Authorization, HTTPS, HSTS header and 1 more. 6 items could not be completed, a gap on our side rather than a finding about Courier: Transport, Schema quality, Stability, Tool coverage and 2 more. 6 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.