HeySale × Devin

HeySale for Devin

Hand Devin the site. Get back a site that sells.

Devin can provision the salesperson, modify the site's code, open the pull request that installs her, and verify the embed once it is deployed.

$0 setup · $0/month · $0.33/minute when customers talk · Custom MCP · Connection steps checked 2026-09-07

Connect HeySale to Devin

Custom MCP
  1. 1Open Devin's MCP Marketplace and add a server, or use the Devin CLI.
  2. 2Use https://hey.sale/mcp with the HTTP transport.
  3. 3Give Devin the task: create the salesperson and install the script.

Configuration

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

No API key is needed to create a salesperson. Reading a salesperson's conversations, leads or results requires the website owner's own HeySale API key.

Or start here, right now

Give us your website address. We read it, build your salesperson, and show her to you before you sign up for anything.

Things to say to Devin

  • Add a HeySale salesperson to our marketing site and open a PR.
  • Verify the HeySale embed is live in production.

Why this pairing works

The site gets built in minutes; the selling still has to happen after the visitor lands.
HeySale reads the finished site and answers from it — no separate knowledge base to maintain.
Leads arrive with the whole conversation attached, so you know what they actually wanted.

HeySale runs one MCP server for every assistant: https://hey.sale/mcp over Streamable HTTP (remote MCP).

All integrationsConnect any MCP clientDeveloper documentationDevin docs

Last verified 2026-09-07 against Devin MCP documentation (stdio, SSE and HTTP transports).