Back to MCP Servers

Outreach MCP Server

Official Outreach-hosted MCP server that exposes sales engagement data (accounts, opportunities, prospects, sequences, Kaia meetings) to AI agents.

Email & Outbound by Outreach OAuth2 active
Overview

The Outreach MCP Server is the official, Outreach-hosted Model Context Protocol endpoint that lets AI agents read sales engagement data and insights from an Outreach instance. Outreach acts as a "producer of knowledge" for MCP clients like Claude, ChatGPT, Microsoft Copilot, Gemini, and Agentforce, so revenue teams can pull deal context, meeting transcripts, and recommended next actions into their existing AI workflows without writing custom integrations.

The server exposes roughly 17 tools spanning prospects, accounts, opportunities, users, sequences, email content, and Kaia (Outreach's meeting AI) transcripts. Beyond simple lookups by ID, name, or external ID, it also offers higher-level question-answering tools (account_answer_question, opportunity_answer_question) that surface Outreach's native insights and best-next-action recommendations directly to the calling agent.

Access is gated by Outreach's standard authentication and RBAC: users must hold a licensed seat with the Amplify add-on enabled, an org admin must turn on the MCP Server toggle, and each user can only retrieve data their Profile permissions allow. Authentication follows the MCP Authorization standards published November 11, 2025, with full OAuth-style consent and optional MFA.

Tools

Tool Description
fetch_kaia_meetings Retrieve Kaia call transcripts and meeting recordings.
emails_search Search email content sent or received in Outreach.
sequence_search_by_name Look up Outreach sequences by name.
prospect_get_by_id Fetch a prospect by Outreach ID.
prospect_search_by_name Search prospects by name.
prospect_search_by_ext_id Look up a prospect by external (CRM) ID.
account_get_by_id Fetch an account by Outreach ID.
account_search_by_name Search accounts by name.
account_search_by_ext_id Look up an account by external (CRM) ID.
account_answer_question Ask a natural-language question about an account and return Outreach insights.
opportunity_get_by_id Fetch an opportunity by Outreach ID.
opportunity_search_by_name Search opportunities by name.
opportunity_search_by_ext_id Look up an opportunity by external (CRM) ID.
opportunity_answer_question Ask a natural-language question about an opportunity and return Outreach insights and next-best-action guidance.
user_get_by_id Fetch an Outreach user by ID.
user_search_by_name Search Outreach users by name.
user_search_by_ext_id Look up an Outreach user by external ID.
Setup Guide

Prerequisites

  • Outreach plan with the Amplify add-on enabled
  • Active, licensed user seat in your Outreach instance
  • Org admin access to enable the server

Step 1: Enable the MCP Server in Outreach

  1. Sign in to Outreach as an admin.
  2. Go to Administration > Organization > Org Info.
  3. Scroll to the GenAI section.
  4. Toggle MCP Server on.

Step 2: Connect from your MCP client

The server is hosted by Outreach at:

https://api.outreach.io/mcp

Claude Desktop (custom connector)

  1. Open Settings > Connectors > Add custom connector.
  2. Name: Outreach MCP Server
  3. Server URL: https://api.outreach.io/mcp
  4. Click Add, then Connect.
  5. Sign in with your Outreach credentials and complete MFA if prompted.
  6. Grant consent to share data with Claude.

Generic MCP client config

{
  "mcpServers": {
    "outreach": {
      "url": "https://api.outreach.io/mcp"
    }
  }
}

Authentication is performed interactively via OAuth in the browser; no API key is stored in the config file. Access is enforced by the user's Outreach Profile (RBAC), so the agent can only see data the signed-in user is allowed to see.

Use Cases
  • Pre-call prep: have an agent pull the latest Kaia meeting transcripts, open opportunities, and prospect history for an account before a sales call.
  • Deal coaching: ask Outreach for next-best-action guidance on a specific opportunity using opportunity_answer_question and surface it inside Claude or Copilot.
  • Sequence performance review: search sequences by name and compare reply or meeting rates across campaigns.
  • Cross-system context: let a CRM-side agent (Agentforce, Copilot) fetch just-in-time Outreach activity and email history for an account without leaving the CRM.
  • Pipeline Q&A: ask natural-language questions like "what changed on the Acme deal this week" and have the server return Outreach-native insights.
Example Prompts
  • "Help me prepare for my next call with Acme Corp, pull recent Kaia transcripts and open opportunities."
  • "What sequences from our Dreamforce campaign had the best reply rates?"
  • "Summarize the activity on opportunity 'Globex Renewal Q4' and recommend the next best action."
  • "Find the prospect John Doe at Initech and show their recent email engagement."
  • "Which accounts has rep jane@acme.com worked this month, and what stage are their opportunities in?"
Pros
  • Official, vendor-hosted server, no self-hosting or custom integration code required.
  • Enforces existing Outreach RBAC and licensing, so agent access cannot exceed the user's own permissions.
  • Includes higher-level question-answering tools (account_answer_question, opportunity_answer_question) that surface Outreach's native insights, not just raw records.
  • Works across major MCP clients including Claude, ChatGPT, Copilot, and Gemini.
Limitations
  • Requires the paid Amplify add-on and a licensed seat; not available on base Outreach plans.
  • Read-oriented surface area: the documented tools focus on lookup and Q&A, with no public write or sequence-enrollment tools.
  • Admin enablement is required, individual reps cannot turn the server on themselves.
Alternatives
  • Salesloft sales engagement platform (no official MCP server published as of this writing; community integrations only).
  • HubSpot MCP server (https://mcp.hubspot.com) for CRM and sequences in the HubSpot ecosystem.
  • Salesforce Agentforce / MCP integrations for CRM-side opportunity and account context.