
Ballast
io.github.useballastPublished by GitHub account useballastv1.0.2Updated Oct 30, 2026
Cold email outreach: manage campaigns, lead sequences, mailbox warmup, and unified inbox replies.
Overview
Ballast connects an AI assistant to a cold email outreach workspace to manage campaigns, sequences, lead lists, mailbox warmup and inbox replies.
- What you can do
- Inspect workspace identity, aggregate performance, billing plan and sending limits
- Check domains and mailboxes: DNS and deliverability diagnostics, list or add sending domains and connected mailboxes
- Manage leads: search, import, list segments, and add do-not-contact suppressions
- Build and run campaigns: create, update, set sequences, enroll leads, preview distribution, check launch readiness, launch or pause, and read stats and analytics
- Handle the unified inbox: list and read threads, draft and send replies, apply sentiment labels
- When to use it
- Useful when you run cold email outreach in Ballast and want an assistant to draft sequences, audit domain and mailbox deliverability, review campaign metrics, or triage and answer replies without switching to the web app.
- Requirements
- A Ballast workspace account and an API key from Settings > API Keys (passed as BALLAST_API_KEY for the local npm package), or OAuth for the hosted remote endpoint. The local package needs Node.js 18 or newer; the remote endpoint needs network access.
Installation
In SourceWeft
- Open Ballast in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- 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/io.github.useballast%2Fballast-mcp/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.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"ballast": {
"type": "http",
"url": "https://ballast.to/api/mcp"
}
}
}README
Ballast MCP Server
[Ballast - Cold Email MCP server – quality and maintenance score on Glama] [Protocol] [License: MIT]
Official Model Context Protocol (MCP) server implementation for Ballast — connect AI agents to manage cold email campaigns, deliverability warmup, lead lists, and inbox replies.
This repository contains the standalone MCP server package that runs locally via standard I/O (stdio) and connects AI assistants (Claude Desktop, Cursor, Claude Code, Zed, etc.) to your Ballast workspace.
Features
- Deliverability & DNS Diagnostics: Inspect secondary domains for SPF, DKIM, DMARC alignment, MX configuration, and blacklist health.
- Campaign & Sequence Management: Build multi-step outbound sequences, set A/B variants, configure sending delays, and verify launch checklists.
- Automated Bounce Circuit Breakers: Monitor campaign placement rates and pause sends if bounce rate thresholds are crossed.
- Unified Inbox (Unibox): Read and summarize customer email threads, check sentiment classification, and draft human-confirmed replies.
- Safe by Default: Destructive operations (launching campaigns, sending emails, deleting data) require explicit two-step confirmation with a 10-minute HMAC token.
Installation & Setup
Requirements
- Node.js >= 18.0.0
- A Ballast workspace API key from Settings > API Keys (starts with
bl_).
Run via npx (Recommended)
You can run the server directly without manual installation:
Install from Source
Client Configuration
Claude Desktop
Add Ballast to your claude_desktop_config.json:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
Cursor
Add to ~/.cursor/mcp.json (or your project's .cursor/mcp.json):
Claude Code
(Note: For clients that support remote Streamable HTTP directly, you can also use --transport http ballast https://ballast.to/api/mcp --header "Authorization: Bearer bl_...")
Tools Reference
The server implements 30 core tools organized by functional area:
Safety: Two-Step Confirmations
To prevent inadvertent mass sends or data deletion:
- When calling
launch_campaign,send_reply, or deletion tools without aconfirm_token, the server generates a dry-run preview describing the exact outcome (e.g. "Will send 320 emails across 6 mailboxes") and issues an HMAC token. - The AI presents the preview to the user.
- The action executes only when the user approves and the AI passes the
confirm_token.
Development
License
MIT © Ballast
Source: README.md at commit e8fbd4f
Tools
0Version history
1- v1.0.2LatestOct 30, 2026
Score
85% 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
- License10 pts