AI

How to Send Notifications from an AI Agent with Courier's MCP Server

AI agents handle support tickets, monitor pipelines, run onboarding flows, and sync CRM data. When they do, someone needs to know what happened. Courier's MCP server gives agents direct access to the full notification API: send across email, push, SMS, Slack, and in-app. Check user preferences before sending. Trigger batch and digest Journeys so high-volume agents don't spam users. This guide covers MCP server setup, CLI tooling, Courier Skills for your IDE, and five real-world patterns with starter prompts.

Build with AI: let your agent handle notifications end to end

Courier's Build with AI toolkit gives coding agents direct access to your notification infrastructure. Four integration points, one goal: let your agent send messages, debug deliveries, manage users, and follow notification best practices without context-switching. Works with Claude Code, Cursor, and any agent that can run shell commands or call MCP tools.

How to Use Claude Code on Mobile to Design, Test, and Ship Multichannel Notifications

A walkthrough of using Claude Code's mobile app with Courier's MCP server and CLI to design, test, and ship a multichannel product announcement from a phone. Covers the full workflow: drafting the content outline, creating notification templates using Courier's elemental format, building channel-specific variants for email, Slack, push, and SMS, customizing brand styling through the API, iterating on design with test sends, getting team approval, and publishing with custom routing rules. The whole thing took a couple hours, mostly cold start and design iterations.

Debug Delivery Issues in Your AI Editor with MCP

Between quarterly audits, delivery issues don’t wait. When emails fail or alerts fire, you need answers fast. Courier’s MCP server lets you debug notifications conversationally—find the message, trace its timeline, and inspect user data in minutes. Instead of jumping between dashboards, your AI agent pulls everything on demand, surfaces root causes, and even automates investigations. The result: faster fixes, less guesswork, and a smarter, always-on reliability workflow.

How to build B2B customer journeys

In B2B the account is the unit of value, not the person. Twelve people share one login, the person who trips the event is rarely the one who should hear about it, and consumer lifecycle flows get all of that wrong. Here's how to build customer journeys in Courier that reason about accounts: account fields on the payload schema, the four trigger types, per-customer settings read from tenant data, a send node addressed to an admin instead of the user who clicked, experiments bucketed by account, and one call that cancels every run on an account the moment it converts.

Audit Notifications with Cursor or Claude Code

Most teams can't answer a basic question about their own product: what notifications are you sending, and are they working? This post walks through a full notification audit using Courier's CLI and MCP server from inside your coding environment. You'll inventory every template, pull delivery logs to surface failures, trace messages end to end, inspect rendered content for stale copy, map the data feeding each notification, break down delivery health by tenant, check preference coverage, and build a hit list of notifications to kill, revise, or batch. All from the command line. Takes about an afternoon.

Customer Journeys Then and Now

Most customer journey platforms don't use product data. They use marketing data. Open rates. Click-throughs. Maybe a segment based on what plan someone's on. That's not a journey. That's a drip campaign with extra steps. I spent years building behavior-based lifecycle programs at Yahoo. The decisioning was sophisticated. The organizational overhead to ship it was not. The infrastructure layer has finally caught up. Here's what behavior-based journeys looked like then, what most teams settled for, and what's actually possible now.

Give your AI agents access to your notification infrastructure with the Courier CLI

The rebuilt Courier CLI lets AI agents send notifications, debug delivery issues, and manage users, lists, and tenants across every channel. If your agent has shell access, it has access to Courier.

Best Email API Providers for Developers in 2026: SendGrid vs Postmark vs Mailgun vs SES vs Resend

Your email provider sticks with you longer than most technical decisions. Courier handles notification infrastructure for thousands of teams, so we went deep on the six email providers that show up most: SendGrid, Postmark, Mailgun, Amazon SES, Resend, and SMTP. This guide covers real API primitives, actual code from each provider's docs, Courier integration examples with provider overrides, and an honest read on where each developer experience holds up and where it breaks down. We also asked Claude to review every API and tell us which one it would wire up first. The answer surprised us.