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
duplicate_broadcast ~78

Copy a broadcast into a new draft. The original is left unchanged.

NameTypeReqDescription
broadcast_idstringyesThe broadcast to copy
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.

generate_jwt_for_user ~83

Generate a JWT authentication token for a user. Used for client-side SDK auth (Inbox, Preferences, etc.).

NameTypeReqDescription
expires_instring–Token expiry duration (e.g. "1h", "2 days")
scopesarray–Permission scopes for the token
user_idstringyesThe user ID to scope the token to

No output schema declared.

No examples provided.

get_audience ~70

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.

NameTypeReqDescription
audience_idstringyesThe audience ID

No output schema declared.

No examples provided.

get_audit_event ~32

Get a specific audit event by its ID.

NameTypeReqDescription
audit_event_idstringyesThe audit event ID

No output schema declared.

No examples provided.

get_brand ~49

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.

NameTypeReqDescription
brand_idstringyesThe brand ID

No output schema declared.

No examples provided.

get_broadcast ~35

Get a broadcast by id, including its channel and send or schedule state.

NameTypeReqDescription
broadcast_idstringyesThe broadcast id

No output schema declared.

No examples provided.

get_broadcast_content ~29

Get a broadcast's Elemental content.

NameTypeReqDescription
broadcast_idstringyesThe broadcast id

No output schema declared.

No examples provided.

get_bulk_job ~29

Get the status of a bulk job.

NameTypeReqDescription
job_idstringyesThe bulk job ID

No output schema declared.

No examples provided.

get_journey ~103

Get a journey by ID. Pass version=draft to retrieve the working draft, or version=vN for a historical version. Defaults to published.

NameTypeReqDescription
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.
versionstring–Version to retrieve: "draft", "published" (default), or a version string like "v001"

No output schema declared.

No examples provided.

get_journey_run ~37

Get one journey run by id: its journey, status, and timestamps.

NameTypeReqDescription
run_idstringyesThe journey run id

No output schema declared.

No examples provided.

get_journey_template ~145

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.

NameTypeReqDescription
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.
versionstring–Version to retrieve: "draft", "published" (default), or "vN"

No output schema declared.

No examples provided.

get_journey_template_content ~150

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.

NameTypeReqDescription
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.
versionstring–Version to retrieve: "draft", "published" (default), or a version string like "v001"

No output schema declared.

No examples provided.

get_list ~33

Get one list by its ID, including its name and current state.

NameTypeReqDescription
list_idstringyesThe list ID

No output schema declared.

No examples provided.

get_list_subscribers ~123

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.

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…
list_idstringyesThe list ID

No output schema declared.

No examples provided.

get_message ~35

Get the full details and status of a single message by its ID.

NameTypeReqDescription
message_idstringyesThe message ID to retrieve

No output schema declared.

No examples provided.

get_message_content ~37

Get the rendered content (HTML, text, subject) of a previously sent message.

NameTypeReqDescription
message_idstringyesThe message ID

No output schema declared.

No examples provided.

get_message_history ~56

Get the event history for a message, showing each step in the delivery pipeline (enqueued, sent, delivered, etc.).

NameTypeReqDescription
message_idstringyesThe message ID
typestring–Filter by event type

No output schema declared.

No examples provided.

get_notification ~101

Retrieve a notification template by ID. Optionally request draft, published, or a version such as v001.

NameTypeReqDescription
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.
versionstring–Version to retrieve: "draft", "published" (default — omit this to get it), or a version string like "v001"

No output schema declared.

No examples provided.

get_notification_content ~56

Get the published content blocks of a notification template.

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

No output schema declared.

No examples provided.

get_notification_draft_content ~62

Get the draft (unpublished) content blocks of a notification template.

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

No output schema declared.

No examples provided.

