Labsco
MCP SERVER · OFFICIAL PROJECT

Outreach MCP Server

by Outreach ↗

Prepare for calls from Kaia recordings and deal data, build sequences and create tasks in Outreach, within your own permissions.

CRM & Sales Pipeline✓ Popular vendor Official
Needed to connect
An account, signed in with OAuth
Tools
44 · from the project's docs
Setup effort
Admin enables it, then paste and authorize
Source
Popular vendor Official

Call prep built from recordings, deals and emails in Outreach.

Before a call, it assembles what Outreach holds on the account, including the deal, recorded calls and emails, and from the same conversation it can enroll prospects or set follow-ups.

What it is

A remote MCP server Outreach runs at api.outreach.io/mcp, for Claude, ChatGPT, Microsoft Copilot, Gemini, VS Code and other AI tools. It sees only the Outreach data your own user profile is allowed to see. In Claude, Outreach recommends its official Outreach connector over adding this address yourself.

What you get

  • Kaia call and meeting recordings searched by topic, account, deal or participant, with transcripts and summaries
  • Emails, calendar events and tasks looked up, and new tasks created
  • Accounts, prospects and deals (opportunities) found by name or CRM ID, and new ones created
  • Questions answered about an account or deal from its record and call transcripts
  • Sequences found and created, prospects added or removed, and their progress tracked
  • Users, teams and your org's stages, schedules and rules looked up
  • With deleting allowed by an admin: accounts, prospects, deals and sequences deleted, each after you confirm

Requirements

  • An active, licensed Outreach seat, in an organization that has the Amplify add-on with active credits.
  • If you are not sure about Amplify, ask your Outreach account executive.
  • An Outreach admin first switches on the MCP Server under Administration > Organization > Org Info.
  • Creating records is allowed by default; deleting stays off until the admin allows it.
  • It can create and delete records but not edit existing ones, so make those changes in Outreach itself.
  • You sign in with your Outreach credentials in your browser, plus multi-factor authentication if your organization requires it.
  • Sign in to the right Outreach account in your default browser first, since the sign-in picks up whichever account is open there.

Setup effort

Admin enables it, then paste and authorize — add the endpoint to your client, then approve the OAuth consent screen