Setting Up a Nooks OAuth App for Custom Claude Connectors

Last updated: June 11, 2026

This guide describes the additional configuration required when creating a Nooks OAuth app intended for use as a Model Context Protocol (MCP) connection — for example, when connecting Nooks to Claude or another MCP-compatible AI assistant.

The general steps for creating an OAuth app — registering the application, retrieving client credentials, and implementing the OAuth 2.0 authorization-code flow — are covered in this guide. This page documents only the settings that differ for an MCP integration.

Background

An MCP connection exposes Nooks as a set of callable tools to an AI assistant. Because the assistant may invoke any of these tools on the user's behalf during a session, the OAuth application backing the connection must be configured to support the full range of MCP-exposed operations.

There are two configuration differences to be aware of when creating an OAuth app for this purpose:

  1. The redirect URIs must include the MCP client's authorization callback endpoints.

  2. The app must be granted all available scopes.

Redirect URIs

When creating the OAuth app, register the following redirect URIs so that the MCP client can complete the authorization flow:

https://claude.ai/api/mcp/auth_callback
https://claude.com/api/mcp/auth_callback

Both URIs are required. Claude initiates the OAuth flow from either the claude.ai or claude.com domain depending on how the user accesses the product, and the OAuth provider must permit redirects to both. If only one URI is registered, authorization will fail for a subset of users with a redirect_uri_mismatch error.

Scopes

Grant all available scopes to the OAuth app.

A typical OAuth integration follows the principle of least privilege and requests only the scopes its functionality requires. MCP connections are different: the application surfaces Nooks as a general-purpose toolset, and the AI assistant may legitimately need to call any endpoint that an authorized user could call. Restricting scopes would cause tool calls to fail at runtime in ways that are difficult for end users to diagnose.

Ensure every scope shown in the scope selector is enabled, including (but not limited to):

  • prospects:read, prospects:write

  • accounts:read

  • sequences:read

  • calls:read

  • emails:read

  • tasks:read, tasks:write

If Nooks introduces additional scopes in the future, update the OAuth app to include them so that newly added MCP tools continue to function.

Next Steps

Once the redirect URIs and scopes are configured, complete the app setup as described in this guide, including copying the Client ID and Client Secret. These credentials, along with the Nooks authorization and token endpoints, are the values you will provide when configuring the MCP connector in Claude or another MCP-compatible client.

Related Resources