get_notification_metrics ~952

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, NEVER both. Supplying both is rejected. For a relative window like 'the last week', `lookback` alone is the whole answer: do not also pin `start` and `end`. Default is the last 30 days by day. Fine granularities cover shorter windows: HOUR spans at most 7 days and DAY at most 90. How far back a workspace may look also depends on its plan; a request reaching further back is refused with a payment error, which means the plan does not cover that window, NOT that there is no data. A coarser granularity can reach further back than a fine one. Reading the numbers correctly: - The first four counters are NESTED, not separate groups. Every delivered message is also counted in sent, every opened one in delivered, every clicked one in opened. So sent >= delivered >= opened >= clicked always. Report rates (delivered/sent) or the counters themselves. Do NOT add them together — the total is meaningless. And sent minus delivered is NOT a failure count; it is only 'did not reach the delivered stage', for any reason. - errors and undeliverable are counted separately and OVERLAP the funnel: a message that failed on one provider and succeeded on a retry appears in both errors and sent. They are not a remainder and do not complete a total. - Every counter is a count of distinct MESSAGES, not of events. A message that errored three times counts once in errors. - A bucket's `data` array holds one entry per provider and channel. To get a bucket total, add up the entries in that array — that is the only sum that means anything here. Note that rows for Courier's own built-in email sender are excluded, so these entries can add up to less than the workspace's true volume. What the buckets mean: - A message is counted in the bucket it…

NameTypeReqDescription
endstring–Window end, ISO 8601 with offset. Requires start. Must not be combined with lookback.
granularitystring–Bucket size. HOUR covers at most 7 days, DAY at most 90. Defaults to DAY.
lookbackstring–Window length counted back from now, as an ISO 8601 duration (P30D, P12W, PT12H). Defaults to P30D. Must not be combined with start/end.
notification_idstringyesThe notification template ID to report on (no commas or whitespace)
startstring–Inclusive window start, ISO 8601 with offset (2026-04-01T00:00:00Z). Requires end. Must not be combined with lookback.

No output schema declared.

No examples provided.

get_preference_section ~59

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.

NameTypeReqDescription
section_idstringyesId of the preference section

No output schema declared.

No examples provided.

get_preference_topic ~91

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 the topic missing.

NameTypeReqDescription
section_idstringyesId of the preference section
topic_idstringyesId of the subscription preference topic

No output schema declared.

No examples provided.

get_preview_device_set ~35

Get a preview device set by id.

NameTypeReqDescription
device_set_idstringyesThe device set id (pvs_...)

No output schema declared.

No examples provided.

get_preview_run ~89

Get a preview run with its per-device results and screenshot URLs. Poll until status is COMPLETED or FAILED. The URLs are short-lived and re-signed on every read, so fetch them rather than storing them.

NameTypeReqDescription
preview_run_idstringyesThe preview run id (pvr_...)
template_idstringyesThe notification template id (nt_...) the run previewed

No output schema declared.

No examples provided.

get_provider ~28

Fetch a single provider configuration by ID.

NameTypeReqDescription
provider_idstringyesThe provider configuration ID

No output schema declared.

No examples provided.

get_routing_strategy ~46

Retrieve a routing strategy by ID. Returns the full entity including routing, channels, and providers.

NameTypeReqDescription
routing_strategy_idstringyesThe routing strategy ID (rs_ prefix)

No output schema declared.

No examples provided.

get_tenant ~27

Get a tenant by its ID.

NameTypeReqDescription
tenant_idstringyesThe tenant ID

No output schema declared.

No examples provided.

get_tenant_template ~42

Get a tenant notification template association by template ID.

NameTypeReqDescription
template_idstringyesThe template ID
tenant_idstringyesThe tenant ID

No output schema declared.

No examples provided.

get_tenant_template_version ~72

Get a specific version of a tenant notification template (e.g. latest, published, or v1).

NameTypeReqDescription
template_idstringyesThe template ID
tenant_idstringyesThe tenant ID
versionstringyesVersion identifier (latest, published, or v-prefixed)

No output schema declared.

No examples provided.

get_translation ~62

Get a translation for a specific locale (e.g. "en_US", "fr_FR").

NameTypeReqDescription
domainstring–Translation domain (only "default" is supported currently)
localestringyesLocale code (e.g. en_US, fr_FR)

No output schema declared.

