Agents
Install Courier Skills in the tool you already use and it builds notifications the way an experienced Courier engineer would. Add the hosted MCP server when you want to test against your account.
Pick your tool
Courier Skills works in every tool that reads a SKILL.md. Each page has the install for that tool, what to build first, and how to add MCP for testing.
Install the Courier plugin and ship production-ready notifications from the terminal.
Install Courier Skills and ship production-ready notifications from Cursor's Agent mode.
Install Courier Skills and ship production-ready notifications from the Codex CLI or IDE extension.
Install Courier Skills and ship production-ready notifications from the VS Code chat panel.
Install Courier Skills and ship production-ready notifications from Windsurf's Cascade agent.
Install Courier Skills and ship production-ready notifications from Antigravity's IDE and CLI.
Install Courier Skills and ship production-ready notifications from Gemini CLI.
Install Courier Skills and ship production-ready notifications from Grok Build.
Install Courier Skills and ship production-ready notifications from OpenCode.
Install Courier Skills and ship production-ready notifications from Zed's agent panel.
Install Courier Skills and ship production-ready notifications from Warp's agent.
Put Courier Skills in the repo and let Devin ship production-ready notifications from its own environment.
What’s included
The skill does the building. The MCP server, the CLI, and the machine-readable docs are there when the agent needs to test, run, or look something up.
About 40 short guides plus a routing file that points your agent at the one or two it needs for the task: seven channels, transactional and growth patterns, routing, reliability, Inbox.
npx skills add trycourier/courier-skills
144 tools covering the full Courier API, for testing and prototyping: publish to your test workspace, send yourself a test, read the delivery events. Hosted, authenticated with your API key in a header. Nothing to run locally.
https://mcp.courier.com
The full Courier API in the terminal your agent already uses: send messages, manage users, inspect delivery logs.
npm install -g @trycourier/cli
Machine-readable docs. Point your agent at llms.txt for the map, llms-full.txt for everything in one file, or add .md to any docs URL to get that page as Markdown.
https://www.courier.com/docs/llms.txt
For agents
Do these in order. Everything you need is linked or pasteable.
# Courier for agents 1. Read https://www.courier.com/docs/llms.txt for the documentation index. 2. Install the skill: npx skills add trycourier/courier-skills Then open SKILL.md; its routing table maps each task to the one or two guides to load. 3. Build against the Courier SDKs and API. Use the test-environment API key. 4. To test what you built: connect to https://mcp.courier.com over MCP with header api_key: <test key>. 144 tools. Send a test, then read the delivery events. 5. New workspace, nothing set up yet: https://www.courier.com/docs/get-started/send-a-message
FAQ
Any tool that reads a skills directory or a SKILL.md can use Courier Skills, and any MCP client can connect to the hosted server. Courier documents the install for Claude Code, Cursor, Codex, VS Code, Windsurf, Antigravity, Gemini CLI, Grok Build, OpenCode, Zed, Warp, and Devin.
A routing file plus about 40 reference guides covering seven channels, transactional and growth patterns, routing, reliability, and Inbox. Your agent reads the router first and loads only the one or two guides a task needs. Install it with npx skills add trycourier/courier-skills.
Not to build. The skill is enough for your agent to write templates, routing, journeys, and Inbox code in your repo. Add the MCP server when you want to test and prototype against your Courier account from the editor: publish to your test workspace, send yourself a test, read the delivery events.
Yes. Every Courier workspace has separate test and production environments, each with its own API key. Let the agent build and experiment with the test key, then switch to the production key when you're ready to ship. It works the same way in both environments.
Yes. courier.com/docs/llms.txt is a structured index of every docs page, courier.com/docs/llms-full.txt is the full documentation in one file, and any docs URL with .md appended returns that page as Markdown.