Back to Browse

Salesmap Plugin MCP Server

Developer ToolsLow Risk10.0MCP RegistryLocalRemote
Free

Server data from the Official MCP Registry

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

About

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

Remote endpoints: streamable-http: https://api.salesmap.site/mcp

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (1 strong, 0 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry. 1 finding(s) downgraded by scanner intelligence.

17 tools verified · Open access · 1 issue found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

What You'll Need

Set these up before or after installing:

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

Environment variable: SALESMAP_API_KEY

How to Install & Connect

Available as Local & Remote

This plugin can run on your machine or connect to a hosted endpoint. during install.

Documentation

View on GitHub

From the project's GitHub README.

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.

Reviews

No reviews yet

Be the first to review this server!