Skip to main content
Let an AI agent send notifications for you, deciding who to tell and when. The agent calls send_message_template over the MCP server. The template holds the content, and Courier handles channel selection, failover, and delivery.

​
What to use it for

  • Test a send while you build. Fire a real notification from your editor, with no script to write and no console to open. It is the fastest way to watch a template render against real data.
  • Alert on your own work. A deploy lands or a nightly job fails, and the agent tells whoever owns it.
  • Let the agent choose. An agent triaging tickets or watching a queue decides who to notify, and when.
  • Send a one-off. Reach one customer without building a screen for it.
For testing, connect the agent with a Test environment key. In Test, email only delivers to the address you signed up with, so an agent cannot reach a real customer by mistake.

​
Prerequisites

  • An MCP-capable agent (Claude Code, Cursor, or Codex)

​
Connect and send

1

Connect the Courier MCP server

Add the Courier MCP server to your agent with your environment API key. Connect once, and the agent can call every Courier tool.
See the .
2

Ask the agent to send

Prompt the agent in plain language. It calls send_message_template to do it:
The agent resolves the recipient, looks up the template, and sends. The content stays in the template, so the agent decides when and who without composing the message.Once providers are configured, ask for email or push. Courier picks the channel and fails over as needed.

​
Verify

1

Read back the requestId

The agent returns a requestId. Open and find that request.
2

Confirm it delivered

Expand the message timeline and confirm the provider accepted it.
3

Try a second channel

Ask the agent to send on another channel. A channel with no configured provider shows as UNROUTABLE and Courier skips it, so start with the inbox channel, which needs no setup.