Connect Nitrosend to VS Code via MCP. Campaigns, contacts, flows. All from GitHub Copilot Chat. It is one of several editor and agent integrations that all speak to the same account.
If you haven't already, install the GitHub Copilot Chat extension in VS Code. MCP support ships with it.
Open Copilot's MCP settings and add nitrosend with command npx -y @nitrosend/mcp. Sign in with your Nitrosend account when prompted.
Ask Copilot to create campaigns, import contacts, or send emails. Nitrosend handles the rest.
"Use Nitrosend to create a campaign announcing our new pricing. Target the active-customers segment. Friendly, concise tone."
"Use Nitrosend to import the contacts from /data/leads.csv into a new list called Q1 Signups."
"Use Nitrosend to show me open and click rates for the last 5 campaigns. What can we improve?"
"Use Nitrosend to set up a welcome flow. Send a hello email immediately, then a product guide 3 days later."
"Use Nitrosend to create a segment of users who opened the last 3 campaigns but haven't purchased."
"Use Nitrosend to send a test of that campaign to [email protected] so I can review it."
Stay in your editor. No browser tabs, no dashboard. Copilot runs the platform directly.
Describe what you want. Copilot translates intent into calls against the Nitrosend email API. You never learn a new UI.
Nitrosend is MCP-first. Every capability is a tool Copilot can call. The most capable email MCP server available.
The same MCP server backs the other editors, so a team split across Cursor, Codex and Claude Cowork shares one set of campaigns and contacts. If you would rather drive it from a terminal, the Nitrosend CLI takes the same commands.
Receipts, resets and confirmations, and why they are the most-read mail you send.
The short glossary entry if you only need the definition.
What decides whether the mail your agent sends actually lands.
SPF, DKIM and DMARC, set up once on your sending domain.