Winnr — Claude Code MCP server: domains, mailboxes, warming
Hooks Winnr's cold-email stack into your agent: buy domains, spin up mailboxes, set DNS, run warming and read replies from plain prompts.
claude mcp add --transport http winnr https://mcp.winnr.app/mcpWhat Winnr does
Winnr is an MCP server for the Winnr cold-email infrastructure API. Your assistant handles domains and SMTP mailboxes, writes DNS records, kicks off warming, triages the inbox and browses the pre-warmed marketplace. It ships 55 tools, 26 of them read-only, along with 8 resources and 5 prompt playbooks.
Two ways in. The hosted endpoint https://mcp.winnr.app/mcp signs you in through Winnr with OAuth 2.1 and PKCE, and needs no local install. The local route runs uvx winnr-mcp over stdio, which means uv on the machine and an API token in the config file. Tokens begin with wnr_. A read-only token hides every tool that creates, sends or deletes; WINNR_NO_PURCHASES keeps write access while dropping the four tools that bill the card.
Money never moves in one call. Domain purchases, pre-warmed purchases and enabling warming first return a live quote with exact prices and a confirmation_token good for 10 minutes, and the order only goes through after you say yes. The quote is recalculated at that point. On startup the server hits GET /v1/account; a bad token kills it right there, which beats a process that stays up and fails every call.
What it helps with
- buy a sending domain without leaving the chat
- create SMTP mailboxes and publish DNS records
- start warming and track its progress
- sort incoming replies into buckets
- check how much account capacity is left
Example prompts for the agent
- What's in my Winnr account and how much capacity do I have left?
- Buy a domain for this project and show me the quote first
- Create mailboxes on the new domain and turn on warming
How to install Winnr
Platform CLI: remote server
claude mcp add --transport http winnr https://mcp.winnr.app/mcpPlatform CLI: remote server
codex mcp add winnr --url https://mcp.winnr.app/mcpConfig file
{
"mcpServers": {
"winnr": {
"url": "https://mcp.winnr.app/mcp"
}
}
}Config file
{
"servers": {
"winnr": {
"type": "http",
"url": "https://mcp.winnr.app/mcp"
}
}
}Platform CLI: remote server
gemini mcp add -t http winnr https://mcp.winnr.app/mcpStep by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about Winnr
How do I install Winnr in Claude Code?
Run claude mcp add --transport http winnr https://mcp.winnr.app/mcp. Then /mcp in Claude lists Winnr as connected.
What does Winnr do?
It exposes the Winnr cold-email API to your assistant: domains, mailboxes, DNS, warming, inbox, the pre-warmed marketplace and webhooks.
Can I keep the assistant read-only?
Yes. Use a read-only token and the tools that create, send, buy or delete stay hidden. WINNR_NO_PURCHASES is the middle ground: writes allowed, spending tools gone.
