6sense
Ask an AI agent about 6sense account insights, buying signals and keyword trends.
Query a Nooks sales-engagement workspace — prospects, sequences, calls, transcripts.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Nooks MCP server connects a Nooks sales-engagement workspace — the dialer, sequencer and call-coaching platform outbound teams run their day from — to Claude, ChatGPT and any MCP-compatible agent. Nooks documents 37 tools that read prospects, sequences, calls, emails and transcripts, and that enrol prospects, manage tasks and unenrol people. Sign-in is OAuth 2.0 with PKCE.
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.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
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.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.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.Retry-After.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.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.
initialize to https://mcp.nooks.in/mcp returned 401 with WWW-Authenticate: Bearer ... resource_metadata="https://mcp.nooks.in/.well-known/oauth-protected-resource"; that descriptor returned 25 scopes_supported; authorization server metadata at https://oauth.nooks.in/.well-known/oauth-authorization-server confirms PKCE S256 and client_secret_post (2026-08-22) · retrieved 2026-08-22robots.txt at nooks.help.usepylon.com is a named-bot whitelist that explicitly permits ClaudeBot, Claude-User and Claude-SearchBot, and publishes a sitemap; no Content-Signal directive is present (checked 2026-08-22) · retrieved 2026-08-22Connect Nooks once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.