# Outplay: MCP server status, API access gate and what it does > Multi-channel sales engagement platform (email, phone, social, SMS) with an AI SDR product layered on top. No MCP found, Gate unknown. Checked 2026-08-24. *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).* --- [Directory](../index.md) / [Engagement & Outbound](../categories/engagement-outbound.md) / Outplay # Outplay [No MCP found](../mcp/none-found.md) [Gate unknown](../gates/unknown.md) [Engagement & Outbound](../categories/engagement-outbound.md) RESEARCHED Checked 2026-08-24 > **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 0. Vendor: [outplay.ai (formerly outplayhq.com, now 301-redirected)](https://outplay.ai (formerly outplayhq.com, now 301-redirected)) · entry id 02-outplay · source 02-engagement-outbound.md line 312 **What it does** Multi-channel sales engagement platform (email, phone, social, SMS) with an AI SDR product layered on top. **AI features, separated from automation with an AI label on it** Vendor advertises AI Mail Writer, AI Sequence Writer, AI Objection Handling, AI detection of out-of-office replies, an "AI SDR" autonomous-prospecting agent, and Conversation Intelligence. Transcription-based features (Conversation Intelligence, OOO detection) are plausible genuine AI/ML use; "AI SDR" autonomy level is vendor-stated and unverified. **RevOps role** Multichannel outbound sequencing with dialer and AI SDR add-on, competing directly with Klenty and Reply.io. **MCP server** - **Status bucket**: No MCP found - **Auth**: n/a - **Parsed URLs**: 0 found in the mcp_url field No server was found at the time of the check. That is a statement about the search, not a promise that none exists. The status was established on 2026-08-24 and has not been re-fetched since. mcp_status, verbatim from the file: none-found mcp_url, verbatim from the file: n/a **Access gate** - **Gate bucket**: Gate unknown - **Can a solo operator reach it**: Not established api_gate, verbatim from the file: unknown 83 of 293 entries carry an unknown gate. Unknown is a legal answer and it ships as unknown rather than as a guess. **API documentation** No documentation URL recorded. 263 of 293 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. **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) - [Run an autonomous SDR agent](../jobs/run-autonomous-sdr-agent.md) - [Extract deal signals from calls](../jobs/extract-deal-signals-from-calls.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 55 job vocabulary. 271 of 293 entries carry at least one tag; 827 tags are assigned in total. **Sources** - [https://outplay.ai/pricing/](https://outplay.ai/pricing/) - [https://outplay.ai/](https://outplay.ai/) 2 source URLs. Raw sources field, verbatim: https://outplay.ai/pricing/, https://outplay.ai/ **Notes, verbatim from the file** A Free Forever ($0) tier exists alongside Starter/Growth/Enterprise, but which tier includes API access was not confirmed from sourced pages. **Provenance** - **Entry id**: 02-outplay - **Source file**: 02-engagement-outbound.md - **Source line**: 312 - **Tier**: RESEARCHED - **last_checked**: 2026-08-24 - **Data baked**: 2026-08-25 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).