Launch Cold Email Outreach Sequences & more from your favourite AI tools & agents.
Works With
Everything you need for a successful cold outreach campaign is available for your AI.
Build, update and archive lists, and add up to 500 contacts at a time.
Create, clone, launch, pause and report on multi-step outreach campaigns.
Look up a lead, move them between lists, read their history and unsubscribe them.
Read threads, reply, forward and update outcomes without leaving your chat.
Draft and edit HTML email templates and keep the library tidy.
Connect mailboxes, reconnect broken ones, and check sender health and warmup.
Run placement tests and see whether you are landing in inbox, promotions or spam.
Pull overall or daily numbers, per-mailbox stats and raw send, open, click and reply events.
Check, add and clear blocked addresses and domains before you send.
Search domains and order done-for-you domains and mailboxes for scaling outreach.
Switch workspaces, invite teammates, organise folders and manage API keys.
One secure endpoint, 100+ tools, and no API keys to copy around
Paste https://mcp.salesblink.io/mcp into any MCP
client
Your client opens SalesBlink login and consent over OAuth 2.1
Every SalesBlink tool loads into your assistant, scoped to your workspace
"Launch my Welcome sequence to the SaaS Founders list" — and it runs
Step-by-step instructions to connect SalesBlink MCP with your favorite AI clients
Most MCP clients use this JSON configuration. Copy this block and paste it into your client's configuration file:
{
"mcpServers": {
"salesblink": {
"url": "https://mcp.salesblink.io/mcp",
"transport": "streamable-http"
}
}
}
SalesBlink and paste the server URL:
https://mcp.salesblink.io/mcp
codex mcp add salesblink --url https://mcp.salesblink.io/mcp
Open your Codex configuration file:
~/.codex/config.toml
.codex/config.toml
[mcp_servers.salesblink]
url = "https://mcp.salesblink.io/mcp"
https://mcp.salesblink.io/mcp
~/Library/Application
Support/Claude/claude_desktop_config.json
%APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"salesblink": {
"command": "npx",
"args": [
"-y",
"mcp-remote@latest",
"https://mcp.salesblink.io/mcp",
"--transport",
"http-only"
]
}
}
}
claude mcp add --transport http salesblink https://mcp.salesblink.io/mcp
Restart your terminal or run /mcp inside Claude
Code to verify.
{
"mcpServers": {
"salesblink": {
"url": "https://mcp.salesblink.io/mcp",
"transport": "streamable-http"
}
}
}
Prefer skills? Add the SalesBlink tap and install the cold email skill:
hermes skills tap add open-salesblink/skill
hermes skills install cold-email-salesblink
Then set SALESBLINK_API_KEY in your environment
using an API key from SalesBlink → Integrations → API.
Full guide
mcp-remote bridge
{
"mcpServers": {
"salesblink": {
"command": "npx",
"args": [
"-y",
"mcp-remote@latest",
"https://mcp.salesblink.io/mcp",
"--transport",
"http-only"
]
}
}
}
openclaw skills install cold-email-salesblink
Then set SALESBLINK_API_KEY in your environment
using an API key from SalesBlink → Integrations → API.
Full guide
·
Skill page
SalesBlink and paste the server URL:
https://mcp.salesblink.io/mcp
streamable-http if you are asked for a
transport, then sign in to SalesBlink and approve access
If you manage Manus MCP servers through a config file, add:
{
"mcpServers": {
"salesblink": {
"url": "https://mcp.salesblink.io/mcp",
"transport": "streamable-http"
}
}
}
For any other client conforming to the standard MCP specification:
mcp.json or
config.json file in the tool's root directory or
~/.config/ folder
"mcpServers" objectmcp-remote@latest:
Need Node.js? Download (LTS) · Step-by-step setup
{
"mcpServers": {
"salesblink": {
"command": "npx",
"args": [
"-y",
"mcp-remote@latest",
"https://mcp.salesblink.io/mcp",
"--transport",
"http-only"
]
}
}
}
Everything you need to know about SalesBlink MCP
SalesBlink MCP is a remote Model Context Protocol server that connects AI assistants - ChatGPT, Claude, Codex, Manus and any other MCP-compatible client - directly to your SalesBlink account. Once it is connected, your assistant can build lists, launch cold email sequences, read replies and pull reporting for you in plain language, instead of you clicking through the app. The server URL is https://mcp.salesblink.io/mcp.
Any client that speaks MCP. The setup guide on this page walks through ChatGPT and Codex, Claude Desktop, Claude Code, Hermes Agent, OpenClaw and Manus step by step, and the same server URL works in Cursor, Windsurf, Zed, VS Code (Cline or Roo Code), GitHub Copilot, JetBrains IDEs, Gemini CLI, OpenCode, Kimi Code, Kilo Code and anything else that supports remote MCP servers.
Just about anything you do in the SalesBlink app: create and update lists, add contacts, build templates, launch and pause sequences, read and reply to inbox threads, track opens, clicks and replies, pull analytics, run inbox placement tests, manage email senders and warmup, work with your blocklist, order domains and mailboxes, and switch between workspaces.
No. The MCP endpoint uses OAuth 2.1, so your client sends you to the normal SalesBlink login and consent screen the first time you use it and no secret is stored in your config file. API keys are not accepted at https://mcp.salesblink.io/mcp at all. They are still used elsewhere: for the SalesBlink public REST API, and for the Hermes Agent and OpenClaw skill installs, which read a SALESBLINK_API_KEY environment variable.
Create a SalesBlink account at run.salesblink.io, add https://mcp.salesblink.io/mcp to your AI client using the setup guide above, and sign in when the consent screen appears. Then just ask - for example, “Launch my Welcome sequence to the SaaS Founders list” - and your assistant does the rest.
Access is scoped to you. The OAuth flow asks only for openid, email and offline_access; access tokens last 15 minutes and refresh tokens roll on a 60-day sliding window. Every tool call is re-checked against your SalesBlink workspace membership, role and plan, so an assistant can never reach data you cannot reach yourself. Tools are also labelled read- only or destructive, which lets your client warn you before anything is changed or sent.
The one you name. You can pin a workspace for the session, or pass a workspace ID with a single request; if you do neither, your default workspace is used, and when that is ambiguous the server asks you to choose from the workspaces you belong to. Any workspace ID your assistant supplies is validated against your real memberships before anything runs.
Yes. Install Node.js and connect through the mcp-remote bridge instead - the “All Other MCP Clients” section of the setup guide above has the exact configuration to copy. The same approach covers Claude Desktop without Connectors and other stdio-only tools.
Remove the SalesBlink MCP server in your AI client and it revokes its token on the way out. Access tokens expire within 15 minutes in any case, and a refresh token stops working after 60 days without use. If you need access cut off straight away, contact SalesBlink support.
No. Setup is pasting one URL into your AI tool, and after that you talk to it normally: “Show me replies from this week”, “Create a list called Marketing Agencies in New York”, “Run an inbox placement test for outreach@mycompany.com”. Your assistant works out which tools to call.