Articles on: SalesBlink AI

Connect SalesBlink MCP to Your AI Tool

title: Connect SalesBlink MCP to Your AI Tool
description: Control SalesBlink from any MCP-compatible AI assistant.

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


  • Active SalesBlink account: Sign up at https://run.salesblink.io/signup if you do not have one.
  • MCP-compatible AI client: Cursor, Claude Desktop, VS Code, Windsurf, Zed, or another supported client.
  • Node.js installed: Required only for clients that need the mcp-remote bridge.


Step 1: Add the MCP endpoint


Use this endpoint in every configuration:


https://mcp.salesblink.io/mcp


Step 2: Sign in and approve access


  1. Restart your AI client after saving the configuration.
  2. When prompted, sign in to SalesBlink in your browser.
  3. 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.


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.


Troubleshooting


Connection failed


  • Confirm the endpoint is exactly https://mcp.salesblink.io/mcp.
  • Do not add api_key or any other credentials to the endpoint URL.
  • Restart your client after changing its configuration.


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@latest with --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, Cursor, Codex, Windsurf, and current versions of many other MCP clients.

Updated on: 01/09/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!