Koskamo

Leads Ranger MCP

The Leads Ranger MCP server enables AI assistants like Claude, ChatGPT, and Gemini to integrate directly with the Leads Ranger platform. It allows users to discover local business leads, find verified emails, draft and manage multi-channel outreach campaigns, and handle reply management through natural language conversations, all while maintaining user approval for every action.

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

Leads Ranger MCP logo, by Leads RangerOAuth sign-inEndpoint checked 2026-10-20Operated by Leads Ranger
MCP endpoint (Streamable HTTP)
https://app.leadsranger.com/mcp
Vendor documentation

What you can do with it

  • Find local businesses and extract verified emails for outreach
  • Draft and preview multi-channel email campaigns before sending
  • Summarize waiting replies and suggest deal stages
  • Identify blocked campaigns and troubleshoot setup issues

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http leads-ranger-mcp https://app.leadsranger.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add leads-ranger-mcp --url https://app.leadsranger.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable leads-ranger-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "leads-ranger-mcp": {
      "url": "https://app.leadsranger.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.
Cline configuration
{
  "mcpServers": {
    "leads-ranger-mcp": {
      "type": "streamableHttp",
      "url": "https://app.leadsranger.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start leads-ranger-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "leads-ranger-mcp": {
      "type": "http",
      "url": "https://app.leadsranger.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http leads-ranger-mcp https://app.leadsranger.com/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "leads-ranger-mcp": {
      "url": "https://app.leadsranger.com/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "leads-ranger-mcp": {
      "serverUrl": "https://app.leadsranger.com/mcp"
    }
  }
}

Ground your agent in cited data

Leads Ranger MCP gives your agent tools. Koskamo gives it reviewed, cited facts to check its answers against. Add it as a second MCP server; public reads need no API key.

Do you run Leads Ranger MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing