Outreach
by Outreach
Query prospects, accounts, opportunities, sales emails and Kaia call transcripts from your AI assistant. 15 listed tools against 42 the vendor documents, OAuth 2.1 sign-in, and a Read Only label Outreach's own docs contradict.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Outreach via MCP
https://api.outreach.io/mcp/Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Outreach Tools & Capabilities (15)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- The "Read Only" label is wrong. Outreach documents 13 write tools, five annotated destructive. Outreach's own description of its design is read-only, create and delete tools.
- You cannot update a record. Outreach ships no update tools, and states the reason: internal testing found language models unpredictable when modifying existing records. Create and delete work; edit does not.
- The directory's 15 tool names are all superseded. Not one matches Outreach's documented vocabulary exactly, and
user_search_by_namis truncated even within its own listing. Discover tools at runtime. - Outreach's own developer portal disagrees with itself three ways. Its tool catalogue page is titled 42 tools, its index and authentication pages both say 32, and an internal anchor on the annotations page says 21. We could not arbitrate; the endpoint is gated.
- The annotations documentation contradicts the catalogue on
openWorldHint. The catalogue states all tools advertiseopenWorldHint: false; the annotations page states all have ittruebecause they reach Outreach's backend. Both were retrieved 2026-08-18. - One placeholder scope, not a permission boundary.
scopes_supportedis["prospects.all"]while the server reaches accounts, opportunities, sequences, tasks, users and Kaia transcripts. The real boundary is your RBAC profile, applied after the token is issued. - Amplify is a hard gate. No Amplify add-on with active credits, no MCP server — the org toggle is greyed out. Outreach publishes no MCP pricing and directs customers to their account executive.
- Dynamic client registration is open. Outreach offers no server-side allowlist of which MCP clients may connect, and directs enterprises to IDP-level controls instead.
- Rate limits are per user and stricter for Kaia. 10,000 requests per hour per user; Kaia recordings and transcripts capped at 3 per second and 6,000 per day at org level. Outreach notes that one natural-language question can become many tool calls, and that the number is non-deterministic.
- No prompts and no resources. Outreach states it exposes neither, matching the directory's empty
prompt_names. There are no one-click report templates on this connector. - The feature was still rolling out at the time of writing. Outreach's page carries a pending rollout banner covering 13 August to 1 September 2026, so availability varies by organisation.
- Endpoint punctuation differs between sources. Anthropic's directory publishes the URL with a trailing slash; Outreach's setup instructions give it without one. This page uses the directory's form, which is what the copy-paste command above carries.
Frequently asked questions
Is the Outreach MCP connector really read only?
No. Anthropic's directory labels it Read Only, and Outreach's own documentation describes thirteen write tools that create records, enrol prospects in sequences and delete accounts, prospects, opportunities and sequences. Outreach states its deliberate product choice was read-only, create and delete tools. What the connector genuinely cannot do is edit or update an existing record.
Which Outreach plan do I need for the MCP server?
The Amplify add-on package, with active credits. Outreach states the organisation must have Amplify enabled and the user must be an active, licensed seat on at least one Outreach instance. Outreach directs customers without Amplify to their account executive. The setup toggle appears greyed out in organisation settings when the add-on is missing.
Can an admin turn the Outreach MCP server off for the whole organisation?
Yes. Outreach documents an org-level toggle under Administration, Organization, Org Info, Gen AI, available only to admins. The server is off until an admin enables it, and the setting exposes only that instance's data. Two sub-settings control writes separately: create actions default to on, delete actions default to off.
What can the Outreach MCP server see about my prospects?
Exactly what your own Outreach login can see, and nothing more. Outreach states it enforces the RBAC profile assigned to your user account on every MCP tool call, the same permissions that govern the web app. It also requires an active account and a valid licence before sharing any data over MCP.
Does the Outreach MCP server give an AI assistant my call recordings?
Yes, including transcripts. Outreach documents two Kaia tools that search recorded meetings and fetch full call detail with summaries and transcripts. Access follows your profile permissions, so you reach only meetings you are already authorised to view. Outreach applies a separate org-level rate limit to Kaia of three calls per second.
Can I edit or update existing records with Outreach MCP tools?
No, and Outreach explains why. It states that internal testing showed language models behave unpredictably when updating existing records, risking detrimental business impact for customers. Outreach therefore shipped read, create and delete tools but no update tools. Records can be created and deleted through MCP, but never modified in place.
What does the ext_id in the Outreach MCP tool names refer to?
An identifier from an external system, most often your CRM. Outreach documents three lookup tools that resolve an account, prospect or opportunity by an ID held in another system such as Salesforce. Outreach's own developer guidance recommends using external ID searches to bridge an agent to your system of record.
Are Outreach MCP calls attributed to me in the audit trail?
Yes. Outreach states that tool calls appear in its activity history attributed to the authenticated user, the same as actions taken in the web interface. Access revocation runs through your identity provider rather than through Outreach when SSO is in use. Disabling the user at the IDP immediately revokes MCP access.
Sources
- Outreach MCP Server Overview, Outreach support (fetched 2026-08-18; the directory's
hc/en-us/articles/46370115253403URL 301s here) · retrieved 2026-08-18 - Outreach MCP tool catalogue (fetched 2026-08-18 as Markdown via the host's
llms.txtindex) · retrieved 2026-08-18 - Outreach MCP tool annotations (fetched 2026-08-18) · retrieved 2026-08-18
- Outreach MCP authentication (fetched 2026-08-18) · retrieved 2026-08-18
- Outreach MCP best practices, usage guide and sample interactions (fetched 2026-08-18) · retrieved 2026-08-18
- Outreach API rate limiting (fetched 2026-08-18) · retrieved 2026-08-18
- Outreach privacy statement
- Live
WWW-Authenticatechallenge and RFC 9728 / RFC 8414 descriptors onapi.outreach.io— 2026-08-18 · retrieved 2026-08-18 - Anthropic connector directory (snapshot 2026-08-16) · retrieved 2026-08-16
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Sales & CRM
- Developer
- Outreach
- Tools
- 15
- Domain
- api.outreach.io
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.