The Winnr MCP server is an open-source Python package. Install with "uvx winnr-mcp" (Cursor and Claude Code) or add to your Claude Desktop config file. Set the WINNR_API_TOKEN environment variable to your Winnr API token. Once running, the AI sees 37 tools for managing domains, mailboxes, warming, and inbox — call them via natural language.
What "MCP" actually is
Model Context Protocol is a way for AI assistants to call external tools. Instead of you writing code that calls Winnr's API, the AI does it directly — you just describe what you want.
Example conversation with Claude, once MCP is set up:
You: Provision 3 new domains for a Q4 outreach campaign. Use .com TLDs. Then create 5 mailboxes on each with first names Sam, Alex, Jordan, Taylor, and Morgan. Enable warming on all of them.
Claude: [calls winnr_purchase_domain 3 times, waits for jobs, then winnr_create_email_user 15 times, then winnr_enable_warming across all 15 mailboxes]
That whole workflow takes about 60 seconds with MCP. Without MCP, you're either clicking through the UI or writing custom scripts.
When MCP is worth setting up
- AI SDR pipelines. Let an agent handle infrastructure provisioning end-to-end.
- Ops automation. Ask Claude to "audit my domain health" and get a full report without leaving the chat.
- One-off complex tasks. Bulk operations that don't fit the UI's bulk actions.
Security notes
- The MCP server holds an API token with your account's full permissions. Treat it like you would any privileged credential.
- Read/write scope is required for most tools. Use read-only if you only want the AI to read (safe for exploratory chats).
- Revoke the token any time from Settings → API Keys if you suspect it's leaked.
What's next
Step-by-step
-
1. Create a Winnr API token
Settings → API Keys → Create Token with read/write scope. Copy the token (starts with wnr_).
-
2. Add to Claude Desktop config
Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%/Claude/claude_desktop_config.json (Windows). Add — {"mcpServers": {"winnr": {"command": "uvx", "args": ["winnr-mcp"], "env": {"WINNR_API_TOKEN": "wnr_YOUR_TOKEN"}}}}
-
3. Restart Claude Desktop
Fully quit and reopen. The MCP server auto-connects on startup. You'll see the tools appear in Claude's tool list.
-
4. For Cursor
Add to ~/.cursor/mcp.json — {"mcpServers": {"winnr": {"command": "uvx", "args": ["winnr-mcp"], "env": {"WINNR_API_TOKEN": "wnr_YOUR_TOKEN"}}}}. Restart Cursor.
-
5. For Claude Code
Add to ~/.claude.json under mcpServers. Same shape as above. Reload Claude Code.
-
6. Test it
Ask the AI — 'List my Winnr domains.' It should call the winnr_list_domains tool and return your domain list. If it doesn't see the tool, restart the AI host and check WINNR_API_TOKEN is set correctly.
Frequently asked questions
What can the MCP server do?
37 tools — provision domains, create mailboxes, enable/tune warming, read metrics, export credentials, purchase marketplace domains, read the inbox, tag and organize. Full CRUD across every Winnr resource.
What AI hosts is it compatible with?
Anything that speaks the Model Context Protocol — Claude Desktop, Cursor, Claude Code, Windsurf. Others as they add MCP support.
Is the MCP server open source?
Yes — the source is on GitHub and the package is published on PyPI as winnr-mcp.
Do I need to pay extra for MCP?
No. MCP calls Winnr's regular API under the hood, so it uses your account's normal rate limit and doesn't add cost. The MCP server itself is free.
Can I self-host the MCP server?
Yes, it's a plain Python package. Run it however you want. Most people use uvx for zero-install convenience.