Add https://mcp.winnr.app/mcp as a custom connector (Claude) or MCP server (ChatGPT, Cursor, Windsurf, VS Code, Claude Code), then sign in with Winnr and choose what the assistant may do. There's nothing to install and no API key to manage. The assistant then has 55 tools for domains, mailboxes, warming, the inbox, the pre-warmed marketplace and webhooks. A local version (uvx winnr-mcp with an API token) is also available for desktop apps. The AI Assistants page in the app (app.winnr.app/mcp) walks you through each assistant.
Two ways to connect
Hosted (recommended). Add https://mcp.winnr.app/mcp as a connector, sign in with Winnr, and choose what the assistant may do. Works with claude.ai on web and mobile, ChatGPT and every desktop client. Nothing to install, no API key to keep safe, and you can revoke it from the API page at any time.
Local. Run the open-source package on your own machine with an API token: uvx winnr-mcp. Desktop apps only. Use it if you want the server in your own environment. Setting WINNR_READ_ONLY=true shows only read tools, and WINNR_NO_PURCHASES=true keeps write access but hides the four tools that charge your card.
The AI Assistants page in the app (app.winnr.app/mcp) has copy-paste steps for Claude, ChatGPT, Claude Desktop, Claude Code, Cursor, Windsurf and VS Code, for both options.
Local config example
For Claude Desktop (Settings, Developer, Edit Config), Cursor (~/.cursor/mcp.json) and Windsurf, add:
{
"mcpServers": {
"winnr": {
"command": "uvx",
"args": ["winnr-mcp"],
"env": { "WINNR_API_TOKEN": "wnr_YOUR_TOKEN" }
}
}
}
Then fully quit and reopen the app. uvx comes with uv. If you don't have it, install uv first, or run pip install winnr-mcp and use "command": "winnr-mcp" with no args.
What "MCP" actually is
Model Context Protocol is a standard way for AI assistants to call external tools. Instead of you writing code against Winnr's API, the assistant calls it for you. You describe what you want.
Example conversation once Winnr is connected:
You: Buy 3 new .com domains for a Q4 outreach campaign. Create 5 mailboxes on each with the first names Sam, Alex, Jordan, Taylor and Morgan. Then turn on warming for all of them.
Assistant: [checks availability and prices with winnr_search_domains_bulk, shows you the total and asks you to confirm, buys them with winnr_purchase_domains, waits for the jobs with winnr_wait_for_job, creates the mailboxes with winnr_bulk_create_email_users, then quotes and, after you confirm, enables warming with winnr_enable_warming]
When MCP is worth setting up
- AI SDR pipelines. Let an agent handle infrastructure end to end.
- Ops checks. Ask for a health report on your domains and mailboxes without leaving the chat.
- Reply triage. Have the assistant read your inbox across all mailboxes and flag the replies that need you.
- One-off bulk jobs. Operations that don't fit the app's bulk actions.
Security notes
- The connection can only do what you granted when you signed in (or what the token's permissions allow when running locally). Grant view-only for exploratory chats.
- Only four tools charge your card, and all four require a quote and your explicit confirmation first.
- Every hosted connection is backed by a token named "MCP ·
" on the API page. Revoke it there if you want to cut an assistant off.
What's next
- Set it up in the app: guided steps for each assistant, with a connection check
- Create an API token
- MCP GitHub repo
- Winnr MCP page
Step-by-step
-
1. Open the AI Assistants page in the app
In the app sidebar, click AI Assistants (or go to app.winnr.app/mcp). Pick your assistant and follow the steps it shows. The page shows Connected once your assistant makes its first call.
-
2. Add the connector (hosted, recommended)
In Claude (web, mobile or desktop) go to Settings, Connectors, Add custom connector, and paste https://mcp.winnr.app/mcp. In ChatGPT use Settings, Apps & Connectors (called Connectors in older builds), Advanced settings, Developer mode, then Create, and choose OAuth. In Cursor, Windsurf or VS Code add an MCP server with that URL. In Claude Code run: claude mcp add --scope user --transport http winnr https://mcp.winnr.app/mcp. Then click Connect.
-
3. Sign in and choose access
Your browser opens Winnr. Choose what the assistant may do (See your infrastructure, Make changes on your behalf, Spend money from your card), approve, and you're returned to the assistant.
-
4. Or run it locally with an API token
Create a token on the API page (Read and Write, or Read only if the assistant should only report). Then add the server to your app's MCP config: command uvx, args ["winnr-mcp"], env WINNR_API_TOKEN=wnr_YOUR_TOKEN. For Claude Code: claude mcp add --scope user winnr -e WINNR_API_TOKEN=wnr_YOUR_TOKEN -- uvx winnr-mcp. Restart the app afterwards.
-
5. Test it
Ask the assistant to list your Winnr domains. It should call the winnr_list_domains tool and return your domains. If it can't see the tools, reconnect the connector (hosted) or restart the app and check the token (local).
Frequently asked questions
Do I need to install anything?
No. The hosted server at https://mcp.winnr.app/mcp is added as a connector and you sign in with your Winnr login. A local install (uvx winnr-mcp with an API token) is available for desktop apps if you prefer to run it yourself.
Does it work with ChatGPT and the Claude mobile app?
Yes, through the hosted server. Anything that supports remote MCP connectors can use it: claude.ai on web and mobile, ChatGPT developer-mode connectors, Claude Desktop, Claude Code, Cursor, Windsurf and VS Code.
Can the AI spend my money without asking?
No. The four tools that charge your card (buying domains, buying one or several pre-warmed domains, and enabling warming) are two-step. The first call only returns a quote with exact prices. Nothing is charged until the assistant calls again with your confirmation, and if the price or availability changed in between, the purchase is refused with a fresh quote. You can also connect without the spend permission, and those tools are then hidden entirely.
What access levels can I grant?
Three, chosen when you sign in. See your infrastructure (list and inspect everything, always included), Make changes on your behalf (create, change, send and delete), and Spend money from your card (buy domains, buy pre-warmed domains, enable warming). The assistant only sees the tools its access allows.
How do I disconnect an assistant?
Go to the API page in Winnr and revoke the token named "MCP ·
What can the MCP server do?
55 tools, 26 of them read-only. Search and buy domains, connect your own domains, check DNS, create and update mailboxes, enable and tune warming, read metrics, export credentials, read and send from the inbox, browse and buy pre-warmed domains, manage webhooks, and track jobs. It also includes ready-made prompts for setup, health checks, reply triage, connecting your own domain and scaling up.
Can a view-only connection export credentials?
No. Exports contain mailbox passwords, so they need Make changes on your behalf (or a Read and Write token when running locally).
What AI hosts is it compatible with?
Anything that speaks the Model Context Protocol. Hosted: claude.ai web and mobile, ChatGPT, Claude Desktop, Claude Code, Cursor, Windsurf, VS Code. Local: any desktop client that runs local (stdio) servers.
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, so it uses your account's normal rate limit and costs nothing extra. You only pay for what you buy through it, the same as in the app.
Can I self-host the MCP server?
Yes. It's a Python package. Most people run it with uvx, or install it with pip install winnr-mcp.