@warmysender/mcp
v1.0.2
Published
WarmySender MCP server launcher. Connects AI assistants (Claude Desktop, Claude Code, Cursor, Windsurf, Zed) to your WarmySender workspace over the Model Context Protocol.
Maintainers
Readme
@warmysender/mcp
Official launcher for the WarmySender MCP server.
Connects AI assistants — Claude Desktop, Claude Code, Cursor, Windsurf, Zed — to your WarmySender workspace so they can manage cold email campaigns, warmup mailboxes, LinkedIn outreach, and prospects with natural language.
Quick start
Claude Code
claude mcp add warmysender -- npx -y @warmysender/mcp --api-key=ws_YOUR_API_KEYClaude Desktop
Add to claude_desktop_config.json:
{
"mcpServers": {
"warmysender": {
"command": "npx",
"args": ["-y", "@warmysender/mcp", "--api-key=ws_YOUR_API_KEY"]
}
}
}Cursor / Windsurf / Zed
Same npx -y @warmysender/mcp --api-key=ws_... command in each client's MCP server config.
Get an API key
- Sign in at https://warmysender.com
- Settings → API Keys → Create new key
- Pick the scopes you want to expose (e.g.
campaigns:read,linkedin:read,warmup:write)
OAuth (no API key needed)
If you omit --api-key, the launcher falls back to the OAuth 2.1 flow. Your AI client will open a browser window to warmysender.com for consent; the resulting access token is stored by mcp-remote and reused on subsequent runs.
What's available
- 30+ tools across campaigns, warmup, LinkedIn, prospects, suppressions
- All actions route through the same schedulers as the UI — LinkedIn safety limits, warmup ramp, and per-mailbox pacing are enforced identically
- No
delete_*, no direct-send, no account-connect tools (those stay in the UI by design)
Full tool list, scope map, and safety invariants: https://warmysender.com/mcp
Environment variables
WARMYSENDER_API_KEY— alternative to--api-keyWARMYSENDER_MCP_URL— override the server URL (defaults tohttps://warmysender.com/mcp); useful for self-hosted or staging
License
MIT
