MCP for sales teams: what it is and what to connect

What MCP is

MCP (Model Context Protocol) is an open standard, introduced by Anthropic in November 2024, that lets an AI agent use tools: read data, search, and take actions. A tool provider runs an MCP server; your agent connects to it and can then call its tools in the middle of a conversation.

For a sales team, that means the agent stops being a chat window you paste into. It can look an account up, research it, write the email and record what it did, in one flow.

What to connect for outbound

• Data. Many data providers, Apollo and Clay among them, ship MCP servers for finding and enriching companies and people.
• Your CRM. Many CRMs offer an MCP server or connector; check with your vendor.
• Email and calendar. Claude has connectors for Gmail and Google Calendar.
• A harness. Something that holds the outbound work itself, runs sequences and watches for replies. That is what Harp is. See What is an MCP harness?.

Local and remote servers

A local MCP server runs on your own machine. Claude Code and Claude Desktop start it for you from a short config entry. A remote server is hosted by the provider, and you add it as a connector by its URL. Web-based assistants can only use remote servers.

What to watch out for

• Tool overload. Every connected server adds tool definitions to the agent’s context. Prefer servers with a few task-shaped tools over ones that expose every API endpoint.
• Irreversible tools. Some tools send email or messages. Know which ones, and keep a person or a guardrail in front of them.
• Credentials. Keep API keys in the server’s configuration, never in a prompt.
• Scope. Make sure each server points at the right workspace or account before the agent writes anything.

Getting started

Connect one data source and one place for the work to live, then ask your agent for a briefing and a short list of accounts to research. Add tools only when the work asks for them. How to run outbound from Claude walks through the full setup.