Abency
Run a marketing agency's social, SEO, ads, WordPress and email from an AI agent.
Query prospects, accounts, opportunities and Kaia call transcripts.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Outreach MCP server connects the Outreach sales engagement platform to Claude, ChatGPT and any MCP-compatible agent. Anthropic's directory lists 15 read tools; Outreach's own developer documentation catalogues 42, including thirteen that write. Sign-in is OAuth 2.1 with dynamic client registration, and the whole server stays dark until an Outreach admin switches it on.
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.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
user_search_by_nam is truncated even within its own listing. Discover tools at runtime.openWorldHint. The catalogue states all tools advertise openWorldHint: false; the annotations page states all have it true because they reach Outreach's backend. Both were retrieved 2026-08-18.scopes_supported is ["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.prompt_names. There are no one-click report templates on this connector.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.
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.
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.
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.
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.
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.
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.
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.
hc/en-us/articles/46370115253403 URL 301s here) · retrieved 2026-08-18llms.txt index) · retrieved 2026-08-18WWW-Authenticate challenge and RFC 9728 / RFC 8414 descriptors on api.outreach.io — 2026-08-18 · retrieved 2026-08-18Connect Outreach once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.