# Nooks
ID: 02-nooks
Page: https://gtmmcps.com/tools/02-nooks
JSON: https://gtmmcps.com/data/tools/02-nooks.json
Documentation references: https://gtmmcps.com/docs/02-nooks/
Category: Engagement & Outbound
MCP support: official
Testing: RESEARCHED
API access: enterprise-only
Last checked: 2026-09-02
Endpoint check: live-auth-gated; date: 2026-09-04

AI parallel dialer and "virtual salesfloor" combining multi-line dialing, live manager coaching, and prospecting assistance for SDR teams.

## MCP links
- https://mcp.nooks.in/mcp
- https://mcp.nooks.in/.well-known/oauth-authorization-server

## Sources
- 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
- https://mcp.nooks.in/.well-known/oauth-authorization-server
- https://tedix.dev/apps/nooks/
- https://www.linkedin.com/pulse/nooks-product-release-mcp-servers-bonus-numbers-dialing-jortberg-gjjsc

## Research notes
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. [api_gate 2026-08-25] Reclassified unknown -> enterprise-only from the vendor's own page (https://www.nooks.ai/pricing): pricing is quote-only; self-serve OAuth app creation exists but requires workspace admin plus a Nooks Sequencing or Coaching seat. 2026-09-02: CHANGED none-found -> official. A first-party endpoint answers at https://mcp.nooks.in/mcp (HTTP 405 to a plain GET, the expected response of a streamable-HTTP MCP server that only accepts POST) and https://mcp.nooks.in/.well-known/oauth-authorization-server returns OAuth metadata with issuer https://oauth.nooks.in, authorization, token and revocation endpoints, authorization-code flow and PKCE S256. The pointer came from a LinkedIn release note titled 'Nooks Product Release: MCP Servers, Bonus Numbers, Dialing' (login-walled, not read) and a third-party listing at tedix.dev/apps/nooks that names the same endpoint and reports 'Requires Login'. CAVEAT: developer.nooks.in, nooks.ai/llms.txt and a site search of nooks.ai contain no MCP documentation, the MCP registry returns nothing for nooks, and tedix reports protocol-handshake failures, so tools, scopes and plan gating are unverified. Official on the strength of a vendor-domain endpoint that answers; needs a hands-on connect before use on camera.

## Named capabilities
Tool names below are reported by sources. Their presence is not a successful call.

## CLI evidence
Status: none-found

Read current vendor documentation before configuring or running commands.