EMAIL & COMMUNICATION · FOR AI AGENTS
Courier
Manage notification templates, journeys and delivery through operational agent tools.
Connect an agent to Courier to inspect notification configuration, manage templates and send through your connected delivery providers using MCP, CLI or APIs.
Your integration checklist
- Capabilities
- What you need from your owner
- Create a Courier workspace, connect delivery providers and prepare a test recipient. Select the Test environment and issue a separate API key for the agent before allowing production sends.
- Authentication
- The operational MCP endpoint is https://mcp.courier.com and uses the api_key header. Test and Production have separate keys and configuration. The CLI can read COURIER_API_KEY from its environment.
- Your first task
- Read the Test environment templates and configuration, then send one approved notification to a controlled recipient and inspect its message log.
- Billing & payment
- Courier meters notification sends, with a free monthly allowance and usage-based paid plans. Budget for the connected channel providers as well as Courier; log retention and enterprise features vary by plan.
- Agent payment support
- Not verified. Programmatic usage does not establish autonomous checkout support.
- Operational limits
- A successful tool call or accepted send does not prove recipient delivery. Provider send-rate settings queue excess traffic and are configured separately for Test and Production. Real recipients require an authorized audience and channel configuration.
ORIGINAL AI AGENT STORE INTEGRATION PLAYBOOK
Resolve environment and provider capacity before releasing a notification
Editorial recommendation · Reviewed 2026-10-23
When to choose this service
Choose Courier when an agent needs to operate existing notification journeys and templates across configured channels, with delivery records available for follow-up.
The service maintains notification configuration, routing and delivery history on operated infrastructure. Generating a message does not establish provider accounts or operate the delivery workflow.
Suggested workflow
- Inspect the workspace, environment, template and connected provider. Use a test recipient and a key dedicated to the agent.
- Send one controlled notification, retain its message reference and follow its delivery status. Check the actual channel outcome before expanding the audience.
- Set provider send rates to match the connected account and account for queued messages. Move to Production with its own configuration and explicit audience and budget limits.
Acceptance checks before real work
- Confirm the key belongs to the intended environment.
- Distinguish accepted, queued and delivered messages.
- Check pending sends before repeating a journey or changing a template.
If the workflow fails
Inspect the message and provider logs before resending. If traffic is queued by a provider limit, wait or adjust the approved rate rather than creating duplicate notifications.