Sendhustle Mcp

io.github.AchleshaPublished by GitHub account Achleshav1.0.2Updated Oct 24, 2026

Send and manage email via the SendHustle API — emails, domains, contacts, audiences, campaigns.

VerifiedSTDIODesktop onlyCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

Local MCP server that lets an assistant send and manage email through the SendHustle API: emails, domains, contacts, audiences and campaigns.

What you can do
Send email through the SendHustle API, with an optional default sender address on a verified domain. Manage sending domains and verified sender identities. Manage contacts and audiences used for outreach. Work with campaigns alongside the underlying email, domain and contact records.
When to use it
Worth adding when you want an assistant to draft and send email or keep SendHustle contacts, audiences and campaigns up to date from within a chat, rather than switching to the SendHustle dashboard.
Requirements
Runs locally as an npm package over stdio, so it needs Node.js on the user's machine and network access to the SendHustle API. Requires a SendHustle API key supplied in the SENDHUSTLE_API_KEY environment variable. Optionally set SENDER_EMAIL_ADDRESS to a default sender on a verified domain.
Before you install
The API key in SENDHUSTLE_API_KEY is a secret with access to your SendHustle account; keep it out of shared logs and configuration. The server can send real email and change domains, contacts, audiences and campaigns, so actions may reach recipients or alter live data. Sending may incur costs or affect sender reputation depending on your SendHustle plan.

Installation

In SourceWeft

  1. Open Sendhustle Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.2LatestSep 17, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

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

  • License10 pts

    Declare a license in the repository or the registry entry.