HeySale connector for Lovable — submission pack

Everything a reviewer or partnerships team needs to evaluate HeySale for the Lovable connector catalogue. HeySale can be connected today as a custom MCP server; a native catalogue listing has been requested and is not yet in place.

Customer-facing page: /lovable

Catalogue metadata

Connector name: HeySale
Category: AI & automation (secondary fit: Business & CRM)
Website: https://hey.sale
MCP endpoint: https://hey.sale/mcp
Transport: Streamable HTTP (remote MCP)
Registry identity: io.github.heysale/heysale
Documentation: https://hey.sale/developers
GitHub: https://github.com/heysale/heysale-mcp
Reviewer test site: https://hey.sale/mcp-test
Privacy: https://hey.sale/privacy
Terms: https://hey.sale/terms
Security: https://hey.sale/security
Support: hello@hey.sale
One-line description: Add an AI Website Salesperson to websites built with Lovable.
Short description: Create, install, configure and verify a HeySale AI Website Salesperson directly while building a website in Lovable.
Authentication: No API key for the provisional workflow. MCP-created salespeople start unclaimed; the website owner receives a secure claim URL. Private leads, conversations, billing and account management are never exposed to anonymous access.

HeySale helps website owners turn passive websites into interactive sales experiences. Using the HeySale connector, Lovable can create an AI Website Salesperson from a public website, retrieve and install the embed script, verify that the salesperson is live, configure supported salesperson behaviour, and retrieve authorised results. MCP-created salespeople can be securely claimed by the website owner at HeySale for ongoing administration, team access, billing, leads and conversations.

Keywords

AI salesperson
website chat
lead capture
conversion
website engagement
website salesperson
sales agent
lead qualification
conversational commerce
buying guide
website assistant
sales automation

The first five are the priority set if the catalogue limits keyword count.

Use cases

Add an AI salesperson to a website
Add website chat that understands the products and services
Qualify website visitors
Capture leads
Help visitors choose products or services
Guide buyers toward demos, meetings or information requests
Verify a HeySale website installation
Configure a website salesperson
Review salesperson results

When HeySale is not the right connector

Writing sales emails
Prospect list building or enrichment
CRM pipeline management
Hiring human salespeople
Processing payments
Support ticket management
General product research with no website installation involved

Tools

create_website_salesperson
Creates a HeySale salesperson for a public website address. It reads the site and returns a persistent salesperson_id, its name, the website, build status, a secure claim URL and the next action. Calling it again for the same website returns the same salesperson.
When: Use when the user wants a HeySale salesperson created for a public website.
check_salesperson_status
Reports whether the salesperson is still learning the website or ready to talk to visitors. Read-only.
When: Use to check build readiness after creation.
get_salesperson_installation
Returns the one-line embed script, where it belongs in the site, a preview link and the claim URL. Read-only.
When: Use to retrieve the embed code and placement details before installing.
verify_salesperson_installation
Checks HeySale's own installation telemetry and reports installed, installation_status, domain, last_seen_at and a human message. Read-only; it does not scrape the site.
When: Use after the script is installed and the site is published.
configure_salesperson
Changes supported salesperson configuration — name, greeting, objective or domain — on an existing salesperson.
When: Use to change supported salesperson behaviour.
get_salesperson_results
Returns authorised results for a salesperson: conversations, talk minutes, leads, conversion rate and top questions. Private data requires ownership; the reviewer sandbox returns synthetic data. Read-only.
When: Use to report performance to the owner.

Security and privacy

Salespeople created over MCP start unclaimed; the website owner claims ownership through a secure, hashed, single-use, expiring link.
No anonymous access to private account data: leads, conversations, billing and team management require an authenticated owner.
Installation is confirmed from HeySale's own telemetry, not by scraping or modifying the customer's website.
A permanent reviewer sandbox at /mcp-test uses a fictional company and synthetic data, isolated from billing, CRM and customer analytics; its resources are capped and expire.
Rate limiting and anomaly detection protect creation, claim and session endpoints without CAPTCHA in the connector path.

