# Nooks: MCP server status, API access gate and what it does > AI parallel dialer and "virtual salesfloor" combining multi-line dialing, live manager coaching, and... No MCP found, Gate unknown. Checked 2026-08-25. *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) / Nooks # Nooks [No MCP found](../mcp/none-found.md) [Gate unknown](../gates/unknown.md) [Engagement & Outbound](../categories/engagement-outbound.md) RESEARCHED Checked 2026-08-25 > **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: [nooks.ai](https://nooks.ai) · entry id 02-nooks · source 02-engagement-outbound.md line 45 **What it does** AI parallel dialer and "virtual salesfloor" combining multi-line dialing, live manager coaching, and prospecting assistance for SDR teams. **AI features, separated from automation with an AI label on it** Genuinely AI: sub-0.5-second pickup detection that filters voicemail/dead air across up to 5 parallel lines, AI call summaries/dispositions, AI roleplay-coaching bots trained on real call recordings, and "AI Prospector" for buying-signal detection and email drafting. Plain automation: the multi-line dialing mechanism itself, waterfall phone-number enrichment, and local-presence number rotation. Live "whisper coaching" is a human-manager feature, not AI. **RevOps role** Outbound calling execution and coaching layer, typically integrated with Salesforce/HubSpot and enrichment providers. **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-25 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** [https://developer.nooks.in/](https://developer.nooks.in/) No documentation text is reproduced anywhere on this site. Read the vendor page for the prose. The structured docs digest specced in SPEC section 3 has not been built or crawled: docs_digest is null on every entry in this build. **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. A github.com URL already appears somewhere in this entry, which is a seed for that rail and not a measurement of repo health: - [https://github.com/NooksApp](https://github.com/NooksApp) **Jobs it can do** - [Find a phone number](../jobs/find-phone-number.md) - [Fetch buyer intent signals](../jobs/fetch-buyer-intent-signals.md) - [Draft personalized outreach](../jobs/draft-personalized-outreach.md) - [Place an outbound call](../jobs/place-outbound-call.md) - [Summarize a meeting](../jobs/summarize-meeting.md) - [Score rep performance](../jobs/score-rep-performance.md) - [Run a sales roleplay practice](../jobs/run-sales-roleplay-practice.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://www.nooks.ai/ai-dialer](https://www.nooks.ai/ai-dialer) - [https://www.nooks.ai/ai-sequencing](https://www.nooks.ai/ai-sequencing) - [https://www.nooks.ai/pricing](https://www.nooks.ai/pricing) - [https://developer.nooks.in/](https://developer.nooks.in/) - [https://github.com/NooksApp](https://github.com/NooksApp) - [https://pipeline.zoominfo.com/sales/nooks-ai-zoominfo-gtm-ai-integration](https://pipeline.zoominfo.com/sales/nooks-ai-zoominfo-gtm-ai-integration) 6 source URLs. Raw sources field, verbatim: https://www.nooks.ai/ai-dialer, https://www.nooks.ai/ai-sequencing, https://www.nooks.ai/pricing, https://developer.nooks.in/, https://github.com/NooksApp, https://pipeline.zoominfo.com/sales/nooks-ai-zoominfo-gtm-ai-integration **Notes, verbatim from the file** No MCP server found on GitHub, mcp.so, glama.ai, or pulsemcp.com (pulsemcp returned zero results). A developer.nooks.in portal with OAuth2/API keys exists, but the pricing page only offers custom quotes with no disclosed API tier; the custom-quote sales motion suggests enterprise-leaning access, but that is inference, not a confirmed fact. RE-CHECKED 2026-08-25 on a specific pointer that Nooks had shipped something in the MCP/agent space. What was found is not a Nooks MCP server: it is Nooks positioning itself as an "Agent Workspace for Intelligent Outbound" (AI Dialing Assistant, AI Coaching Assistant, AI Prospector, AI Sequencing) and a native bidirectional integration with ZoomInfo's GTM.AI context layer, where mutual customers connect a ZoomInfo entitlement to Nooks through a native connector and Nooks engagement signals flow back through a Custom Data Connector inside ZoomInfo's GTM Studio. ZoomInfo's own write-up does not state whether Nooks consumes GTM.AI over MCP or over REST, and does not claim Nooks exposes an MCP server of its own. So Nooks is an MCP *consumer* story at best, not an MCP provider; mcp_status stays none-found. If Nooks ships a first-party server this is the entry to update. **Provenance** - **Entry id**: 02-nooks - **Source file**: 02-engagement-outbound.md - **Source line**: 45 - **Tier**: RESEARCHED - **last_checked**: 2026-08-25 - **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).