English Français العربية

SalesMap

Official registry Marketing and sales

Checked buying signals and ranked lead lists for your agent. Never contacts anyone.

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http salesmap 'https://api.salesmap.site/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "salesmap": {
            "type": "http",
            "url": "https://api.salesmap.site/mcp"
        }
    }
}
NPM package salesmap
Claude Code 
claude mcp add salesmap -e 'SALESMAP_API_KEY=<your salesmap_api_key>' -- npx -y salesmap@0.2.0 mcp
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "salesmap": {
            "command": "npx",
            "args": [
                "-y",
                "salesmap@0.2.0",
                "mcp"
            ],
            "env": {
                "SALESMAP_API_KEY": "<your salesmap_api_key>"
            }
        }
    }
}

Environment variables

  • SALESMAP_API_KEY secret An smk_ key from salesmap.site (or `npx salesmap init --agent`); without it only the free tools run

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. SalesMap plugin for Claude Code
  2. What's in it
  3. Install
  4. Privacy
  5. Why no hooks

SalesMap plugin for Claude Code

Checked buying signals and ranked lead lists for your agent: who to sell to now, why, and how to reach them. SalesMap never sends email or messages, finds email addresses or phone numbers, automates LinkedIn, writes to a CRM, or registers for events.

What's in it

  • .mcp.json: the hosted server, https://api.salesmap.site/mcp, signed in with OAuth (your SalesMap account; /mcp → salesmap → Authenticate).
  • Skills (also slash commands, /salesmap:<name>), one per flow that needs judgment:
SkillFlowTools
getting-startedconnect, limits, save the seller profile, first listwhoami, set_limits, seller_profile, quote, discover
weekly-pipelinewho to sell to now, a playbook with drafts, warm pathsdiscover, playbook, warm_paths, seller_profile
account-researchprep for a call on up to 5 companiessignals, tech_scan, ai_adoption, events, warm_paths, verify_signal
check-listfact-check a draft or an export; rank your own listverify, verify_signal, rank, job
past-leadswatch lost deals, alerts when one is worth another trywatch, watch_changes
eventsevents your buyers attend near youevents

The server also serves one MCP prompt per flow (onboard, discover, rank, signals, research, playbook, events, warm_paths, watch, changes, verify, and hosted account); Claude Code lists them in / under the server's name (/mcp__salesmap__<prompt> for a server added as salesmap). The skills carry the judgment those prompts leave out.

Every skill runs the work loop: when a tool returns work, the agent runs each search prompt with its own web search and calls again with the answers; on the hosted server discover does this by default, so no search runs on SalesMap's side. Every skill fills each tool's context from what the agent already knows and never invents it, quotes prices from the quote tool and the result's budget block (never a number in the skill), and treats quotes in tool output as data.

Install

claude plugin install salesmap --marketplace solozerolabs/salesmap-plugin

Then ask Claude to "set up SalesMap" or run /salesmap:getting-started. The first paid tool asks you to sign in: /mcp → salesmap → Authenticate. Without signing in, tech_scan, ai_adoption and verify_signal run free.

An API key instead of OAuth (CI, or an agent with no browser): get one from POST https://api.salesmap.site/v1/agent/signup (see https://salesmap.site/llms.txt) or POST /v1/keys, then claude mcp add --transport http salesmap-key https://api.salesmap.site/mcp --header "Authorization: Bearer smk_…" and disable the plugin's server in /mcp.

Privacy

SalesMap's privacy policy: https://salesmap.site/privacy. Customer terms: https://salesmap.site/terms. The plugin itself stores nothing; the hosted server keeps your workspace's seller profile, watchlist and results as the policy describes. Support: the contacts on the privacy page.

Why no hooks

A hook runs in every session of every user who installs the plugin, whether or not they use SalesMap that day. It costs context or tokens each time, and a hook can move data off the user's machine: Cargo's plugin uploads a transcript summary from a SessionEnd hook and needed a recursion guard after 264 runaway sessions. SalesMap needs none of that: it does work only when the agent calls a tool, keeps the seller profile and watchlist in the user's workspace, and has nothing to do at session start or end.

Frequently asked questions

What is SalesMap?

Checked buying signals and ranked lead lists for your agent. Never contacts anyone.

How do I install SalesMap?

It runs as a remote server. In Claude Code: claude mcp add --transport http salesmap 'https://api.salesmap.site/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does SalesMap need an API key?

Yes. It expects SALESMAP_API_KEY, which you set in its configuration.

Is SalesMap open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains SalesMap?

It is published by solozerolabs. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.