Marketing

hey.sale

Enables creation and management of AI salespeople that engage website visitors, answer business questions, and capture leads.

1 endpoint6 known toolsFirst detected September 8, 2026Last detected September 8, 2026

ENDPOINT 1

https://hey.sale/mcp

No auth detected

MCP server metadata

Name: heysale
Version: 1.1.0

Capabilities

tools

Server instructions

HeySale gives a website an AI salesperson that talks to visitors, answers their questions from the site's own content and captures leads. Start with create_website_salesperson and a public website address; it returns a salesperson_id — keep that id, every other tool needs it. Then check_salesperson_status until it is ready, get_salesperson_installation for the one-line script, and verify_salesperson_installation once the script is live. Finally give the website owner the claim_url so they can claim their HeySale account, where they manage leads, team and billing. Never ask a website owner for an API key; private results and changes to a claimed salesperson happen inside HeySale.

Known tools 6

create_website_salesperson

Give any public website an AI salesperson that talks to its visitors, answers questions about the business, and captures leads.

Inferred read-only

check_salesperson_status

Find out whether a website salesperson has finished reading the website and is ready to talk to visitors, and whether its script has been detected on the live site.

Inferred read-only

get_salesperson_installation

Return the exact one-line script to add to a website so its salesperson appears for visitors, plus where to place it and whether HeySale has detected it yet.

Inferred read-only

verify_salesperson_installation

Check whether a HeySale salesperson has actually been installed on its website and is reporting back to HeySale.

Inferred read-only

configure_salesperson

Change a salesperson's name, its opening line, or the goal it works towards.

Inferred read-only

get_salesperson_results

Summarise how many visitors talked to the salesperson, how many left their details, and what they asked about most.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.heysale]
url = "https://hey.sale/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "heysale": {
      "type": "http",
      "url": "https://hey.sale/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: heysale
Remote MCP URL: https://hey.sale/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "heysale": {
      "url": "https://hey.sale/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "heysale": {
      "type": "http",
      "url": "https://hey.sale/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "heysale",
  "transport": "streamable-http",
  "url": "https://hey.sale/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.