TL;DR: Request an OAuth client ID and secret from Noded. In Claude, open Settings → Connectors → Add custom connector, name it Noded, paste https://app.getnoded.ai/api/mcp/apps, enter the client ID and secret under Advanced settings, then click Connect and sign in with your Noded account. Reads are read-only. Every write (an email, a message, a note, a CRM record, a workflow run) arrives as a recommendation card that you approve or dismiss.
What you need
- A Noded account with data connected. Claude can only find what Noded has synced. Connect at least one source (Gmail, Slack, a calendar, a call recorder, or a CRM) in the Noded app first.
- A Claude plan that supports custom connectors. Custom connectors are added by the user on individual plans, and by an owner or admin on Team and Enterprise plans. See Anthropic’s custom connector guide for the current plan list.
- An OAuth client ID and client secret from Noded. Claude’s automatic (dynamic) registration does not complete against Noded’s sign-in service, so we issue credentials for your workspace. Email hello@getnoded.ai with the subject OAuth client for Claude and the email address of your Noded workspace. We reply with a client ID and a client secret, and we register Claude’s callback URL for you.
- The server URL.
https://app.getnoded.ai/api/mcp/apps- enter it exactly, including the path.
Using another assistant? See the guides for ChatGPT, Gemini, and Microsoft Copilot Studio.
Connect Noded in Claude (web and desktop)
1️⃣ Open connectors. In Claude, go to Settings → Connectors.
2️⃣ Add a custom connector. Click Add custom connector. Set the name to Noded and the remote MCP server URL to https://app.getnoded.ai/api/mcp/apps. Click Advanced settings and enter the OAuth Client ID and OAuth Client Secret that Noded sent you. On Team and Enterprise plans an owner does this once under Organization settings → Connectors, and members then click Connect on the shared connector.
3️⃣ Sign in to Noded. Click Connect. A Noded sign-in window opens. Use the same email address as your Noded account, then approve the requested access. The consent screen lists read access to your customer context and the ability to create recommendations for you to review.
4️⃣ Enable it in a chat. In a new chat, open the tools menu (the + or Search and tools control) and make sure Noded is switched on.
5️⃣ Test with a read. Ask: “What can Noded do?” Claude calls Noded and lists the built-in actions plus the searches, workflows, and record types installed for your account. Then try “When did we last talk to Acme, and is anyone waiting on a reply from us?”
Connect Noded in Claude Code
One command adds the connector with your client ID, then /mcp completes the sign-in. Claude Code signs in through a local callback, and by default picks a random port; the --callback-port flag pins it so that we can register the URL. Tell us in your credentials request that you also use Claude Code and we register http://localhost:8080/callback for you (or another port if you say so).
| Step | Command |
|---|---|
| Add the server | claude mcp add --transport http noded https://app.getnoded.ai/api/mcp/apps --client-id YOUR_CLIENT_ID --client-secret --callback-port 8080Claude Code prompts for the client secret so it never lands in your shell history. |
| Sign in | Run /mcp inside Claude Code, select noded, and complete the browser sign-in. |
What Claude can do with Noded
Noded exposes one connector with a small set of capability groups. You never need the tool names; describe what you want and Claude picks the right one.
| Group | What it does | Example prompt |
|---|---|---|
| Find people and accounts | Resolves a name or company to the right contact or account, lists related people (buying committee, who else is involved), and reads your saved folders such as My Accounts. | “Who else at Acme has been on our calls?” |
| Read activity | Emails, chat messages, meetings and transcriptions, notes, tasks, and saved CRM or support records - filtered by person, account, date, direction, or status. Semantic search finds themes when exact filters are not enough. | “What was decided on the last two Acme calls?” |
| Check engagement | Per-account activity across every channel in one call, and unanswered emails - who is waiting on you, and who has gone quiet. | “Which of my accounts have gone quiet this month?” |
| Search connected apps | Read-only live lookups in the apps you have connected (Salesforce, HubSpot, Zendesk, Jira, Linear, and others) using the searches installed for your account. Results render as cards in the chat. | “Find open Zendesk tickets for Acme.” |
| Draft and act | Draft an email, a Slack or Teams message, or a note; create a record in a connected system (a Jira issue, a Salesforce case, a HubSpot record); or run one of your installed workflows. Each one arrives as a recommendation to review. | “Draft a follow-up to Jane at Acme about next steps.” |
| Dates | Helpers for the current time, relative dates, and date arithmetic so questions such as “in the last 10 days” resolve correctly. | “How many days until the Acme renewal?” |
The exact list of searches, workflows, and record types is specific to your account. It depends on which apps you have connected in Noded and which queries and functions your team has installed. Ask “What can Noded do?” at any time to see the current list.
How the review step works
Noded separates reading from writing. All the read tools are read-only. Every write goes through a recommendation:
1️⃣ Claude proposes. When you ask for an email, a message, a note, a record, or a workflow run, Claude composes the proposal and asks Noded to create a recommendation. Nothing is sent, saved, created, or run at this point.
2️⃣ You review the card. The recommendation appears as a card in the chat: the recipients, the subject and body, the record fields, or the workflow inputs. You can edit the text in the card before you decide.
3️⃣ Approve or dismiss. Approve accepts the recommendation with your edits, and Noded carries it out through the connected system. Dismiss discards it. Claude reports the result only after Noded confirms it.
The same recommendations are visible in the Noded app, so a teammate with access can also review them there. If Noded cannot create a recommendation, Claude tells you so instead of pretending the action happened.
Permissions and data handling
- The connector runs as you. Claude sees only what your Noded user can see. Tenant boundaries and sharing permissions are the same as in the Noded app.
- Sign-in is OAuth 2.1 with PKCE. Claude never holds your Noded password. The token is scoped to reading your customer context and creating recommendations.
- Disconnect at any time. Remove the connector in Claude’s Settings → Connectors. Access ends for that Claude account immediately.
- Nothing new is stored in Claude by Noded. Query results are returned to the chat you are in and are governed by your Claude plan’s data policy.
Troubleshooting
- Connect fails before the Noded sign-in window opens, or Claude reports a registration error. The client ID and secret are missing or mistyped. Open the connector’s Advanced settings and check both values against the email from Noded.
- “Unauthorized” or the connector shows as disconnected. Sign in with the same email address as your Noded account. If you have more than one Noded workspace, use the one you want Claude to read.
- Claude finds nothing for an account you know is active. Check that the source (email, calendar, Slack, call recorder, CRM) is connected in Noded and has finished its first sync.
- Claude answers from general knowledge instead of Noded. Make sure the Noded connector is switched on in the chat’s tools menu, or say “use Noded” in the prompt.
- The recommendation card does not appear. Ask Claude to show the recommendation again, or open the Noded app - the recommendation is there too.
FAQ
Why do I need a client ID and client secret from Noded?
Claude’s automatic (dynamic) OAuth registration does not complete against Noded’s sign-in service. We issue a client ID and client secret for your workspace instead, and you enter them under the connector’s Advanced settings. The sign-in itself is the same standard OAuth flow.
Can Claude send an email or create a record through Noded without asking me?
No. Every write becomes a recommendation card. Nothing is sent, saved, created, or run until you approve it.
What data can Claude see?
Only the data the signed-in Noded user can already see in Noded, under the same tenant and sharing permissions.
Which URL do I paste?
https://app.getnoded.ai/api/mcp/apps, entered exactly, including the /api/mcp/apps path.
Does the same connector work with ChatGPT, Gemini, and Microsoft Copilot?
Yes. The same server URL is used for ChatGPT, Gemini, and Microsoft Copilot Studio, each with its own client ID and secret from Noded. See our guide to MCP for customer teams for the wider picture.