Conduit Mail

app.conduitmailPublished by conduitmail.appOfficial publisherv1.0.0Updated Oct 24, 2026

Your mailbox for MCP clients: search, read, draft, send, rules and notes. Sending is off by default.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

A remote mailbox service for MCP clients that lets an assistant search, read, draft and send email, plus manage rules and notes.

What you can do
Search and read messages in the connected mailbox, including notes kept alongside them. Create and edit drafts, and send mail when sending has been enabled. Manage mailbox rules that organize or route incoming messages. Sending is turned off by default, so the assistant can prepare mail without delivering it until that is changed.
When to use it
Useful when you want an assistant to triage an inbox, summarize or find messages, prepare drafts for review, or apply mailbox rules, without building your own mail integration.
Requirements
A remote MCP endpoint reached over streamable HTTP at the provider's connect host, with OAuth sign-in required. No packages, environment variables or headers are declared.
Before you install
The server works on a real mailbox: it can read message contents, create drafts, change rules and notes, and send email once sending is enabled. Sending is off by default, so check that setting before relying on it as a safeguard. OAuth grants the server access to the connected account, so review the scopes shown at sign-in.

Installation

In SourceWeft

  1. Open Conduit Mail 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.conduitmail%2Fconduit-mail/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": {
    "conduit-mail": {
      "type": "http",
      "url": "https://connect.conduitmail.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

1
  1. v1.0.0LatestSep 16, 2026

Score

67% 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.

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