MarleyFetch

com.marleyfetchPublished by marleyfetch.comOfficial publisherv1.0.0Updated Oct 24, 2026

Let AI agents send email from your own Gmail, Microsoft 365 or SMTP inbox, with guardrails.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

MarleyFetch lets an AI assistant send email from your own Gmail, Microsoft 365 or SMTP inbox, with guardrails built in.

What you can do
  • Send email from a connected Gmail, Microsoft 365 or SMTP mailbox on the user's behalf.
  • Apply guardrails around outgoing mail, as described in the provider's brief description.
  • No tool list is published, so the exact set of actions is not documented here.
When to use it
When you want an assistant to compose and send email from your own existing mailbox rather than a separate sending service, and you want some guardrails around what it sends.
Requirements
A remote MCP endpoint at the provider's API host, reached over streamable HTTP. OAuth authentication is required, so you need an account with the provider and a Gmail, Microsoft 365 or SMTP mailbox to connect. No environment variables or headers are declared.
Before you install
The server can send email from your real inbox, so messages go out under your identity to real recipients. OAuth grants it access to your mail account; review the scopes requested. The guardrails are only described in general terms, and no tool list or documentation is available here, so verify what it can actually do before connecting.

Installation

In SourceWeft

  1. Open MarleyFetch 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.marleyfetch%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": {
    "marleyfetch": {
      "type": "http",
      "url": "https://api.marleyfetch.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.0.0LatestSep 30, 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.