colding

app.coldingPublished by colding.appOfficial publisherv1.0.1Updated Oct 29, 2026

Send and read email through connected mailboxes. Warm them up, check addresses and run campaigns.

VerifiedStreamable HTTPWeb executableCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

Remote MCP server for Colding that lets an assistant send and read email from connected mailboxes, verify addresses, warm up mailboxes and run campaigns.

What you can do
  • Send and read email through connected mailboxes
  • Check email addresses for validity
  • Warm up mailboxes to build sending reputation
  • Run email campaigns
When to use it
Useful when an assistant should work inside an email outreach setup: drafting and sending mail, reading replies, validating recipient addresses, or managing mailbox warm-up and campaigns without leaving the chat.
Requirements
A remote MCP endpoint at api.colding.app over streamable HTTP. OAuth authentication is required, so a Colding account with connected mailboxes is needed. No environment variables or headers are declared.
Before you install
The server can send email and run campaigns, which means messages go out to real recipients and may incur costs or affect sender reputation. Mailbox warm-up and campaign actions change account state. Review what the assistant is allowed to send before connecting, and grant OAuth access only to the account you intend to use.

Installation

In SourceWeft

  1. Open colding 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/app.colding%2Fcolding/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": {
    "colding": {
      "type": "http",
      "url": "https://api.colding.app/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

2
  1. v1.0.1LatestOct 29, 2026
  2. v1.0.0Oct 21, 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.