# Quick orientation
- Saleshandy MCP: full-stack cold outbound — prospecting, sequences, sending, deliverability, campaign metrics. Good if you want one MCP to handle most outbound tasks.
- Apollo MCP: contact data and sequence enrollment — strong for pulling contacts and putting them into sequences.
- Clay MCP: AI-powered lead enrichment — useful when you need firmographic and tech-stack enrichment on existing lists.
- ZoomInfo MCP: enterprise B2B intelligence — better when you prioritize depth and scale of contact data.
- HubSpot MCP: CRM automation — focused on automating CRM records and pipeline tasks.
- Salesforce MCP: enterprise RevOps workflows — fits teams that run Salesforce-centric operations.
- Instantly MCP: cold email campaign management — built around sending and campaign control.
- Smartlead MCP: email deliverability monitoring — use when sender health and placement are priorities.
- Outreach MCP: for existing Outreach customers — best if the team already uses Outreach.
- Lemlist MCP: multichannel outreach — suited for teams mixing email and other channels.
# What an MCP server actually does
# Read-only vs read-write — a decisive permission
# Choosing the right MCP server for your team Start with the workflow you want to automate. If you need prospecting + sending in one place, favor a full-stack MCP (Saleshandy). If you only need contact enrichment, pick an enrichment-first MCP (Clay or ZoomInfo). If deliverability matters, choose Smartlead or Instantly. If your org runs HubSpot or Salesforce, prefer their MCPs for deeper CRM actions.
Check these specifics before you connect: access type (read vs write), supported actions, data sources and database size, deliverability features, and how errors/edge cases are surfaced.
# Practical cautions and common mistakes
- Don't connect without reviewing auth scopes and session expiry behaviors.
- Don't rely solely on AI for campaign launches until you've audited deliverability and monitoring.
# Bottom line The MCP landscape is diverse: some servers focus on data, others on outreach, and a few try to cover the full sales stack. Match the server to your immediate automation goal, confirm read/write capabilities, and plan for security and deliverability checks before you hand over production workflows.