bots.st/courier
Courier
Manage notification templates and sending
1910 ms
answered our call
- State
- Answered
- Protocol
- MCP 2025-06-18
- Tools listed
- 173
- Answered
- 3 of the last 3 calls
How to reach it
- MCP, HTTP
https://mcp.courier.comNeeds header api_key
What it can do
| Tool | What it says it does |
|---|---|
add_bulk_users | Add users to an existing bulk job. |
add_subscribers_to_list | Append subscribers to a list without removing existing subscribers. |
add_user_to_tenant | Add a user to a tenant. |
archive_journey | Archive a journey. Archived journeys cannot be invoked but existing runs continue to completion. |
archive_journey_template | Archive a journey-scoped notification template. Archived templates cannot be sent. |
archive_notification | Archive a notification template by ID. |
archive_preference_section | Archive a preference section. The section must be empty: delete its topics first, otherwise the request fails with 409. |
archive_preference_topic | Archive a topic within a section. |
archive_preview_device_set | Archive a preview device set. Runs that used it keep their own copy of its devices. The Courier Recommended set cannot be archived. |
archive_request | Archive a send request and all its associated messages by request ID. |
archive_routing_strategy | Archive a routing strategy. The strategy must not have associated notification templates; unlink all templates before archiving. |
bulk_add_user_tenants | Add a user to multiple tenants at once. A custom profile can be supplied per tenant. |
bulk_add_user_tokens | Add multiple push/device tokens for a user in one request. Overwrites matching existing tokens. |
bulk_replace_user_preferences | 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… |
bulk_subscribe_to_list | Replace all subscribers on a list with the given recipients. |
bulk_update_user_preferences | 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`. |
cancel_automation | Cancel a running automation by its cancelation_token. This invokes a second ad-hoc automation with a single cancel step. The token must match the cancelation_token set when the original automation was started. Note: spelling is "cancelation_token" (single "l"). |
cancel_broadcast_schedule | Cancel a broadcast's scheduled send. The broadcast itself is kept. |
cancel_journey | 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. |
cancel_message | Cancel a message that is currently being delivered. Returns the message details with updated status. |
cancel_notification_submission | Cancel a notification template submission. |
courier_installation_guide | Get the Courier SDK installation guide for one platform: the install command, a quick-start code sample and the relevant doc links. This is the answer to "how do I integrate Courier" or "how do I get started". Client-side platforms need a JWT to authenticate; each guide says so and names the tool… |
create_brand | Create a new brand. The API requires settings — omitting it returns a 400. If you do not have specific brand colors, omit settings and a safe default will be used automatically (black primary, white secondary). Example: { name: "Acme", settings: { colors: { primary: "#1a73e8", secondary: "#ffffff"… |
create_broadcast | 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. |
create_bulk_job | Create a new bulk job for sending messages to multiple recipients. Workflow: create_bulk_job → add_bulk_users → run_bulk_job. |
create_journey | Create a new journey. Always created as a draft; making it live is a separate step this tool cannot perform. Send two nodes: the trigger, and an exit node last. Both are required — a create with no exit node is rejected, and the API reports that as "exit node must be the last node in the journey"… |
create_journey_template | Create a notification template scoped to a journey. Always created as a draft; making it live is a separate step this tool cannot perform. The template can then be referenced in journey send nodes. content.elements must be wrapped in a channel block — the API rejects bare elements. Example: {… |
create_list | Create or update a list by list ID. |
create_notification | Create a V2 notification template. name is required. Content may be provided inline or set separately afterwards. A newly created template is a draft; making it live is a separate step this tool cannot perform. Link a routing strategy via notification.routing.strategy_id to control which channels… |
create_or_merge_user | Create a new user profile or merge supplied values into an existing profile (POST). Existing fields not included are preserved. |
create_or_replace_user_push_token | Create or replace a push/device token for a user. |
create_or_update_tenant | Create or replace a tenant. Tenants represent organizations or groups that users belong to. |
create_preference_section | Create a preference section in your workspace. The section id is generated and returned. Add topics afterwards with create_preference_topic. |
create_preference_topic | Create a subscription preference topic inside a section. The topic id is generated and returned. Fails with 404 if the section does not exist. |
create_preview_device_set | Create a named, reusable set of preview devices. |
create_preview_run | 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. |
create_provider | 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… |
create_routing_strategy | Create a routing strategy defining how notifications are delivered across channels and providers. |
delete_audience | Delete an audience by its ID. |
delete_brand | Delete a brand by its ID. |
delete_broadcast | Delete a broadcast. |
delete_list | Delete a list by its ID. |
delete_profile | Delete a user profile permanently. |
delete_provider | Delete a provider configuration. Returns 409 if the provider is still referenced by routing or notifications. |
delete_tenant | Delete a tenant by its ID. |
delete_tenant_preference | Remove default notification preference for a topic from a tenant. |
delete_tenant_template | Delete a tenant notification template. Returns 204 on success, 404 if the template does not exist for this tenant. |
delete_user_list_subscriptions | Delete all list subscriptions for a user. |
delete_user_preference_topic | Delete a user's preference for a specific subscription topic, reverting it to the topic's default status. |
delete_user_token | Delete a specific push token for a user. |
duplicate_broadcast | Copy a broadcast into a new draft. The original is left unchanged. |
generate_jwt_for_user | Generate a JWT authentication token for a user. Used for client-side SDK auth (Inbox, Preferences, etc.). |
get_audience | Get one audience by ID, including the filter that defines its membership. Read this to explain why someone is or is not in an audience — the filter is the rule, not a stored member list. Use list_audience_members for who currently matches. |
get_audit_event | Get a specific audit event by its ID. |
get_brand | Get one brand by ID, including its colors, logo and styling settings. Read this to describe what a template referencing this brand will actually look like. |
get_broadcast | Get a broadcast by id, including its channel and send or schedule state. |
get_broadcast_content | Get a broadcast's Elemental content. |
get_bulk_job | Get the status of a bulk job. |
get_journey | Get a journey by ID. Pass version=draft to retrieve the working draft, or version=vN for a historical version. Defaults to published. |
get_journey_run | Get one journey run by id: its journey, status, and timestamps. |
And 113 more tools.
In its maker's words
Send notifications, manage templates, and configure integrations with Courier.
- Website
- courier.com
- Source
- github.com/trycourier/courier-mcp
- Publisher
- trycourier
- Listed from
- the official MCP Registry as
io.github.trycourier/courier - Version
- 1.3.7, updated 18 Jun 2026
- Kinds of work
- Messaging and support, AI models and agent tools, Productivity
The domain it lives on
- courier.com
- registered 9 Sep 1993 (33 years ago), at Amazon Registrar, Inc., its home page is a working site
From our own crawl of domain names: registry records and the home page as our crawler last saw it.
Every call we made
| When | What happened | Time |
|---|---|---|
| Answered | 1910 ms | |
| Answered | 2406 ms | |
| Answered | 913 ms |
Next door
- Inbin: email for AI agentsDisposable inboxes for agent email verification
- AgentLairEmail delegation via inbox and vault
- Mailrith Email MarketingManage email subscribers, broadcasts, and automations with r
- faxforagents-mcpSend and receive faxes with approval
- AnyHookManage webhook inboxes for agent events
Is this your bot? Claim its address to add a verified badge and keep the listing current.