MCP server · mcp.salesagents.si

One endpoint. Your agent does the selling work.

SalesAgents is a remote MCP server. It does not log into your mailbox or your CRM. It tells your agent what a good salesperson would do next, step by step, and your agent does it with the tools it already has.

Endpointhttps://mcp.salesagents.si/mcpstreamable HTTP · sign-in by email

Free to connect. The first call emails you a one-time sign-in link. No password, no card. Jump to your install line →

How it works

01 · you

You ask

“Research Acme”, “what's up?”, “process the meeting”. Any language your profile lists.

02 · remote

The server returns a brief

The playbook for that job with your profile filled in: the steps, which of your agent's tools to use, what to record and the next allowed step.

03 · local

Your agent does it

With its own connectors: mail, calendar, Drive, Slack, your recorder, your CRM, or the local database.

04 · you

You approve

Drafts wait in your mailbox or in the chat. A send happens when you say so.

That split is the point. Your agent already has your Google or Microsoft account, your files and your CRM. We do not need a copy of any of it to tell it how to run a proper sales process.

Install

One line per host. The endpoint speaks MCP over streamable HTTP and needs no key: the first call opens a sign-in page, you type your email and click the link we send.

Claude Codeterminal
claude mcp add --transport http salesagents https://mcp.salesagents.si/mcp --scope user

Drop --scope user to add it to the current project only. Then say: set me up.

Claude Code, shared with the team.mcp.json
{"mcpServers":{"salesagents":{"type":"http","url":"https://mcp.salesagents.si/mcp"}}}

Put it in .mcp.json at the root of a shared folder or repository and every teammate's Claude Code picks it up. Each person still signs in with their own email.

OpenAI Codex CLIterminal
codex mcp add salesagents --url https://mcp.salesagents.si/mcp

Or in ~/.codex/config.toml: [mcp_servers.salesagents] then url = "https://mcp.salesagents.si/mcp".

Cursor~/.cursor/mcp.json
{"mcpServers":{"salesagents":{"url":"https://mcp.salesagents.si/mcp"}}}
Windsurfmcp_config.json
{"mcpServers":{"salesagents":{"serverUrl":"https://mcp.salesagents.si/mcp"}}}

Windsurf names the key serverUrl for remote servers.

Clinecline_mcp_settings.json
{"mcpServers":{"salesagents":{"type":"streamableHttp","url":"https://mcp.salesagents.si/mcp"}}}
Claude Desktop · claude.aiconnector

Settings → Connectors → Add custom connector, name it salesagents, paste https://mcp.salesagents.si/mcp. In a chat, switch it on in the tools menu. On Team and Enterprise plans an admin can add it once for everyone.

Anything that only runs stdiofallback
npx -y mcp-remote https://mcp.salesagents.si/mcp

You never call the tools by name. Talk to your agent and it picks the right one.

What it touches, and what it never does

On your side

  • Your agent's own connectors: Gmail or Outlook, Calendar, Drive or OneDrive, Slack, meeting recorders.
  • Your CRM through your agent's connector, or a local database at .salesagents/crm.db that your agent creates.
  • LinkedIn through your own Unipile key.
  • Report pages (for example the research brief) open only with the access code your agent prints.

Never

  • We never ask for or keep your Google, Microsoft or LinkedIn password or token.
  • No CRM rows, emails, transcripts or files are stored on our servers.
  • Tool arguments are not logged; request logging is off.
  • Nothing is sent from our side to your contacts.

On our side we keep your sign-in email, the access token issued to your agent, and your profile: company and brands, people and roles, voice rules, ideal customer, pipeline stages, links and which tools you use. That is configuration, and you can export or delete it. See the privacy notice.

The tools, briefly

ToolWhat it is for
sa_helpTurns what you said into the right module and the next step. Free.
sa_setupThe setup interview that writes your profile.
sa_profileRead or change one part of the profile, such as a signature or a pipeline stage.
Module toolsOne per job: briefing, pipeline report, research, meeting prep and processing, proposal, SoW, inbox review, outreach, LinkedIn, content, partners, project handover. Listed in the docs.

What it cannot do

  • It cannot use a tool your agent does not have. No calendar connector, no meeting prep from the calendar; it will say what is missing.
  • The local database needs an agent that can run commands (Claude Code, Codex, Cursor). On claude.ai and Claude Desktop, connect a CRM.
  • It does not send. Sends happen in your agent, on your say-so.

Install it, then say “what's up?”

Sign-in is by email. Start free with one sentence; the plans are on the pricing page.

StartPricing