Skip to main content

GetSales MCP — Connect Claude (and other AI assistants) to your workspace

Meet the GetSales MCP server — drive your workspace (single team or multi-team) from Claude or any MCP-compatible AI client via a single OAuth-authenticated connector.

Written by Peter

What is GetSales MCP?

MCP (Model Context Protocol) is an open standard that lets AI assistants like Claude securely talk to external tools. We just shipped GetSales MCP — a server that exposes most of GetSales as tools your AI assistant can call directly.

Instead of clicking through the UI, you can ask Claude things like:

  • "Create a new sender profile and generate a LinkedIn binding link for me."

  • "Spin up an auto for cold outreach to this list, with a 3-step follow-up."

  • "Show me reply-rate by sender for last week."

  • "Move all replied leads from Auto X into Auto Y."

  • "Switch me to the Acme team and pull the funnel report."

A single connector covers multi-team use — once you sign in, your assistant can switch between any team you have access to and even create new ones.

What can the MCP do today?

A lot already — and the surface keeps growing. Over the next few fix we will be actively improving it.
​
Highlights:

  • Team & billing management — switch between teams you have access to, create new teams, apply subscription plans.

  • Sender profiles — create senders, generate account-binding links (LinkedIn, email, etc.) for the user to authorize.

  • Autos (automations / flows) — create autos from scratch, add or remove leads, start/stop, configure steps.

  • Inbox — read threads, reply, move conversations, manage statuses.

  • Reports & analytics — pull a wide range of reports (activity, funnel, reply rates, sender performance, dashboards) on demand, scoped to a team or across teams.

  • CRM — search, read, and update lead records and CRM fields directly from chat.

Built-in feedback channel — please use it

The MCP ships with a built-in report tool. If anything feels off — a tool returns the wrong shape of data, an action fails, behavior is confusing, or a feature you expected is missing — just tell your assistant something like "send a report: <what went wrong>". The report goes straight to our team with the relevant context attached.

This is the fastest path to fixes and the best way to shape the roadmap. The product is moving quickly, and your reports directly drive what we ship next.

Setup in Claude

Setup takes about a minute. Authentication uses standard OAuth — your password never goes to Claude, only to GetSales.

  1. Add a custom connector. Open Claude (claude.ai or the desktop app) and go to Settings → Connectors → Add custom connector.
    ​

  2. Fill in the details and click Add.

  3. Click Connect and sign in. The new GetSales entry appears in the connectors list with a Connect button.


    Click it — Claude will redirect you to the GetSales login page. Sign in with your normal GetSales email and password.

  4. You're done. After login, you're redirected back to Claude and the connector activates automatically — the button now reads Configure instead of Connect.

  5. Verify it works. Start a new chat and ask Claude to use GetSales MCP and list your teams.

Did this answer your question?