SimplyWarmup

com.simplywarmupPublished by simplywarmup.comOfficial publisherv0.1.0Updated Oct 25, 2026

Hosted MCP server for inbox health, reporting, and warmup operations.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

A hosted MCP server for SimplyWarmup that lets an assistant work with inbox health, reporting and email warmup operations.

What you can do
Connect an assistant to a SimplyWarmup account for inbox health, reporting and warmup operations. The manifest lists no individual tools, so the exact actions available are not documented here. It runs as a hosted remote endpoint rather than a local process.
When to use it
Relevant if you already use SimplyWarmup for email warmup and want an assistant to reach that account's inbox health, reporting and warmup data directly. Not useful without a SimplyWarmup account and API key.
Requirements
A remote MCP connection to the SimplyWarmup endpoint over streamable HTTP. A SimplyWarmup account and an API key copied from the developer settings page, sent in the X-SimplyWarmup-Api-Key header. Network access is required.
Before you install
The API key in the X-SimplyWarmup-Api-Key header is a secret that grants access to your SimplyWarmup account; keep it out of shared logs and configs. Warmup operations may change settings or sending behavior, so review actions before approving them. Account data is sent to the SimplyWarmup service.

Installation

In SourceWeft

  1. Open SimplyWarmup in the dashboard and add it to a workspace.
  2. Connect X-SimplyWarmup-Api-Key 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.simplywarmup%2Fsimplywarmup/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.

{
  "mcpServers": {
    "simplywarmup": {
      "type": "http",
      "url": "https://simplywarmup.com/mcp",
      "headers": {
        "X-SimplyWarmup-Api-Key": "<YOUR_API_KEY>"
      }
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

56% 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 listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • 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.