# Outreach: MCP server status, API access gate and what it does > Sales engagement platform for building, running, and tracking multichannel outbound sequences (email, call,... Official MCP, Enterprise only. Checked 2026-09-02. *Markdown twin of the HTML page at the same path. Same content, no navigation, no styling, no scripts. Links below point at other twins. Site map for machines: [llms.txt](../llms.txt). The whole dataset: [directory.json](../data/directory.json).* *Maintained by Andrew McGuire (https://andrewcmcguire.com), who also publishes https://gtmsignals.co and https://justsaid.ai.* --- [Directory](../index.md) / [Engagement & Outbound](../categories/engagement-outbound.md) / Outreach # Outreach [Official MCP](../mcp/official.md) [Enterprise only](../gates/enterprise-only.md) [Engagement & Outbound](../categories/engagement-outbound.md) RESEARCHED Checked 2026-09-02 > **RESEARCHED** Facts from public sources with URLs. No usage claims. Nobody has run this tool. The other tier is BENCH-TESTED, which means Andrew personally ran the tool on a stated date and cannot be bought at any price. Across the whole directory that count is 1. Vendor: [outreach.ai (outreach.io 301s here as of 2026-09-02; the API and MCP endpoints remain on api.outreach.io and support docs on support.outreach.io)](https://outreach.ai (outreach.io 301s here as of 2026-09-02; the API and MCP endpoints remain on api.outreach.io and support docs on support.outreach.io)) · entry id 02-outreach · source 02-engagement-outbound.md line 7 **What it does** Sales engagement platform for building, running, and tracking multichannel outbound sequences (email, call, social) and rep activity, tied into a CRM. **AI features, separated from automation with an AI label on it** Vendor markets "AI Agents" that act across the customer lifecycle, AI-assisted forecasting/pipeline projection, and real-time conversation intelligence (AI battle cards, objection handling, action-item detection during calls). None of the underlying model mechanics are disclosed publicly - these are vendor-stated capabilities, not independently verified. **RevOps role** Core outbound execution layer between prospecting/data tools and CRM - cadence orchestration, call/email logging, activity data feeding forecasting. **MCP server** - **Status bucket**: Official MCP - **Auth**: OAuth 2.1 with Dynamic Client Registration; also requires the org-level "Amplify" add-on to be enabled and admin-toggled - not available to every customer by default. - **Parsed URLs**: 2 found in the mcp_url field - **Endpoint probe**: auth wall at every path, not proven a server - **Endpoint URL**: [https://api.outreach.io/mcp/](https://api.outreach.io/mcp/) - **Probed**: 2026-09-04, HTTP 401 The vendor ships and maintains the server itself. A wrapper built by Zapier, Composio or a similar third party does not count as official. The status was established by hand on 2026-09-02. On 2026-09-04 the recorded URL answered an auth challenge, but so did a path on that host which cannot exist, so the challenge proves a wall rather than a running MCP server. mcp_status, verbatim from the file: official mcp_url, verbatim from the file: https://api.outreach.io/mcp/ ; overview at https://support.outreach.io/support/solutions/articles/159000425158-outreach-mcp-server-overview - [https://api.outreach.io/mcp/](https://api.outreach.io/mcp/) - [https://support.outreach.io/support/solutions/articles/159000425158-outreach-mcp-server-overview](https://support.outreach.io/support/solutions/articles/159000425158-outreach-mcp-server-overview) **What this server exposes** Not harvested yet. Unmeasured, not empty: nobody has read this server's tool list, so this page says nothing about what it exposes. 141 of the 741 entries that record an official or community MCP server carry a harvested tool list. The other 600 are unmeasured, which is not the same as empty. Harvest last run 2026-09-27. The full roll up is on the [tools index](../tools-index.md). **Command line** No CLI found by the 2026-09-27 harvest across vendor docs, npm, PyPI, Homebrew and GitHub. That is a probe result, not proof of absence. **Access gate** - **Gate bucket**: Enterprise only - **Can a solo operator reach it**: Not without a contract api_gate, verbatim from the file: enterprise-only (all four Amplify tiers list API call allowances of 250,000 to 1,000,000 plus Outreach MCP, but no prices are published and every tier routes to custom pricing from the sales team) **API documentation** No documentation URL recorded. 727 of 1252 entries are in the same position. Blank is legal and it is published as blank. **GitHub health** Not measured. github_url, github_stars, github_last_commit and github_archived are null on every entry in this build. The refresh rail specced in SPEC section 7.2 has not been run. An unstamped star count is a lie, so nothing is shown rather than something stale. **On GitHub** No GitHub organisation could be tied to outreach.ai with evidence on 2026-09-08. Recorded by the harvest: github candidates were seen but none passed the evidence rules. 5 candidate accounts seen and rejected by the evidence rules: getoutreach, galaxyproject, ACM-VIT, csivitu, outreachy. A name match alone is never accepted; the account has to point at the vendor domain. **Jobs it can do** - [Run an email sequence](../jobs/run-email-sequence.md) - [Send a LinkedIn message or connection request](../jobs/send-linkedin-message.md) - [Draft personalized outreach](../jobs/draft-personalized-outreach.md) - [Place an outbound call](../jobs/place-outbound-call.md) - [Read outreach performance](../jobs/read-outreach-performance.md) - [Extract deal signals from calls](../jobs/extract-deal-signals-from-calls.md) - [Write CRM records](../jobs/write-crm-records.md) - [Read the pipeline forecast](../jobs/read-pipeline-forecast.md) A job tag means the vendor says the tool does this. It is not a test result, not proof the capability is reachable through the tool's MCP server, and not proof it is available on the gate this entry records. Tagged by machine-pass on 2026-08-25 against the closed 56 job vocabulary. 271 of 1,252 entries carry at least one tag; 849 tags are assigned in total. **Sources** - [https://support.outreach.io/support/solutions/articles/159000425158-outreach-mcp-server-overview](https://support.outreach.io/support/solutions/articles/159000425158-outreach-mcp-server-overview) - [https://support.outreach.io/support/solutions/articles/159000426361-where-are-the-outreach-development-portal-and-api-documentation-](https://support.outreach.io/support/solutions/articles/159000426361-where-are-the-outreach-development-portal-and-api-documentation-) - [https://developers.outreach.io/](https://developers.outreach.io/) - [https://www.outreach.ai/product](https://www.outreach.ai/product) - [https://www.outreach.ai/pricing](https://www.outreach.ai/pricing) 5 source URLs. Raw sources field, verbatim: https://support.outreach.io/support/solutions/articles/159000425158-outreach-mcp-server-overview, https://support.outreach.io/support/solutions/articles/159000426361-where-are-the-outreach-development-portal-and-api-documentation-, https://developers.outreach.io/, https://www.outreach.ai/product, https://www.outreach.ai/pricing **Notes, verbatim from the file** The official MCP server is gated behind the paid "Amplify" add-on plus admin enablement, not a free-for-all connector. Base API access requires requesting developer-portal access; no public self-serve pricing found, so api_gate is left unknown rather than assumed. Community/read-only alternatives also exist (github.com/ZLeventer/outreach-mcp-server, github.com/CDataSoftware/outreach.io-mcp-server-by-cdata). [api_gate 2026-08-25] Reclassified unknown -> enterprise-only from the vendor's own page (https://www.outreach.ai/pricing): all four Amplify tiers list API call allowances of 250,000 to 1,000,000 plus Outreach MCP, but no prices are published and every tier routes to custom pricing from the sales team. 2026-09-02: vendor_url corrected from outreach.io to outreach.ai. https://www.outreach.ai/pricing loaded on that domain today with four tiers named Amplify Essentials, Amplify Core, Amplify Plus and Amplify Pro, each listing "Outreach MCP (Server & Client)" plus 250,000, 250,000, 500,000 and 1,000,000 API calls respectively. The MCP overview at https://support.outreach.io/support/solutions/articles/159000425158-outreach-mcp-server-overview still resolves and still documents the endpoint https://api.outreach.io/mcp with OAuth 2.1 and Dynamic Client Registration, requiring the Amplify add-on with active credits and a licensed seat. mcp_status official unchanged. **Provenance** - **Entry id**: 02-outreach - **Source file**: 02-engagement-outbound.md - **Source line**: 7 - **Tier**: RESEARCHED - **last_checked**: 2026-09-02 - **Data baked**: 2026-09-27 Every field above is rendered from directory.json exactly as the build produced it. Nothing is summarised and nothing is dropped. The one change made at render time is typographic and it is disclosed on the [methodology page](../methodology.md).