Connect HuntSales to your AI

In HuntSales, open Admin, then Developer, name your key and click Create key. Any member whose role includes the API Keys & MCP permission can create their own key. The key can use the tools your role permits, never more, and follows your role if it changes. The one choice is Allow this key to launch campaigns, off by default: without it the key can build and fill draft campaigns but cannot launch or resume one, or add contacts to or change a live one (see What a key can do below). Copy the key when shown; it is only displayed once. It starts with hs_live_. Keep it private, it is scoped to your workspace, and you can revoke it from the same page any time (admins can see and revoke every key in the workspace).

Workspace keys. For an integration that must keep working when staff change, a Super Admin can create a workspace key under Admin, then Developer, Workspace keys. It belongs to the workspace, not a person, and is bound to a role the Super Admin chooses (never the Super Admin role): every call is capped by that role's current permissions (except API Keys & MCP, which a workspace key ignores, since a Super Admin made it), and it acts as a member of the role who owns nothing. It reads and changes contacts, companies, deals, notes and the Suppression List as the role allows; it cannot search for or add prospects, build lists or campaigns, send email, work on tasks or manage webhooks, because those belong to a member. All workspace keys share one daily read limit, the same as one member's. Every Super Admin can see and revoke it, and its creation is recorded in the activity log and emailed to them.

Older keys. A key the Developer page marks as a legacy key was made for the whole workspace before keys became personal and held every permission. It no longer works: revoke it, and create a workspace key bound to a role instead.

Works with a key today: Claude Code and Claude Desktop on Mac, which we have run end to end, and, following each maker's documentation and not yet tested by us, Cursor, VS Code, n8n's MCP Client Tool, Gemini CLI and your own agent on the OpenAI or Claude API. Each lets you add a remote MCP server with your key in a header.

Pick the app you use. Replace hs_live_YOUR_KEY with the key from step 1.

Claude Code (the CLI)

Run this one command in your terminal. It is a single line, so it works as it is in PowerShell, Command Prompt and macOS or Linux terminals:

claude mcp add --transport http --scope user huntsales https://huntsales.io/api/mcp --header "Authorization: Bearer hs_live_YOUR_KEY"

Check it worked with claude mcp list (HuntSales should show ✓ Connected). It is available in new Claude Code sessions.

Claude Desktop (follows the mcp-remote documentation, not yet tested by us in this form)

Go to Settings → Developer → Edit Config (this opens a file called claude_desktop_config.json; if Windows asks which app to open it with, choose Notepad or VS Code). Add HuntSales inside mcpServers. Desktop launches local commands, so we use the mcp-remote bridge to reach the hosted server (you need Node.js installed):

{
  "mcpServers": {
    "huntsales": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote", "https://huntsales.io/api/mcp",
        "--header", "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer hs_live_YOUR_KEY"
      }
    }
  }
}

Copy it exactly: your key goes in env, and the header line has no space after Authorization:. Claude Desktop on Windows breaks any argument that contains a space, so the key travels in AUTH_HEADER instead, the workaround the mcp-remote documentation gives. We connected Claude Desktop on Mac with the key written directly in the header argument; we have not yet run this env form ourselves, on Mac or Windows. If you already have other servers, just add the huntsales block alongside them. Save the file and fully restart Claude Desktop (quit it, do not just close the window). HuntSales then appears under Settings → Developer, which also shows the server's status and its log if it does not connect.

Cursor (follows Cursor's documentation, not yet tested by us)

Add HuntSales to ~/.cursor/mcp.json (every project) or .cursor/mcp.json in one project. Cursor connects to the hosted server directly, so no bridge is needed:

{
  "mcpServers": {
    "huntsales": {
      "url": "https://huntsales.io/api/mcp",
      "headers": {
        "Authorization": "Bearer hs_live_YOUR_KEY"
      }
    }
  }
}

The file holds your key, so keep a project's .cursor/mcp.json out of version control.

VS Code (follows VS Code's documentation, not yet tested by us)

Run MCP: Open User Configuration from the Command Palette (or create .vscode/mcp.json in a project) and add:

{
  "inputs": [
    {
      "type": "promptString",
      "id": "huntsales-key",
      "description": "HuntSales API key",
      "password": true
    }
  ],
  "servers": {
    "huntsales": {
      "type": "http",
      "url": "https://huntsales.io/api/mcp",
      "headers": {
        "Authorization": "Bearer ${input:huntsales-key}"
      }
    }
  }
}

VS Code asks for your key the first time the server starts and keeps it out of the file, so paste just the key, starting hs_live_.

claude.ai, the Claude mobile app and ChatGPT

These apps connect by OAuth sign-in instead of a key. Add a custom connector with the URL https://huntsales.io/api/mcp (exactly, no trailing slash), sign in to HuntSales when the app asks, and choose what it may do:

• Reading is always included.
• Adding prospects, which uses credits, is ticked by default; untick it if you like.
• Launching campaigns, which sends real email, stays off unless you tick it.

Only what your role allows is offered, and every call still follows your role, which needs API Keys & MCP, as a key does. The app's contact reads count toward your daily read limit. A connection lasts up to 90 days, then you sign in again. See or disconnect your apps under Admin, then Developer, Connected apps; to change what an app may do, disconnect it and connect again. In a managed workspace only the Super Admin can connect an app. We have not yet tested these sign-ins end to end ourselves.

Once connected, you can ask things like:

• How many contacts are at the Follow-up stage?
• What is my pipeline breakdown right now?
• Which of my campaigns got the most replies?
• How many calls did the team make yesterday?
• How many HR managers in Singapore could I add to my CRM?
• How many HuntSales credits do I have left?

If your role includes the write permissions, you can ask it to do the work too. See the end-to-end example below.