Courier MCP: notifications, templates and delivery in your AI app

Connect Courier to Claude, ChatGPT or Cursor

1. 1Click Connect Courier free. There's no sign-in, so its tools are ready at once.
2. 2Template tools such as `create_notification` and `put_notification_content` only change drafts; making a template live is a separate step they can't perform. Sending reaches real people, so switch off any send tool your AI app shouldn't call.
3. 3Add ContextGate to your AI app as a connector or MCP server. The steps for each app are on the Works with page.
4. 4Ask your AI app why a password-reset email sent through Courier wasn't delivered, then open Activity to see the `get_message_history` call.

Messaging work from Claude or Cursor

• Find messages you've sent by status, recipient or tag with `list_messages`, and follow each delivery step with `get_message_history`.
• Draft a new notification template with `create_notification`; it stays a draft until someone publishes it.
• Add Spanish or other locale overrides to a template with `put_notification_locale`.
• See which providers are configured with `list_providers`, and how routing strategies pick a channel with `list_routing_strategies`.

Courier's server has 60 tools; the full list appears in ContextGate as soon as you add it.

Keep notifications from going out unchecked

• Switch off any sending or template tool; it's hidden and refused if called.
• A policy can hide recipients' emails and phone numbers in message lookups.
• Activity records every Courier call your team's AI apps make.

What you get with Courier and ContextGate

• Your AI apps can use CourierClaude, Cursor, ChatGPT and other AI apps reach Courier through the one ContextGate connection you add to them.
• You choose which tools they can useSwitch off any Courier tool you don't want used. It's hidden from your AI apps and refused if called.
• Every call is checked and recordedYour policies check each call (for example, personal data is hidden and secrets are blocked), and Activity keeps a record of it.

ContextGate sees only the tool calls that go through it, not your AI app's built-in tools or your chats.

Courier tools

Examples of what your AI apps can do in Courier. You'll see the exact list of tools after you connect it.

• list_messagesList messages you've previously sent. Filter by status, recipient, notification, provider, tags, or tenant.
• get_messageGet the full details and status of a single message by its ID.
• get_message_contentGet the rendered content (HTML, text, subject) of a previously sent message.
• get_message_historyGet the event history for a message, showing each step in the delivery pipeline (enqueued, sent, delivered, etc.).
• list_notificationsList notification templates, newest first. Pass tags to return only templates carrying ALL of the given tags. Page through the rest with cursor.
• get_notification_contentGet the published content blocks of a notification template.
• get_notification_draft_contentGet the draft (unpublished) content blocks of a notification template.
• create_notificationCreate 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
• get_notificationRetrieve a notification template by ID. Optionally request draft, published, or a version such as v001.
• replace_notificationReplace a notification template entirely (full document PUT). The template stays a draft; making it live is a separate step this tool cannot perform.
• put_notification_contentReplace the elemental content of a V2 notification template. Overwrites all elements. Use channel elements to target specific channels. Multi-channel example: e
• put_notification_elementUpdate a single element within a V2 notification template. The template stays a draft; making it live is a separate step this tool cannot perform.
• put_notification_localeSet locale-specific content overrides for a V2 notification template. Each element override must reference an existing element by its id. Example for Spanish lo
• list_notification_versionsList 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 ver
• list_notification_checksList 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
• list_providersList configured provider integrations for the workspace.
• get_providerFetch a single provider configuration by ID.
• list_provider_catalogList the provider integrations Courier supports and the configuration each one expects. This is the catalog of what COULD be connected, not what this workspace
• get_routing_strategyRetrieve a routing strategy by ID. Returns the full entity including routing, channels, and providers.
• list_routing_strategiesList the workspace's routing strategies, returning metadata only. A routing strategy decides which channel a notification takes and in what order. Use this to f