WarmySender

com.warmysenderPublished by warmysender.comOfficial publisherv1.1.0Updated Oct 24, 2026

AI-agent outreach: cold email, warmup, LinkedIn, Instagram, WhatsApp, verification, 200M leads

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

WarmySender is an outreach MCP server that lets an AI assistant run cold email, inbox warmup and multi-channel outreach campaigns across LinkedIn, Instagram and

What you can do
The manifest lists no tools, so capabilities come from the registry description only. It is positioned as AI-agent outreach covering cold email, inbox warmup, LinkedIn, Instagram and WhatsApp outreach, address verification, and a large lead database of roughly 200 million contacts. It is offered both as a remote endpoint and as a local npm package run with npx.
When to use it
Consider it when you want an assistant to help run outbound sales or marketing outreach and warmup across email and social channels, rather than for general-purpose tasks.
Requirements
An OAuth-authenticated WarmySender account; authentication is declared as required. It can be used as a remote endpoint or as a local process via the npm package run with npx, which needs Node.js. No environment variables or headers are declared.
Before you install
This is outreach tooling that sends messages on your behalf and works with a large lead database, so expect outbound sending, contact data handling and possible account or subscription costs. The manifest lists no tools, so review exactly what it can send or change before connecting. Credentials are handled through OAuth.

Installation

In SourceWeft

  1. Open WarmySender in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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.warmysender%2Fmcp/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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "warmysender": {
      "type": "http",
      "url": "https://warmysender.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.1.0LatestSep 16, 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.