Anymail

io.github.creathinkonePublished by GitHub account creathinkonev1.0.0Updated Oct 29, 2026

Cold email outreach: manage prospects, campaigns, replies and webhooks in Anymail.

VerifiedStreamable HTTPWeb executableCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

Remote Anymail MCP server that lets an assistant manage cold email outreach: prospects, campaigns, replies and webhooks.

What you can do
  • Manage prospects in Anymail outreach lists
  • Create and manage cold email campaigns
  • Review and handle replies from prospects
  • Manage webhooks for outreach events
  • Tool-level details are not published in the registry entry, so exact actions are unconfirmed.
When to use it
Useful when you run cold email outreach through Anymail and want an assistant to work with prospects, campaigns, replies and webhooks without switching to the web app.
Requirements
A remote MCP endpoint at app.anymail.watch over streamable HTTP; OAuth sign-in is required. No environment variables or headers are declared. An Anymail account with outreach data is implied.
Before you install
The server can act on live outreach data, so expect it to create or change prospects, campaigns and webhooks and to send email to real contacts. OAuth grants access to your Anymail account; review the scopes before authorizing. Outreach content and contact data are handled by a third-party service.

Installation

In SourceWeft

  1. Open Anymail 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/io.github.creathinkone%2Fanymail/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": {
    "anymail": {
      "type": "http",
      "url": "https://app.anymail.watch/api/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.0.0LatestOct 29, 2026

Score

83% 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
  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.