Overview
Use the Model Context Protocol (MCP) to control SalesBlink directly from your AI assistant. Create lists, launch sequences, check replies, and track reports through natural language commands.
SalesBlink MCP uses OAuth 2.1. Add the MCP endpoint to your client, then sign in to SalesBlink and approve the connection in your browser. No API key is required or accepted for MCP connections.
Prerequisites
- MCP-compatible AI client: Cursor, Claude Desktop, ChatGPT, Perplexity, VS Code, Windsurf, Zed, or another supported client.
- Node.js installed: Required only for clients that need the
mcp-remotebridge.
Step 1: Add the MCP endpoint
Use this endpoint in every configuration:
https://mcp.salesblink.io/mcp
Step 2: Sign in and approve access
- Restart your AI client after saving the configuration.
- When prompted, sign in to SalesBlink in your browser.
- Approve the connection, then return to your AI client.
Client configurations
Cursor
Add this to ~/.cursor/mcp.json or .cursor/mcp.json:
{
"mcpServers": {
"salesblink": {
"url": "https://mcp.salesblink.io/mcp",
"transport": "streamable-http"
}
}
}
Windsurf
Add this to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"salesblink": {
"serverUrl": "https://mcp.salesblink.io/mcp"
}
}
}
Zed
Add this to ~/.config/zed/settings.json:
{
"context_servers": {
"salesblink": {
"enabled": true,
"url": "https://mcp.salesblink.io/mcp"
}
}
}
Claude Desktop
In Claude Desktop, go to Customize → Connectors → Add custom connector, enter https://mcp.salesblink.io/mcp, then complete the SalesBlink sign-in flow.
If Connectors are unavailable, use the fallback in Connect SalesBlink to Claude Desktop.
ChatGPT
In ChatGPT, go to Settings → Connectors, add a custom connector named SalesBlink with the URL https://mcp.salesblink.io/mcp, then sign in to SalesBlink. See Use SalesBlink with ChatGPT.
Perplexity
In Perplexity, add a custom connector (remote MCP server) with the URL https://mcp.salesblink.io/mcp. When prompted, sign in to SalesBlink and approve access.
Codex
Add this to ~/.codex/config.toml:
[mcp_servers.salesblink]
url = "https://mcp.salesblink.io/mcp"
Claude Code
claude mcp add --transport http salesblink "https://mcp.salesblink.io/mcp"
VS Code (Cline or Roo Code)
{
"mcpServers": {
"salesblink": {
"url": "https://mcp.salesblink.io/mcp",
"type": "streamableHttp"
}
}
}
GitHub Copilot
Add this to ~/.copilot/mcp-config.json:
{
"mcpServers": {
"salesblink": {
"type": "http",
"url": "https://mcp.salesblink.io/mcp",
"tools": ["*"]
}
}
}
JetBrains AI Assistant
{
"mcpServers": {
"salesblink": {
"url": "https://mcp.salesblink.io/mcp"
}
}
}
OpenHands
openhands mcp add salesblink --transport http "https://mcp.salesblink.io/mcp"
Kimi Code and Kilo Code
Kimi Code:
{
"mcpServers": {
"salesblink": {
"url": "https://mcp.salesblink.io/mcp"
}
}
}
Kilo Code:
{
"mcp": {
"salesblink": {
"type": "remote",
"url": "https://mcp.salesblink.io/mcp",
"enabled": true
}
}
}
Other stdio-first clients
Use this bridge configuration when your client cannot connect to a remote MCP URL directly:
{
"mcpServers": {
"salesblink": {
"command": "npx",
"args": [
"-y",
"mcp-remote@latest",
"https://mcp.salesblink.io/mcp",
"--transport",
"http-only"
]
}
}
}
Verify the connection
Ask your AI assistant "Show me my SalesBlink lists" or "What sequences are running?" It should respond with live data from your SalesBlink account.
Safety rules
SalesBlink MCP has built-in safeguards that apply in every AI client:
- No attachments. Templates, replies, and forwards sent through MCP can't include files. The error reads
Attachments are not supported on this connector. To send files, attach them via the SalesBlink web app. - Confirmation for risky actions. The AI asks you to confirm before it launches or resumes a sequence, deletes an inbox placement test, revokes an API key, or removes entries from your blocklist.
- Consent basis for new contacts. When adding contacts, the AI must state where they came from. Accepted values are
opt_in_list,crm_export,inbound_lead,existing_customer,partner_referral,event_or_webinar,market_research, andlead_search_tools. Requests without a consent basis are rejected.
Troubleshooting
Connection failed
- Confirm the endpoint is exactly
https://mcp.salesblink.io/mcp. - Do not add
api_keyor any other credentials to the endpoint URL. - Restart your client after changing its configuration.
Unauthorized API Key or 401 error
If tool calls fail with SalesBlink API Error: Unauthorized API Key or a 401 error, your client is still using an old API-key MCP configuration, for example an endpoint like https://mcp.salesblink.io/mcp?api_key=YOUR_KEY. SalesBlink MCP no longer accepts API keys, so these configurations return 401.
To fix it:
- Open your client's MCP configuration.
- Remove the
?api_key=part and any API key arguments or environment variables for SalesBlink. - Set the endpoint to exactly
https://mcp.salesblink.io/mcp, using the configuration for your client above. - Restart your client and complete the OAuth sign-in in Step 2: Sign in and approve access.
Note: Generating a new API key does not fix this error. MCP connections only work through the OAuth sign-in.
Authorization did not open
- Run a SalesBlink command again to trigger the OAuth sign-in flow.
- Reconnect the SalesBlink server in your client's MCP settings.
Bridge connection failed
- Confirm Node.js is installed and available in your PATH.
- Use
mcp-remote@latestwith--transport http-only.
Frequently Asked Questions
Do I need an API key to use SalesBlink MCP?
No. SalesBlink MCP uses OAuth 2.1 and authorizes your SalesBlink account through your browser.
Which AI tools are compatible with SalesBlink MCP?
SalesBlink MCP works with OAuth-capable MCP clients such as Claude, ChatGPT, Perplexity, Cursor, Codex, Windsurf, and current versions of many other MCP clients.