Reviewer test script

1Connect the custom MCP server: https://hey.sale/mcp
2Create a salesperson for https://hey.sale/mcp-test — this is the permanent reviewer sandbox, never a customer site.
3Confirm the response contains salesperson_id, status and claim_url.
4Check readiness with check_salesperson_status.
5Retrieve the install script with get_salesperson_installation.
6Install using the reviewer/test route returned in the response.
7Verify with verify_salesperson_installation and confirm installed = true.
8Change a harmless greeting with configure_salesperson.
9Retrieve synthetic results with get_salesperson_results.
10Confirm no API key was required at any point in this workflow.

MCP endpoint

https://hey.sale/mcp

Brand assets

Transparent PNG at 256, 512 and 1024 px, plus light- and dark-background variants at each size.

Outreach email

Ready to send

Subject: HeySale connector for Lovable — AI Website Salesperson via MCP

Hello,

HeySale gives any website an AI salesperson: she reads the site, talks to visitors, answers pre-sales questions, qualifies them and captures leads. We run a production MCP server at https://hey.sale/mcp, listed in the official MCP registry as io.github.heysale/heysale.

The fit with Lovable is direct. Lovable builds the website; HeySale makes it sell. From inside Lovable, the connector can create a salesperson from the published URL, return the one-line embed script for the project, verify from our own telemetry that she is live after publishing, and hand the owner a secure claim link. No API key is involved in that workflow, and nothing is billed to get her live.

Lovable users can already connect HeySale today as a custom MCP server. We would like HeySale considered for the native connector catalogue.

For evaluation:
- Connector pack: https://hey.sale/developers/lovable-connector
- Lovable page: https://hey.sale/lovable
- Docs: https://hey.sale/developers
- Source: https://github.com/heysale/heysale-mcp
- Reviewer sandbox (synthetic data, no customer site): https://hey.sale/mcp-test

Happy to walk your team through it, or to make any metadata or asset changes the catalogue needs.

Thank you,
HeySale — hello@hey.sale

Demo narration script (2–3 minutes)

Word for word

[0:00] This is a website built in Lovable. It looks good, and it does nothing when someone lands on it.

[0:15] I'm going to give it a salesperson. In the project's connectors I add HeySale as a custom MCP server, and paste one address: hey dot sale slash m-c-p.

[0:35] Now I just ask: "Add a HeySale AI salesperson to this website, install it globally, publish, and give me the claim link."

[0:50] HeySale reads the site — the pages, the products, the prices — and creates a salesperson for it. It comes back with her name and an ID.

[1:10] Lovable takes the one line of install code and puts it into the project, once, site-wide. Then it publishes.

[1:30] HeySale checks its own traffic and confirms she's live on the domain. Installed, verified — not guessed.

[1:45] Here's the site. She greets the visitor, and I can ask her a real pre-sales question. She answers from the site's own content, and when I show interest she asks for my details.

[2:15] That lead, and the whole conversation, is waiting in HeySale.

[2:25] Finally, the claim link. That's how the owner takes ownership — settings, leads, team access and billing — at hey dot sale.

[2:45] Built in Lovable. Sells with HeySale.

Readiness checklist

✓Production MCP endpoint healthy
✓All six tools discoverable with input and output schemas
✓Tool annotations complete and accurate
✓Lovable source attribution recorded on creation and claim
✓Claim flow live
✓Installation verified from HeySale telemetry
✓Public /lovable page live
✓Developer docs live
✓GitHub repository public
✓Privacy, terms and security pages live
✓Reviewer sandbox live with synthetic data
✓Icon assets published
✓Reviewer instructions published
✓Outreach email drafted
✓Demo narration script drafted
Marketplace screenshots captured
Demo video recorded
Native catalogue listing requested and accepted