Nooks is a sales platform that helps reps prospect and run outbound sequences, with AI coaching for calls.
Agen.co connects to Nooks through Nooks' own hosted MCP server as an Official connector. Each user signs in with their own Nooks account and approves access. Nooks does not support dynamic client registration, so a Nooks user first creates an OAuth app in Nooks and gives Agen.co its client ID and secret.
Prerequisites
Prerequisites
- A Nooks account with a Sequencing seat, an AI Coaching seat, or both. Nooks only lets users with one of these seats create OAuth apps.
- Permission in Nooks to open Developer and create OAuth apps. Nooks help center articles differ on whether this requires a workspace admin, so check with your Nooks administrator.
- In the Agen.co portal, go to Connectors → My connectors and click Add connector.
- In the Select connector drawer, search for
Nooksand select it. The Add Nooks panel opens. - Copy both read-only URLs shown in the panel:
- Callback URL — completes the initial OAuth handshake between Agen.co and your Nooks app.
- Gateway callback URL — used by the Agen.co MCP gateway for per-user authorization at runtime.
Leave this panel open — you return to it after creating the app in Nooks.
- Sign in to Nooks and go to Developer → OAuth Apps.
- Create a new OAuth app and give it a name your users will recognize. Nooks shows this name on the consent screen.
- Add both callback URLs from Agen.co as redirect URIs, one entry each. Nooks matches the redirect URI exactly, so paste each URL without changes.
- Grant every scope the app offers, so that all of Nooks' MCP tools work.
- Save the app, then copy the Client ID and Client Secret. Store the secret before you leave the page. If you lose it, rotate the secret from the app's settings in Nooks.
A missing scope can make tools fail
A missing scope can make tools fail
Nooks decides which tools a session can use from the scopes granted to the app. If a tool fails for a missing scope, add the scope to the Nooks app and reconnect.
Return to the open Add Nooks panel and fill in the fields:
| Field | Required | Description |
|---|---|---|
| Instance Slug | Yes | Namespaces this instance — it prefixes each imported tool as slug__tool, so several instances of the same MCP can coexist. Prefilled with nooks. Use lowercase kebab-case. You can change it later from the connector's settings. |
| Client ID | Yes | The OAuth client ID from your Nooks app. |
| Client Secret | Yes | The OAuth client secret from your Nooks app. |
| Callback URL | — | Read-only. Add it as a redirect URI in your Nooks app. |
| Gateway callback URL | — | Read-only. Also add it as a redirect URI — the MCP gateway uses it for per-user authorization at runtime. |
- Click Connect. Nooks opens in a new tab, and the panel shows Waiting for authorization — complete it in the opened tab…
- Sign in to Nooks and approve the requested access.
- Back in Agen.co, the panel switches to Select the tools to import from Nooks. Every tool is toggled on; turn off any you don't want to import, then click Add.
The connector is created and its tools imported only when you click Add. If you close the panel before that, nothing is saved, even if the Nooks tab reported success.
Everything runs as the signed-in user, so agents only reach the Nooks data and actions that user can already access. Nooks' server needs a signed-in session to list its tools, so the tool selection screen after Connect shows exactly what your account serves.
Enabling the Nooks connector isn't enough on its own. Tool calls remain denied until you create a policy that grants access to the specific tools you want to expose.