Outreach MCP Server

Summary

Outreach MCP Server allows other AI Agents to utilize Outreach knowledge directly inside their workflows. Outreach acts as a server (producer) of knowledge.

Outreach MCP Server is built to support Anthropic’s Model Context Protocol (MCP) standard and can be utilized by any MCP Client that follow the MCP standards. Any user who wants to utilize Outreach MCP Server will need to be active and licensed in an Outreach instance and have Amplify enabled.

What is MCP?

AI applications are only as useful as the knowledge they can generate from the data they have access to. The real world is a landscape of disconnected data islands, hosted in their own servers and controlled by the hosting product. For useful and usable experiences AI applications need to connect to these data sources. This is where MCP or Model Context Protocol (MCP) comes in.

MCP is an open-source standard from Anthropic for connecting AI applications to external systems for knowledge and actions that the local system doesn’t have. MCP standardizes how LLMs communicate with each other. Think of MCP as context in motion – your Outreach AI can share or draw to and from the broader ecosystem of tools your company already uses, and those systems can talk back to Outreach.

You can learn more about MCP from Anthropic’s official documentation.

Outreach MCP Server

In a Server capacity, Outreach is a producer of knowledge and facilitator of actions for MCP Clients. Other AI Agents, or end users, can now utilize Outreach’s data and draw best in class insights directly inside their Revenue workflows.

Outreach MCP Server is available to all Outreach customers to connect to. While it’s an authenticated, open Server it is expected to be most useful for MCP Clients that integrate Outreach value into their workflows and end user experiences.

Outreach envisions that customers can use Outreach exposed MCP Tools in all sorts of applications include LOB tools, open MCP Clients like Claude, OpenAI, Slack, and in chat applications like Agentforce or CoPilot.

Above is not an exhaustive list. We’re constantly adding more tools through collaboration with our customers and creating innovative scenarios with partners.

Setup

Enabling Outreach MCP Server

Before MCP Clients can connect to it, Outreach MCP Server will need to be enabled. This setting is per organization and only exposes the data of that specific instance. This action is only available to the organization admin.

To enable MCP Server, go to your Administration (settings) > Organization > Org Info > Gen AI > MCP Server and enable the toggle.

Authentication

Outreach enforces that only authenticated, authorized and licensed users can connect to the Server. We also require that the instance, and the user, has Amplify enabled. For supported features, Outreach follows MCP’s Authorization standards as published on November 11, 2025.

To access Outreach tools, the user must sign in with their Outreach credentials and provide any additional factors required by their organization.

Using Outreach with MCP Clients

For the purposes of this documentation, we’ll use Claude desktop as an example. Note that any MCP Client can connect to Outreach Server and utilize its knowledge and insights as long as the user is able to authenticate with their credentials against Outreach.

To set up Outreach MCP Server, go to Claude Desktop > Settings > Connectors > Add custom connector:

In the ‘Add custom connector’ dialog enter the following information:

1. Name – Outreach MCP Server (or your preferred name)
2. Server URL – https://api.outreach.io/mcp

You can skip the Advanced settings and click on ‘Add’

Make sure that Claude was able to successfully add the Outreach MCP Server connector. The next step would be to enable the server to connect to Claude. To do that, hit the ‘Connect’ button next to Outreach MCP Server:

This will open a browser window. Sign in with your Outreach credentials. If you have multiple instances, make sure you’re using the credentials the MCP Server of the organization you want to connect to:

Complete authentication by providing multi-factored authentication if required by your organization. Once you have successfully authenticated, Outreach will prompt you to consent to the information that will be shared with Claude (or another MCP client if you’re not using Claude):

Once you have authenticated and provided consent, Claude will be connected to Outreach MCP Server and will be ready for you to run some queries.

Experience

MCP is a standalone protocol and can be utilized by any end user GenAI application that can support the protocol. This opens a whole world of possibility on how best to utilize Outreach’s knowledge inside your daily workflows.

With GenAI, the most common experiences are either a chat based (user initiated) interaction or Agent to Agent autonomous collaboration. Let’s look at those closely.

Chat experience

Outreach MCP Server can be connected directly with GenAI (LLM) chat experiences within Agentforce, CoPilot, OpenAI etc. or your LOB applications, once you have set up the MCP clients. You can run queries as you would generally do as part of your daily revenue workflows and the chat should be able to connect automatically to Outreach MCP Server and display insights and knowledge from Outreach.

Agent to agent autonomous collaboration

If you are running Agentic AI that is fully autonomous (for example, task completions, automatic workflow execution etc.), these agents can also utilize insights and knowledge from Outreach MCP Server as part of their flow.

From MCP point of view, these are fundamentally the same client à server communication as chat-based interaction. The key difference is that in this case the Agent will run fully autonomously.

Outreach MCP Tools

Outreach exposes the following tools:

1. Workflow Tools:
   • Retrieve transcripts from Kaia calls – fetch_kaia_meetings
   • Retrieve email content – emails_search
   • Lookup existing sequences – sequence_search_by_name
2. Prospecting Tools:
   • Lookup prospect by account IDs – prospect_get_by_id
   • Lookup prospect by account name – prospect_search_by_name
   • Lookup prospect by external IDs like CRM IDs – prospect_search_by_ext_id
3. Account Tools:
   • Lookup account by account IDs – account_get_by_id
   • Lookup account by account name – account_search_by_name
   • Lookup account by external IDs like CRM IDs – account_search_by_ext_id
4. Deal Management Tools:
   • Lookup opportunity by opportunity IDs – opportunity_get_by_id
   • Lookup opportunity by opportunity name – opportunity_search_by_name
   • Lookup opportunity by external IDs like CRM IDs – opportunity_search_by_ext_id
5. User Tools:
   • Lookup user by user IDs – user_get_by_id
   • Lookup user by username – user_search_by_name
   • Lookup user by user IDs like CRM IDs – user_search_by_ext_id

Exact configuration of the tools and sample responses can be found in our developer documentation. At this moment, Outreach has not exposed any resources or prompts.

We are always refreshing the list of available tools, so please keep an eye on this documentation for future enhancements. 

FAQ

Where can I find MCP clients I can use?

MCP allows you to use any compliant client to connect to servers and you are welcome to use any well-known MCP Clients.

To try out Outreach MCP server, the fastest way would be to use Claude or. For more technically minded people you can also use Visual Studio CoPilot.

Outreach MCP Server really shines when the knowledge and insights show up in daily revenue flows. If your organization has access to Salesforce Agentforce, Microsoft CoPilot, Google Gemini, they all support connecting to MCP Servers and provides an integrated experience.

You can also use tools like Slack or Microsoft Teams if you want to use Outreach directly into your team selling communication workflows.

Some organizations might have restrictions on and might restrict usage of public MCP Clients. Your organization admin would be the best group to reach out to. At minimum your organization will need to enable MCP Server for your Outreach instance before you can use it.

Can a MCP client connect to multiple Outreach instances?

One client can only connect to one server per MCP protocol. However, you can create an MCP host to connect to multiple Outreach MCP servers if the host is able to maintain credentials from multiple accounts. This is not something Outreach controls and you’ll need to refer to the documentation of your host AI Application.

Which version of MCP Spec does Outreach support?

For supported features, Outreach follows MCP’s Authorization standards as published on November 11, 2025.