No examples provided.

get_user_list_subscriptions ~129

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.

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…
user_idstringyesThe user ID

No output schema declared.

No examples provided.

get_user_preference_topic ~114

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.

NameTypeReqDescription
tenant_idstring–Omit this for the user's workspace-level choice, which answers most questions. Only pass it when you need this topic as scoped to one specific tenant.
topic_idstringyesThe subscription topic ID
user_idstringyesThe user ID

No output schema declared.

No examples provided.

get_user_preferences ~75

Get a user's notification preferences (subscriptions, opt-outs, channel preferences).

NameTypeReqDescription
tenant_idstring–Omit this to get the user's workspace-level preferences — that answers most preference questions. Only pass it when you need the tenant-scoped overrides for one specific tenant instead.
user_idstringyesThe user ID

No output schema declared.

No examples provided.

get_user_profile_by_id ~45

Get a user profile by their ID. Returns profile data including email, phone, and custom properties.

NameTypeReqDescription
user_idstringyesThe user ID to look up

No output schema declared.

No examples provided.

get_user_push_token ~41

Get a specific push/device token for a user.

NameTypeReqDescription
tokenstringyesThe token identifier
user_idstringyesThe user ID

No output schema declared.

No examples provided.

invoke_ad_hoc_automation ~149

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.

NameTypeReqDescription
automationobjectyesThe automation definition with typed steps
brandstring––
dataobject––
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.
profileobject––
recipientstring––
templatestring––

No output schema declared.

No examples provided.

invoke_automation_template ~171

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

NameTypeReqDescription
brandstring–Brand ID override
dataobject–Data to pass to the automation
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.
profileobject–Profile data for the recipient
recipientstringyesRecipient user ID
templatestring–Notification template override
template_idstringyesThe automation template ID

No output schema declared.

No examples provided.

invoke_journey ~172

Invoke a journey run from a journey template. template_id refers to an existing journey template in the workspace. Example: { template_id: "j-onboarding", user_id: "user-123", data: { plan: "pro" } }.

NameTypeReqDescription
dataobject–Data payload passed to the journey for conditions and template variables
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.
profileobject–Profile data for the user (email, phone, custom fields)
template_idstringyesThe journey template ID
user_idstring–Recipient user ID. Can also be resolved from profile or data.

No output schema declared.

No examples provided.

list_audience_members ~128

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.

NameTypeReqDescription
audience_idstringyesThe audience ID
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…

No output schema declared.

No examples provided.

list_audiences ~121

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.

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…

No output schema declared.

No examples provided.

list_audit_events ~34

List audit events in the workspace. Useful for tracking API usage and changes.

NameTypeReqDescription
cursorstring–Pagination cursor

No output schema declared.

No examples provided.

list_automation_run_steps ~51

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.

NameTypeReqDescription
run_idstringyesThe automation run id

No output schema declared.

No examples provided.

list_automation_runs ~180

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

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 automation template ids to filter on

No output schema declared.

No examples provided.

list_automations ~143

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.

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…
versionstring–Return only templates in this state. Omit to return every automation template regardless of state.

No output schema declared.

No examples provided.

list_brands ~112

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.

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…

No output schema declared.

No examples provided.

list_broadcasts ~40

List broadcasts in the workspace.

NameTypeReqDescription
cursorstring–Pagination cursor from a previous response
limitinteger–Max broadcasts per page

No output schema declared.

No examples provided.

list_bulk_users ~38

List the users in a bulk job.

NameTypeReqDescription
cursorstring–Pagination cursor
job_idstringyesThe bulk job ID

No output schema declared.

No examples provided.

list_digest_instances ~174

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 accumulating, or it has nothing in it.

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 instances to return. Defaults to 20; the API caps this at 100.
schedule_idstringyesThe digest schedule id, in the form "sch/{uuid}"

No output schema declared.

No examples provided.

list_journey_run_steps ~54

List the steps of a journey run in order, with each node and what happened at it. This is how to see where a run stopped and why.

NameTypeReqDescription
run_idstringyesThe journey run 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.