Nooks MCP server icon

Nooks

by Nooks

HIPAA CompliantSOC2 ReadyISO 27001 Ready
Productivity37 tools

Query a Nooks sales-engagement workspace — prospects, sequences, calls, tasks and call transcripts — from an AI agent. Anthropic's directory lists zero tools; Nooks documents 37 of them. OAuth 2.0 with PKCE and 25 advertised scopes.

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.

Connect Nooks via MCP

https://mcp.nooks.in/mcp

Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.

Nooks Tools & Capabilities (37)

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • Anthropic's directory publishes no tool names for this connector. The entry we hold, dated 2026-08-16, carries an empty list. Every tool name on this page comes from Nooks' own documentation, cross-checked between its Claude and ChatGPT articles and against its OpenAPI specification.
  • The scope descriptor and the connector documentation disagree. The server advertises 25 scopes; the documented table names 17. We could not find vendor documentation for desktop-notes:read in either source, and Nooks' own API scope table omits coaching:read, teams:read, email-templates:read and desktop-notes:read while the server advertises all four.
  • Advertised scopes are not observed enforcement. Nooks documents INSUFFICIENT_SCOPE errors on write endpoints, and states scope is enforced per user per request. We did not authenticate, so we did not observe any scope check. Treat the boundary as documented rather than verified.
  • Enrolment and task completion can send. No connector tool sends directly, but createSequenceState, completeTask and skipTask can each cause an automated email or SMS to go out, depending on how the sequence is configured. The tool names do not carry that.
  • Only one workspace at a time. Nooks states the connector supports a single workspace per connector instance. Switching means disconnecting and reconnecting.
  • Sequencing data only. Nooks states the connector cannot see tasks or sequences created in another sales-engagement platform — Outreach, Salesloft, Apollo, Gong Engage and Groove are named — nor tasks created manually in your CRM, nor CRM data not yet synced into Nooks.
  • Rate limits are per workspace and per endpoint, in a fixed one-minute window, with separate buckets that do not share quota: 300/min for list reads, 600/min for reads by ID, 120/min for sequence, step, enrolment and task writes, 30/min for CRM note writes, 10/min for prospect sync, and 30/min shared default for anything else. Exceeding one returns 429 with Retry-After.
  • List results default to 25 records in the connector. Nooks notes that broad requests such as "all emails in the last year" cause Claude to page through results and may warn before a large fetch. Narrow by date range or sequence.
  • CRM sync lags. Nooks states a prospect added to your CRM less than 15 minutes ago may not have synced yet, and recommends searching by email rather than name because names match loosely.
  • Revocation takes two steps. Nooks states access tokens last up to one hour and refresh tokens rotate, so disconnecting in Claude is not enough on a custom connector — you must also revoke the OAuth app in Nooks under Settings → All Settings → Developer → OAuth Apps.
  • We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous initialize on 2026-08-22, so no parameter-level detail for the MCP tools is published here. Parameter claims on this page come from the REST operation of the same name in Nooks' OpenAPI specification.

Frequently asked questions

Thirty-seven. Anthropic's directory entry lists no tool names at all, so the count comes from Nooks, which publishes the same 37 in two separate help articles — one for Claude and one for ChatGPT. Both name every tool and group it by resource. The directory's empty list is a gap in the listing, not a sign that the surface is user-defined.

Not directly, but it can cause one to be sent. Nooks states the connector cannot send outbound emails or place calls itself. It can enrol a prospect in a sequence, and a sequence step of type auto_email sends without further human action. Nooks also states that marking a task complete may trigger a downstream automated email.

Yes, through enrolment. Nooks' API documents an emailOverrides parameter on the enrol operation that sets a custom subject and HTML body per sequence step, overriding the step's template. Enrolling into a sequence whose step is auto_email therefore sends agent-authored text to a real person. The tool name createSequenceState gives no hint of this.

Twenty-five, read from the server's own RFC 9728 descriptor on 2026-08-22. The connector help article's scope table lists only 17 of them. The eight it omits include three write scopes — emails:write, calls:write and sequences:write — plus sequence-steps:write and notes:write. The descriptor is the authoritative list.

Nooks says yes; least privilege says no. Nooks' OAuth setup guide instructs admins to grant every available scope, arguing that restricting them causes tool calls to fail in ways users cannot diagnose. That advice is operationally sound and grants the write scopes too. Nooks' counter-argument is that seat assignment still gates tool access per user.

Yes, two things. deleteTask permanently deletes a task, and deleteSequenceState removes a prospect from a sequence, deleting the enrolment and cancelling every pending task attached to it. Nooks labels both destructive in its own tool table. Neither is reversible from the connector, and no tool restores a cancelled enrolment.

Prospect records, email bodies and full call transcripts. A prospect carries name, job title, primary email, LinkedIn URL and CRM custom fields. Emails return their bodies and delivery tracking. getCallTranscript returns speaker-labelled, timestamped turns of a recorded sales call, which means the other party's words enter the agent's context.

Because your tool list depends on your Nooks seats. Nooks states that searchCalls and getCallTranscript require a Nooks AI Coaching seat, and they only cover calls made by reps who also hold one. Sequencing tools require a Sequencing seat. Granting a scope on the consent screen does not add a tool your seat does not carry.

Yes. Nooks states that both the official directory connector and a custom OAuth connector work with Claude Code and the Claude API, and that the same https://mcp.nooks.in/mcp URL works for any MCP-compatible client. Nooks Desktop, the Anthropic API and third-party MCP clients all connect the same way.

Sources

Use in Agentman

Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio

Server Info

Category
Productivity
Developer
Nooks
Tools
37
Domain
mcp.nooks.in

Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.