
Warmerly
com.warmerlyPublished by warmerly.comOfficial publisherv1.0.0Updated Oct 24, 2026
Cold email outreach: find leads, launch campaigns, fix deliverability, answer replies.
Overview
Connects an AI assistant to a Warmerly workspace to find leads, run cold email campaigns, check deliverability, and handle replies.
- What you can do
- Warmerly is a remote MCP server that exposes a workspace's cold email outreach features to an assistant. Tools cover account and docs lookup, mailbox health and warmup settings, domain checks (SPF, DKIM, DMARC, MX) and placement tests, lead search, counting, email verification and finding, campaign creation, sequencing, launching, pausing and stats, inbox conversations with drafted or sent replies, and transactional email sending. Writes are logged in the workspace audit log.
- When to use it
- Use it when you want an assistant to run or inspect cold email outreach inside Warmerly: building lead lists, assembling and launching campaigns, diagnosing mailbox or domain deliverability problems, and triaging replies. It fits teams already using Warmerly who want those actions driven from a chat client.
- Requirements
- A remote streamable HTTP endpoint with OAuth 2.1 sign-in; no API key. You need a Warmerly account and must pick one workspace, which the connection is limited to. Any plan, including Free, can connect. Clients that only support local stdio servers need a bridge such as mcp-remote.
Installation
In SourceWeft
- Open Warmerly in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.warmerly%2Fwarmerly/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"warmerly": {
"type": "http",
"url": "https://app.warmerly.com/api/mcp"
}
}
}README
This repository has no README.
Tools
0Version history
1- v1.0.0LatestSep 26, 2026
Score
60% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.
