What Is an MCP Server?
MCP (Model Context Protocol) is an open protocol that allows AI assistants like Claude Desktop to connect with external tools and data sources. An MCP server is a lightweight program that exposes a set of tools — functions that the AI can call — over a standardized interface. When you connect an MCP server to your AI assistant, you give it the ability to take real actions in your sales tools, CRM, or any other software.
In the context of sales, an MCP server lets you interact with your lead generation platform through natural language. Instead of clicking through a UI or writing API code, you can tell your AI assistant to "find 20 SaaS companies in the fintech space with 50-200 employees" and it will execute that request through the MCP server.
How MCP Works: The Architecture
The Three Components
- AI Assistant (Host) — Claude Desktop, or another MCP-compatible AI client. This is where you interact with the system through natural language.
- MCP Server — A program that translates between the AI assistant and your tools. It defines available tools, validates inputs, and returns structured results.
- Backend Service — The actual tool or API being accessed. In AutoReach's case, this is the AutoReach API.
The Communication Flow
``
You (natural language) → Claude Desktop → MCP Server → AutoReach API → Results → Claude Desktop → You (formatted answer)
`
You: "Show me all qualified leads from last week with a score above 75"
Claude Desktop: Calls the MCP server's list_leads tool with parameters { status: 'qualified', minScore: 75, dateRange: 'last_week' }
MCP Server: Translates the tool call into an AutoReach API request, receives results, and returns them to Claude.
Claude Desktop: "Here are 12 qualified leads from last week with scores above 75: [formatted list with key details]"
The AutoReach MCP Server
Available Tools
AutoReach provides an MCP server with 20 tools covering the full lead generation workflow:
Workflow Management:- create_workflow
— Create a new prospecting workflow - list_workflows
— View all your workflows - run_workflow
— Start a workflow run - pause_workflow
— Pause a running workflow - get_workflow_status
— Check workflow progress
- search_leads
— Find leads with filters - get_lead_details
— View full lead data including research and scores - add_leads
— Add prospects to a workflow - qualify_lead
— Trigger AI qualification for a lead - update_lead_status
— Accept, reject, or flag leads
- research_company
— Analyze a company website - get_research_results
— Retrieve research data
- draft_email
— Generate a personalized email for a lead - send_email
— Send an approved email - list_sent_emails
— View outreach history
- get_campaign_stats
— View campaign performance metrics - get_credit_balance
— Check remaining credits - get_usage_report
— Generate usage and ROI reports
- get_settings
— View current settings - update_settings
— Modify workflow settings
Setting Up the AutoReach MCP Server
#### Prerequisites
- Node.js 18 or later installed
- An AutoReach account with an API key
- Claude Desktop (or another MCP-compatible AI assistant)
- Clone or download the AutoReach MCP server:
bash
git clone https://github.com/autoreach/mcp-server.git
cd mcp-server
npm install
npm run build
`
- Configure your API key:
`bash
export AUTOREACH_API_KEY=your-api-key-here
`
- Add the server to Claude Desktop's configuration file (
claude_desktop_config.json):`json
{
"mcpServers": {
"autoreach": {
"command": "node",
"args": ["/path/to/mcp-server/dist/index.js"],
"env": {
"AUTOREACH_API_KEY": "your-api-key-here"
}
}
}
}
`
- Restart Claude Desktop
- Verify the connection by asking Claude: "What AutoReach tools are available?"
Real-World MCP Use Cases
Use Case 1: Morning Pipeline Review
Instead of logging into the AutoReach dashboard, open Claude Desktop and ask:
"Give me a summary of yesterday's workflow activity — how many leads were processed, qualified, and contacted? What is my current credit balance?"
Claude calls multiple MCP tools, aggregates the data, and presents a concise morning briefing.
Use Case 2: Quick Research
"Research the company Acme Corp at acme.com and tell me if they would be a good fit for our product."
Claude calls
research_company, analyzes the results, and gives you a fit assessment — all without leaving your chat window.
Use Case 3: Lead Triage
"Show me the 10 most recent qualified leads, sorted by score. For any below 60, explain why they scored low."
Claude retrieves leads, filters, sorts, and provides analysis — combining data retrieval with AI-powered interpretation.
Use Case 4: Campaign Analysis
"Compare the performance of my Q1 SaaS workflow versus my Q1 Fintech workflow. Which one has a better reply rate and lower cost per qualified lead?"
Claude pulls stats from both workflows and generates a side-by-side comparison with recommendations.
MCP vs Direct API: When to Use Each
Scenario Use MCP Use Direct API Ad-hoc queries and analysis Yes No Automated integrations No Yes Data exploration Yes No Scheduled tasks No Yes Building custom UIs No Yes Quick actions without switching apps Yes No High-volume operations No Yes
MCP is best for interactive, exploratory use cases where you benefit from AI interpretation. Direct API is best for automated, programmatic integrations that run without human involvement.
Security Considerations
API Key Protection
Your MCP server has the same access level as any API integration. Secure it accordingly:
- Store the API key in environment variables, not in config files
- Limit MCP server access to trusted machines
- Use a dedicated API key for MCP (separate from other integrations)
- Monitor API key usage for unexpected patterns
Data Privacy
MCP tool responses pass through the AI assistant. Be aware that:
- Lead data is processed by the AI assistant's language model
- Do not request sensitive personal data through MCP unless you are comfortable with AI processing
- Review your AI assistant's data handling policies
Access Control
The MCP server inherits the permissions of the API key it uses. If you want to limit what the MCP server can do, create an API key with restricted permissions (read-only, specific endpoints only).
Building Your Own MCP Server
If you want to connect other sales tools to your AI assistant, you can build custom MCP servers:
MCP Server Structure
An MCP server is a Node.js (or Python) program that:
- Defines available tools with names, descriptions, and parameter schemas
- Handles tool call requests from the AI assistant
- Validates inputs and calls the underlying API
- Returns structured results to the AI
Key Design Principles
- Clear tool names — Use descriptive names like
search_leads not sl`FAQ
Do I need to be a developer to use MCP?
You need basic technical skills to install the MCP server (running terminal commands, editing a config file). Once installed, you interact with it entirely through natural language — no coding required.
Is MCP the same as a plugin or extension?
MCP is similar in concept to plugins but uses a standardized, open protocol. Unlike proprietary plugin systems, MCP servers work with any compatible AI assistant.
Can I use MCP with other AI assistants besides Claude?
MCP is an open protocol. Any AI assistant that implements the MCP client specification can connect to MCP servers. Claude Desktop currently has the best MCP support.
Does using MCP cost extra credits?
MCP tool calls consume the same credits as equivalent API calls or UI actions. There is no additional charge for using MCP.
How many MCP servers can I connect at once?
There is no practical limit. You can connect AutoReach, your CRM, your calendar, and other tools simultaneously. The AI assistant intelligently chooses which tools to use based on your requests.
Getting Started
- Generate an API key in AutoReach Settings
- Install the AutoReach MCP server
- Configure it in Claude Desktop
- Start with simple queries ("Show my workflows", "Check my credit balance")
- Progress to more complex operations as you get comfortable