Courier
REMOTE · MCP.COURIER.COM
Send notifications, manage templates, and configure integrations with Courier.
Available components
Last scanned (15 hours ago)
Scores higher than 19% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Communication
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, but returns a challenge with no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
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.
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 →
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
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/ |
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 →
add_bulk_users ~85
Add users to an existing bulk job.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | – | 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. |
| job_id | string | yes | The bulk job ID |
| users | array | yes | Array of user objects to add |
No output schema declared.
No examples provided.
add_subscribers_to_list ~46
Append subscribers to a list without removing existing subscribers.
| Name | Type | Req | Description |
|---|---|---|---|
| list_id | string | yes | The list ID |
| recipients | array | yes | Recipients to set on the list |
No output schema declared.
No examples provided.
add_user_to_tenant ~52
Add a user to a tenant.
| Name | Type | Req | Description |
|---|---|---|---|
| profile | object | – | Tenant-scoped profile overrides |
| tenant_id | string | yes | The tenant ID |
| user_id | string | yes | The user ID |
No output schema declared.
No examples provided.
archive_journey ~39
Archive a journey. Archived journeys cannot be invoked but existing runs continue to completion.
| Name | Type | Req | Description |
|---|---|---|---|
| journey_id | string | yes | The journey template ID to archive |
No output schema declared.
No examples provided.
archive_journey_template ~52
Archive a journey-scoped notification template. Archived templates cannot be sent.
| Name | Type | Req | Description |
|---|---|---|---|
| journey_id | string | yes | The journey template ID that owns this notification |
| notification_id | string | yes | The notification template ID |
No output schema declared.
No examples provided.
archive_notification ~29
Archive a notification template by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| notification_id | string | yes | The notification template ID to archive |
No output schema declared.
No examples provided.
archive_preference_section ~49
Archive a preference section. The section must be empty: delete its topics first, otherwise the request fails with 409.
| Name | Type | Req | Description |
|---|---|---|---|
| section_id | string | yes | Id of the preference section to archive |
No output schema declared.
No examples provided.
archive_preference_topic ~46
Archive a topic within a section.
| Name | Type | Req | Description |
|---|---|---|---|
| section_id | string | yes | Id of the preference section |
| topic_id | string | yes | Id of the subscription preference topic to archive |
No output schema declared.
No examples provided.
archive_preview_device_set ~53
Archive a preview device set. Runs that used it keep their own copy of its devices. The Courier Recommended set cannot be archived.
| Name | Type | Req | Description |
|---|---|---|---|
| device_set_id | string | yes | The device set id (pvs_...) |
No output schema declared.
No examples provided.
archive_request ~39
Archive a send request and all its associated messages by request ID.
| Name | Type | Req | Description |
|---|---|---|---|
| request_id | string | yes | The request ID (requestId returned from /send) |
No output schema declared.
No examples provided.
archive_routing_strategy ~46
Archive a routing strategy. The strategy must not have associated notification templates; unlink all templates before archiving.
| Name | Type | Req | Description |
|---|---|---|---|
| routing_strategy_id | string | yes | The routing strategy ID to archive |
No output schema declared.
No examples provided.
bulk_add_user_tenants ~76
Add a user to several tenants. The user's other tenant memberships are kept. A tenant the user already belongs to is left as it is, unless a profile is given for it, which replaces that membership's profile.
| Name | Type | Req | Description |
|---|---|---|---|
| tenants | array | yes | Array of tenant associations |
| user_id | string | yes | The user ID |
No output schema declared.
No examples provided.
bulk_add_user_tokens ~63
Add several push/device tokens to a user. The user's other tokens are kept. A token that is already stored is replaced with the record given here.
| Name | Type | Req | Description |
|---|---|---|---|
| tokens | array | yes | Token records to upsert |
| user_id | string | yes | The user ID |
No output schema declared.
No examples provided.
bulk_replace_user_preferences ~122
Replace a user's complete set of preference overrides in one request. The topics in the body become the recipient's entire override set: listed topics are created or updated, and every existing override not included is reset to its topic default. An empty `topics` array clears all overrides. Validation-atomic (all-or-nothing).
| Name | Type | Req | Description |
|---|---|---|---|
| tenant_id | string | – | Scope the replacement to a specific tenant context |
| topics | array | yes | The complete set of topic overrides. An empty array resets every existing override. |
| user_id | string | yes | The user ID |
No output schema declared.
No examples provided.
bulk_subscribe_to_list ~47
Replace all subscribers on a list with the given recipients.
| Name | Type | Req | Description |
|---|---|---|---|
| list_id | string | yes | The list ID |
| recipients | array | yes | Recipients to set on the list |
No output schema declared.
No examples provided.
bulk_update_user_preferences ~108
Additively create or update a user's preferences for one or more topics in a single request. Only the topics in the body are touched; existing overrides for other topics are left untouched. Partial-success: valid topics are written and returned in `items`, unapplicable ones collected in `errors`.
| Name | Type | Req | Description |
|---|---|---|---|
| tenant_id | string | – | Scope the update to a specific tenant context |
| topics | array | yes | Topics to create or update |
| user_id | string | yes | The user ID |
No output schema declared.
No examples provided.
cancel_automation ~85
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 "cancelation_token" (single "l").
| Name | Type | Req | Description |
|---|---|---|---|
| cancelation_token | string | yes | The cancelation_token that was set when the automation was originally invoked |
No output schema declared.
No examples provided.
cancel_broadcast_schedule ~34
Cancel a broadcast's scheduled send. The broadcast itself is kept.
| Name | Type | Req | Description |
|---|---|---|---|
| broadcast_id | string | yes | The broadcast id |
No output schema declared.
No examples provided.
cancel_journey ~110
Cancel journey runs. Supply EXACTLY ONE of cancelation_token (cancels every run associated with the token) or run_id (cancels a single run). Cancelation is idempotent: a run that already finished or was already canceled is left unchanged.
| Name | Type | Req | Description |
|---|---|---|---|
| cancelation_token | string | – | Cancels every run associated with this token. Mutually exclusive with run_id. |
| run_id | string | – | Cancels a single run by id. Mutually exclusive with cancelation_token. |
No output schema declared.
No examples provided.
cancel_message ~38
Cancel a message that is currently being delivered. Returns the message details with updated status.
| Name | Type | Req | Description |
|---|---|---|---|
| message_id | string | yes | The message ID to cancel |
No output schema declared.
No examples provided.
cancel_notification_submission ~40
Cancel a notification template submission.
| Name | Type | Req | Description |
|---|---|---|---|
| notification_id | string | yes | The notification template ID |
| submission_id | string | yes | The submission ID to cancel |
No output schema declared.
No examples provided.
courier_installation_guide ~92
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 JWT to authenticate; each guide says so and names the tool that issues one.
| Name | Type | Req | Description |
|---|---|---|---|
| platform | string | yes | Which SDK to return the installation guide for. |
No output schema declared.
No examples provided.
create_brand ~195
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", settings: { colors: { primary: "#1a73e8", secondary: "#ffffff" } } }.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | Optional brand ID; auto-generated if omitted |
| idempotency_key | string | – | 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. |
| name | string | yes | Brand display name |
| settings | object | – | Brand appearance settings. If omitted, defaults to { colors: { primary: "#000000", secondary: "#ffffff" } }. |
| snippets | object | – | Brand snippets |
No output schema declared.
No examples provided.
create_broadcast ~120
Create a broadcast: a one-off message to a list or audience on a single channel. It starts as a draft with no content; add content with put_broadcast_content, then send_broadcast or schedule_broadcast.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | yes | The single delivery channel for this broadcast |
| idempotency_key | string | – | 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. |
| name | string | yes | Human-readable name |
No output schema declared.
No examples provided.
create_bulk_job ~93
Create a new bulk job for sending messages to multiple recipients. Workflow: create_bulk_job → add_bulk_users → run_bulk_job.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | – | 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. |
| message | object | yes | Bulk message definition with event/template and content |
No output schema declared.
No examples provided.
create_journey ~490
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 reports that as "exit node must be the last node in the journey" even when no exit was sent at all. Send and delay nodes are added afterwards by replace_journey, once journey-scoped templates exist. Node ids are server-generated; do NOT include an id field. Example: { name: "Welcome Journey", nodes: [{ type: "trigger", trigger_type: "api-invoke" }, { type: "exit" }], enabled: true }. 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.
| Name | Type | Req | Description |
|---|---|---|---|
| enabled | boolean | – | Whether the journey is active. Defaults to true. |
| idempotency_key | string | – | 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. |
| name | string | yes | Journey display name |
| nodes | array | yes | The trigger node, then a terminal exit node — both required. Send and delay nodes are added later by replace_journey. Node ids are server-generated — do NOT include an id field. Example: [{ type: "tr… |
| state | string | – | Must be "DRAFT". These tools cannot publish. |
No output schema declared.
No examples provided.
create_journey_template ~378
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 channel block — the API rejects bare elements. Example: { journey_id: "j-abc", channel: "email", notification: { name: "Welcome Email", tags: [], brand: null, subscription: null, content: { version: "2022-01-01", elements: [{ type: "channel", channel: "email", elements: [{ type: "text", content: "Hello!" }] }] } } }. The result carries a "verification" object confirming the new id is really present on the journey. verified:true means the id in this response is safe to reference from a send node. verified:false means it is not visible yet — re-read the journey before referencing it, and do not create a second template to work around it. An "errorKind" of "unauthorized" means the template was created and only the check was refused.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | yes | Channel for this template (e.g. "email", "push", "sms", "inbox") |
| idempotency_key | string | – | 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_id | string | yes | The journey template ID. Copy it exactly, character for character, from the response that returned it — never retype it from memory or reconstruct it. |
| notification | object | yes | Notification template definition |
| provider_key | string | – | Specific provider key to target |
| state | string | – | Must be "DRAFT". These tools cannot publish. |
No output schema declared.
No examples provided.
create_list ~40
Create or update a list by list ID.
| Name | Type | Req | Description |
|---|---|---|---|
| list_id | string | yes | The list ID |
| name | string | yes | Display name for the list |
No output schema declared.
No examples provided.
create_notification ~191
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 notification.routing.strategy_id to control which channels are used. Example: { notification: { name: 'welcome-email', tags: [], brand: null, subscription: null, routing: { strategy_id: 'rs_01abc' }, content: { version: '2022-01-01', elements: [] } } }.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | – | 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 | object | yes | Notification template payload |
| state | string | – | Must be "DRAFT". These tools cannot publish. |
No output schema declared.
No examples provided.
create_or_merge_user ~71
Create a new user profile or merge supplied values into an existing profile (POST). Existing fields not included are preserved.
| Name | Type | Req | Description |
|---|---|---|---|
| profile | object | – | Profile data to create or merge (e.g. { email: "...", phone_number: "..." }) |
| user_id | string | yes | The user ID |
No output schema declared.
No examples provided.
create_or_replace_user_push_token ~63
Create or replace a push/device token for a user.
| Name | Type | Req | Description |
|---|---|---|---|
| device | object | – | Device metadata |
| provider_key | string | yes | Push provider |
| token | string | yes | The token string |
| user_id | string | yes | The user ID |
No output schema declared.
No examples provided.
create_or_update_tenant ~159
Create or replace a tenant. Tenants represent organizations or groups that users belong to.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | string | – | Brand ID to associate with this tenant |
| default_preferences | object | – | Default notification preferences applied to users in this tenant. Example: { "items": [{ "id": "topic_abc", "status": "OPTED_IN", "type": "subscription_topic" }] } |
| name | string | yes | Display name for the tenant |
| parent_tenant_id | string | – | Parent tenant ID for hierarchical tenants |
| properties | object | – | Custom properties for the tenant |
| tenant_id | string | yes | The tenant ID |
| user_profile | object | – | Default profile data for users in this tenant |
No output schema declared.
No examples provided.
create_preference_section ~129
Create a preference section in your workspace. The section id is generated and returned. Add topics afterwards with create_preference_topic.
| Name | Type | Req | Description |
|---|---|---|---|
| has_custom_routing | boolean | – | Whether the section defines custom routing for its topics |
| idempotency_key | string | – | 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. |
| name | string | yes | Human-readable name for the section |
| routing_options | array | – | Default channels for the section. Defaults to empty if omitted. |
No output schema declared.
No examples provided.
create_preference_topic ~239
Create a subscription preference topic inside a section. The topic id is generated and returned. Fails with 404 if the section does not exist.
| Name | Type | Req | Description |
|---|---|---|---|
| allowed_preferences | array | – | Preference controls a recipient may customize for this topic |
| default_status | string | yes | Default 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. |
| idempotency_key | string | – | 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. |
| include_unsubscribe_header | boolean | – | Whether to include a list-unsubscribe header on emails for this topic |
| name | string | yes | Human-readable name for the preference topic |
| routing_options | array | – | Default channels delivered for this topic. Defaults to empty if omitted. |
| section_id | string | yes | Id of the preference section to create the topic in |
| topic_data | object | – | Arbitrary metadata associated with the topic |
No output schema declared.
No examples provided.
create_preview_device_set ~105
Create a named, reusable set of preview devices.
| Name | Type | Req | Description |
|---|---|---|---|
| device_ids | array | yes | Device ids (pvd_...) from list_preview_devices. An id the catalog does not list is rejected. |
| idempotency_key | string | – | 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. |
| name | string | yes | Human-readable name for the set |
No output schema declared.
No examples provided.
create_preview_run ~265
Render a template's email on real email clients and capture screenshots. Pass exactly one of device_set_id or device_ids. Each run is billed to the workspace's previews add-on. The run starts PENDING, so poll get_preview_run for the results.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | Variables for the template, the same shape as the data a send would carry |
| device_ids | array | – | Device ids (pvd_...) from list_preview_devices. An id the catalog does not list is rejected. |
| device_set_id | string | – | A saved device set id (pvs_...). Use the Courier Recommended set from list_preview_device_sets for a sensible default. |
| idempotency_key | string | – | 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. |
| locale | string | – | Locale to render, e.g. "en-US" |
| template_id | string | yes | The notification template id (nt_...). It must be a Design Studio template with an email channel. |
| template_version | string | – | Which version renders: omit for the latest draft, "published" for the live version, or a publish such as "v002". |
No output schema declared.
No examples provided.
create_provider ~170
Create a new provider (integration) configuration. Once routing strategies or notification templates reference this config, credential or settings mistakes can affect live sends—confirm provider key and settings against list_provider_catalog before saving. The provider field must be a known Courier provider key.
| Name | Type | Req | Description |
|---|---|---|---|
| alias | string | – | Short alias for referencing this provider |
| idempotency_key | string | – | 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. |
| provider | string | yes | Provider key from the catalog (e.g. sendgrid, twilio, firebase-fcm) |
| settings | object | – | Provider-specific settings (API keys, credentials, etc.) |
| title | string | – | Display name for this provider configuration |
No output schema declared.
No examples provided.
create_routing_strategy ~141
Create a routing strategy defining how notifications are delivered across channels and providers.
| Name | Type | Req | Description |
|---|---|---|---|
| channels | object | – | Per-channel delivery configuration |
| description | string | – | Description of the routing strategy |
| idempotency_key | string | – | 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. |
| name | string | yes | Human-readable name for the routing strategy |
| providers | object | – | Per-provider delivery configuration |
| routing | object | yes | Routing tree defining channel selection method and order |
| tags | array | – | Tags for categorization |
No output schema declared.
No examples provided.
delete_audience ~29
Delete an audience by its ID.
| Name | Type | Req | Description |
|---|---|---|---|
| audience_id | string | yes | The audience ID to delete |
No output schema declared.
No examples provided.
delete_brand ~28
Delete a brand by its ID.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | string | yes | The brand ID to delete |
No output schema declared.
No examples provided.
delete_broadcast ~24
Delete a broadcast.
| Name | Type | Req | Description |
|---|---|---|---|
| broadcast_id | string | yes | The broadcast id |
No output schema declared.
No examples provided.
delete_list ~26
Delete a list by its ID.
| Name | Type | Req | Description |
|---|---|---|---|
| list_id | string | yes | The list ID |
No output schema declared.
No examples provided.
delete_profile ~27
Delete a user profile permanently.
| Name | Type | Req | Description |
|---|---|---|---|
| user_id | string | yes | The user ID to delete |
No output schema declared.
No examples provided.
delete_provider ~41
Delete a provider configuration. Returns 409 if the provider is still referenced by routing or notifications.
| Name | Type | Req | Description |
|---|---|---|---|
| provider_id | string | yes | The provider configuration ID to delete |
No output schema declared.
No examples provided.
delete_tenant ~29
Delete a tenant by its ID.
| Name | Type | Req | Description |
|---|---|---|---|
| tenant_id | string | yes | The tenant ID to delete |
No output schema declared.
No examples provided.
delete_tenant_preference ~45
Remove default notification preference for a topic from a tenant.
| Name | Type | Req | Description |
|---|---|---|---|
| tenant_id | string | yes | The tenant ID |
| topic_id | string | yes | The subscription topic ID |
No output schema declared.
No examples provided.
delete_tenant_template ~63
Delete a tenant notification template. Returns 204 on success, 404 if the template does not exist for this tenant.
| Name | Type | Req | Description |
|---|---|---|---|
| template_id | string | yes | The notification template ID to delete |
| tenant_id | string | yes | The tenant ID that owns the template |
No output schema declared.
No examples provided.
delete_user_list_subscriptions ~30
Delete all list subscriptions for a user.
| Name | Type | Req | Description |
|---|---|---|---|
| user_id | string | yes | The user ID |
No output schema declared.
No examples provided.
delete_user_preference_topic ~53
Delete a user's preference for a specific subscription topic, reverting it to the topic's default status.
| Name | Type | Req | Description |
|---|---|---|---|
| topic_id | string | yes | The subscription topic ID |
| user_id | string | yes | The user ID |
No output schema declared.
No examples provided.
delete_user_token ~41
Delete a specific push token for a user.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | The token identifier to delete |
| user_id | string | yes | The user ID |
No output schema declared.
No examples provided.
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
claude mcp add --transport http trycourier-courier 'https://mcp.courier.com/'
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.