HeySale — AI Website Salesperson

io.github.heysalePublished by GitHub account heysalev1.0.0Updated Oct 25, 2026

Create and install an AI Website Salesperson for sales, qualification, and lead capture.

VerifiedStreamable HTTPWeb executableCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

A remote MCP server that lets an assistant create, install, configure and monitor an AI salesperson chatbot on a public website and review its lead results.

What you can do
Create a website salesperson that reads a public site and talks to visitors, answering questions and capturing leads, and check whether it has finished reading the site and been detected live. Retrieve the one-line install script and where to place it, and verify through HeySale telemetry whether it is actually installed. Change the salesperson's name, opening line or goal while it is unclaimed. Summarise visitor conversations, captured details and most-asked topics.
When to use it
Useful when someone wants to add a sales chatbot, live chat or lead-capture assistant to a public website and needs help creating it, installing the script and checking results. Also for checking whether an existing salesperson is live and working.
Requirements
A remote streamable HTTP endpoint at hey.sale; no package, environment variables or headers are declared. A public website address to attach the salesperson to, and the salesperson_id returned at creation for later calls.
Before you install
Results are private business data returned only to authorised callers, and the server warns never to ask a website owner for an API key. Once a site owner claims a salesperson, configuration changes must be made by the owner in HeySale. Creating a salesperson and installing a script change a live public website.

Installation

In SourceWeft

  1. Open HeySale — AI Website Salesperson in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.heysale%2Fheysale/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

README

Brand Assets

Add approved HeySale brand assets here only if you want downstream marketplaces or integration guides to reference files from this repository.

Recommended assets to add later:

  • heysale-icon-512.png
  • heysale-logo-dark.png
  • heysale-logo-light.png

Do not add unapproved generated logos or third-party trademarks to this directory.

Source: README.md at commit 3b44949

Tools

6

create_website_salesperson

Create a website salesperson

Give any public website an AI salesperson that talks to its visitors, answers questions about the business, and captures leads. Use this when someone wants to add a salesperson, live chat, a sales assistant or a chatbot alternative to a site. Provide the website address; the salesperson reads the site itself. The response always includes an explicit salesperson_id — keep it, because every other HeySale tool needs it — plus the one-line install script and a claim_url to give the website owner. Safe to call twice for the same website. To try HeySale without touching a real website, use website_url https://hey.sale/mcp-test — that creates an isolated, disposable test salesperson on HeySale's own reviewer sandbox.

Parameterscampaignwebsite_urlrequiredbusiness_nameintegration_sourceexternal_project_id

check_salesperson_status

Check a salesperson's readiness

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. Give it the salesperson_id returned when the salesperson was created.

Parameterssalesperson_idrequired

get_salesperson_installation

Get the install script

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. Give it the salesperson_id returned when the salesperson was created.

Parameterssalesperson_idrequired

verify_salesperson_installation

Verify a salesperson's website installation

Check whether a HeySale salesperson has actually been installed on its website and is reporting back to HeySale. Uses HeySale's own telemetry, so it works with single-page apps, tag managers and deferred script loading — never scrape the website's HTML to answer this. Give it the salesperson_id returned when the salesperson was created.

Parameterssalesperson_idrequired

configure_salesperson

Change how a salesperson introduces itself

Change a salesperson's name, its opening line, or the goal it works towards. While a salesperson is still unclaimed this can be set as part of setting it up. Once the website owner has claimed it, changes must be made by the owner in HeySale — do not ask anyone for an API key.

Parametersnameapi_keygreetingobjectivesalesperson_idrequired

get_salesperson_results

See what the salesperson achieved

Summarise how many visitors talked to the salesperson, how many left their details, and what they asked about most. This is private business data: it is only returned to an authorised caller. Never ask a website owner for an API key — send them to HeySale instead.

Parametersdaysapi_keysalesperson_idrequired

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts