Install, sign in, set up. Then just ask.

How it works

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. The playbooks live on the server and reach your agent as it works, so they improve without a reinstall.

Getting started, end to end

From nothing to your first brief in about ten minutes. You add one server to the agent you already use, sign in with your work email, answer a short interview, and then talk to it in plain sentences. No password, no card.

1. 01 · InstallOne line or one setting in your agent.
2. 02 · Sign inYour email, a 6-digit code, approve.
3. 03 · Set upSay “set me up”. A few minutes.
4. 04 · DataYour CRM, or a local database.
5. 05 · Daily useSentences, slash prompts, “send it”.

1 · Install it in your agent

SalesAgents is a remote MCP server at https://mcp.salesagents.si/mcp (streamable HTTP, sign-in by email, no API key). Name it salesagents everywhere; the slash prompts use that name.

The local database needs an agent that can run terminal commands and Node.js 22.13 or newer (node --version). If you use HubSpot, Pipedrive, ClickUp or Salesforce you do not need it. See Data.

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

{"mcpServers":{"salesagents":{"type":"http","url":"https://mcp.salesagents.si/mcp"}}}

codex mcp add salesagents --url https://mcp.salesagents.si/mcp

{"mcpServers":{"salesagents":{"url":"https://mcp.salesagents.si/mcp"}}}

{"mcpServers":{"salesagents":{"serverUrl":"https://mcp.salesagents.si/mcp"}}}

{"mcpServers":{"salesagents":{"type":"streamableHttp","url":"https://mcp.salesagents.si/mcp"}}}

{"mcpServers":{"salesagents":{"command":"npx","args":["-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. On a phone? Email yourself the line and paste it later where your agent runs.

2 · Sign in with your email

The first time your agent talks to the server, it opens the sign-in page in your browser. In Claude Code that happens through /mcp, in claude.ai through Connect, in the others on first use.

1. “Sign in with your email.” The page names the app that is connecting. Type your work email and press Send me the link. Use the address you want the workspace and the licence under: one email is one workspace.
2. “Check your inbox.” A mail from SalesAgents <[email protected]> arrives with the subject Your SalesAgents sign-in code, followed by the app's name. It holds a 6-digit code and a Sign in button.
3. Finish one of two ways. Press Sign in in the mail if it opens in the same browser that showed the sign-in page. Or type the 6-digit code into that sign-in page: this is the way when you read the mail on your phone or in another browser. Opening the button in a different browser does not sign you in there; it shows you the code to type where you started.
4. “Approve the connection.” The page shows the email you signed in with, where access goes (for Claude Code, Codex and other local hosts: an app on this computer), and the tools the app may call. Press Approve and connect only if you just started this connection; Cancel otherwise.
5. Back in your agent. The browser hands the connection back and your agent is signed in. You can close the tab.

How long you stay signed in. Your agent holds an access token for 24 hours and renews it quietly with a refresh token that lasts 90 days and is replaced on every renewal. Use it at least once in 90 days and you never see the sign-in page again.

Signing out or switching account. Remove the server from your agent (see Troubleshooting) or disconnect the connector; your agent then forgets the tokens. To sign in again or as someone else, in Claude Code type /mcp → salesagents → Re-authenticate; elsewhere remove and add the server, or press Connect again. Signing in with another email opens another workspace, with its own profile and licence.

The mail does not arrive. Give it a minute, then look in spam, junk or your quarantine, and search for the subject. Ask IT to allow [email protected] if mail from new senders is held. Then start again from your agent for a fresh mail. An error page saying Sign-in expired means the page waited longer than ten minutes, the code was already used, or you typed the code in a different browser from the one that asked; start again from your agent. Link expired means the link is older than 15 minutes or was already used.

3 · Set up your profile

Say set me up (in Slovenian nastavi me), or in Claude Code run /salesagents:setup. The interview is free and takes a few minutes. Before it asks anything, your agent reads what it can already see: your website, the signature in a recent sent mail, an AGENTS.md or CLAUDE.md in the workspace, your CRM's stages and the connectors it has. Then it asks only what is left, one section at a time, at most five questions a round.

To finish it needs the company name, one brand with its sign-off, the owner's name, your working languages and your CRM (or “none”). The rest can wait.

Where the profile lives. On our server, under your sign-in email. It is configuration only: company, brands, people, voice, ICP, stages, links and which tools you use. Never CRM rows, mail or transcripts, and never a password or API key: those stay in your agent's own settings.

Change it later with a sentence: show my profile, change my signature, connect my Gmail and calendar. Say set me up again to go through it all.

4 · Your data

From a spreadsheet. Say import my contacts from a CSV: your agent reads the file on your machine, skips duplicates and adds each company, contact and deal to your CRM or the local database. The free pipeline check also takes a CSV export as it is.

What stays with us. Your sign-in email and a contact record (email, time, the app you connected from), the tokens issued to your agent, your profile, and the report pages of the free briefs, each behind a six-character access code and deleted after seven days. Never CRM rows, mail, transcripts or files. See the privacy notice.

Out or gone. export my data gives you the profile as JSON to keep. delete my profile removes the profile and any setup draft after you confirm; it cannot be undone. The CRM rows are already yours: in your CRM, or in .salesagents/crm.db, which you can copy or delete like any file. For anything else, including the contact record, write to [email protected].

5 · Daily use

Talk to your agent in plain sentences, in English or Slovenian. You never call a tool by name. Hosts that show MCP prompts also give you shortcuts; in Claude Code they are slash commands:

Free to start. Setup, your profile and four briefs: research Acme, pipeline health, prep me for my meeting with Acme and audit my DMs. Each brief opens as a report page; your agent prints the link and the access code. Everything else (the briefing, the inbox, proposals, LinkedIn, the local database and the rest of the modules) comes with the licence.

You say send. Every email, DM, comment and connection request is a draft. Your agent shows it to you and waits. send it sends exactly the draft you just saw, through your own mail or LinkedIn, and nothing else; if it is unclear which draft you mean, it asks. More under Approval.

Every morning. Say schedule my morning brief every weekday, or see Scheduling.

Modules

176 commands across twelve modules. The full reference, every sentence with what it does, is on Modules; each module also has its own page.

• 01 · Setup & data24 commands

  Everything a new team does once: the profile interview, the CRM (your own, or a local one the agent creates), imports, the tools you connect, and your data out or gone.

• 02 · CRM & pipeline20 commands

  The morning briefing, the pipeline by stage, the deals gone dark, and every record kept up to date with a sentence.

• 03 · Research & accounts13 commands

  From a list of names to a qualified account with a plan: research, qualification, scoping, discovery material and a pre-read for leadership.

• 04 · Meetings9 commands

  A prep brief before every call, scheduling and booking links, and the recording turned into notes, CRM updates and the follow-up.

• 05 · Proposals & contracts11 commands

  Scope, proposal, SoW, pilot, pitch and redline review, in your own template and saved to the account's folder.

• 06 · Inbox & outreach20 commands

  The replies you owe, inbox zero, cold sequences, campaigns, inbound leads and objections, all drafted in your voice and sent only when you say so.

• 07 · LinkedIn acquisition22 commands

  Signals, comments, DMs, warm intros, hiring leads and the daily top-of-funnel loop, on your own account at a human pace.

• 08 · Content20 commands

  Ideas from what happened this week, posts, cards, decks, demos, videos and copy, with a proofread before anything goes out.

• 09 · Partners6 commands

  Find, qualify and onboard partners, keep them updated, and see who owes whom an introduction.

• 10 · Projects & handover10 commands

  The project opened from the signed SoW, a plan with tasks per person, blockers, monthly reports and scope kept in check.

• 11 · Reports & automation11 commands

  Daily and weekly reports, dashboards, the team's focus, and recurring jobs scheduled in your own harness, not on our cron.

• 12 · Optional · Slovenian pack10 commands

  Business registry enrichment, NDA, DPA and framework agreements, invoice instructions with DDV, and Slovenian proofreading. Switch it on in your profile.

The same sentences work in Slovenian. You do not need the exact words: the server routes what you meant.

The tools, briefly

Your agent sees these as MCP tools. You never type their names; it picks one from what you said.

Scheduling

Recurring work runs in your own setup, not on our cron: the morning briefing, the weekly pipeline review and the daily LinkedIn pass. Say schedule my morning brief every weekday and your agent sets it up where it can. In Claude Code that is /schedule running /salesagents:whats-up; elsewhere a cron entry or a Codex automation that runs the same sentence. A scheduled run prepares drafts and waits for you like any other.

Approval rules

• Every external send (email, DM, comment, connection request, like) is a draft until you say send it for that draft.
• send it is never a send by itself: it approves the one draft you just saw, and your agent sends it through your own mail or LinkedIn.
• Prices never go into outreach unless you write them in.
• Your voice rules apply to every draft: banned phrases, length limits, sign-offs and the rules against machine-sounding text.
• The server itself sends nothing to your contacts. It has no access to your mailbox, calendar, CRM or LinkedIn.

What it cannot do

• It cannot use a tool your agent does not have. No calendar connector, no meeting prep from the calendar; it says 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.

Licence

Free: connecting, the setup interview, your profile, export and delete, and the four briefs above. With the licence: every playbook in the modules, the local database and playbook updates without a reinstall. Plans are on the pricing page.

1. Ask in your agent: do I have the licence? It tells you whether this email holds one and until when. A licensed tool you call without it says so and offers to request access; your agent asks you before it does.
2. Say yes, and your agent requests it for the email you signed in with. You get a mail, SalesAgents request received, with the next step, and a person on our side is told. Or use the request form on the pricing page with the same email.
3. Once it is paid, the licensed tools unlock on that email within a minute, in every agent where you signed in with it. No reinstall. The free tools keep working meanwhile.

Troubleshooting