Reference
The Noded MCP server
Noded keeps a living graph of your customers - the people and companies you work with, every email, meeting, note, and record, and what Noded has learned along the way. The Noded MCP server gives AI assistants like Claude safe access to that graph: rich search over your customer context, drafts that always come back to you for approval, and guided workspace setup. This page documents the whole server - how it authenticates, what it can and cannot do, and every tool it exposes.
Who this page is for. One server, three readers:
Asking Noded questions from your assistant? Start with the connection guide for Claude, ChatGPT, Gemini or Copilot Studio; the tools you'll use are under Search & read, Connected tools and Drafts & approvals.
Configuring Noded - insights, tables, folders, agents? The Workspace Setup skill drives it conversationally; the tools it calls are under Workspace setup.
Building software on Noded? This server is a thin layer over the Graph API; the SDK is the quickest route into it. The developers hub lays out all four doors.
Connecting
The server speaks the Model Context Protocol over streamable HTTP at:
https://app.getnoded.ai/api/mcp/apps
In Claude, add it as a connector and sign in with your Noded account - the step-by-step guide covers claude.ai, the desktop apps, and Claude Code. ChatGPT and other MCP hosts are covered in Supported hosts. Each request is self-contained and stateless; there is nothing to install or run on your side.
Authentication
The server uses standard OAuth 2.1. When you add the connector, your AI assistant opens the Noded sign-in page; you log in with your normal Noded account, and the assistant receives a token scoped to you. Claude and ChatGPT register themselves automatically from the server URL - there is no client ID or secret to paste. Hosts that need manual OAuth configuration (such as Copilot Studio) receive credentials from the Noded team.
- Scopes requested:
openid,profile,email- identity only. - Tokens are issued and verified by Noded's own authorization server and expire on a normal OAuth schedule; the host refreshes them silently.
- Disconnecting the connector in your assistant, or revoking access in Noded, ends the assistant's access immediately.
Permissions and data handling
The assistant signs in as you, and every tool call runs with exactly your permissions. It can see what you can see in Noded - including content shared with you - and nothing more. There is no service-account mode and no way to widen access from the assistant's side.
- Reads are permission-filtered at the data layer on every call, using the same sharing model as the Noded app.
- Consequential actions go through review. Emails, messages, notes, and external records are created as drafts in your Noded feed for you to approve, edit, or dismiss - the assistant cannot send or save them itself (see the review model).
- Workspace setup tools change configuration (insights, folders, agents) directly, additively, and only after confirming with you in the conversation; they never touch your customer data or send anything.
- Result sizes are bounded (typically 100 items) and history queries are capped at one year per call.
- Noded does not use your data to train models, and the MCP server adds no data collection beyond what the Noded product already stores. See the privacy policy.
The review model
The server draws a hard line between reading and acting. Anything that would leave Noded or change your customer record - an email, a Slack message, a note, a CRM record, a workflow run - is created as a recommendation: a reviewable draft in your Noded feed, also shown inline in supported assistants. You approve it (optionally with edits), or dismiss it. Nothing is sent, saved, or executed until you do. Configuration changes made by the workspace setup tools follow a different but equally explicit rule: the assistant describes the change and gets your agreement in the conversation before calling the tool, and changes that would affect existing dependencies require a second, explicit confirmation.
Search & read read-only
Finding people, companies, and everything that has happened with them.
| Tool | What it does |
|---|---|
| queryTags | Find people, companies, and channels by name, email, type, or ID. |
| searchRelatedTags | Find who and what is related to an account, with co-occurrence strength. |
| queryFolders | Read the user's folder structure and which accounts belong to each group. |
| queryBlocks | General search across the graph's content - notes, tasks, records, and more. |
| queryEmails | Email history, filterable by account, thread, direction, and intent. |
| queryEvents | Calendar events, past and upcoming. |
| queryTasks | Tasks by account, status, and due date. |
| queryTranscriptions | Meeting and call transcriptions. |
| queryRecords | Structured records synced from connected systems. |
| searchSemanticBlocks | Meaning-based search across the graph ("renewal risk conversations"). |
| checkTagActivity | Batched activity rollup per account - who has been active, where, and when. |
| checkUnansweredEmails | Batched check for emails sitting unanswered past a threshold. |
Utilities read-only
| Tool | What it does |
|---|---|
| getCurrentTimestamp | The current time. |
| parseDate | Turn "last Tuesday" or an ISO string into a precise date. |
| adjustDate | Add or subtract time from a date. |
| dateDifference | The gap between two dates. |
| listNodedCapabilities | A plain-language overview of everything this workspace's connector can do. |
Connected tools read-only
Working with the searches and functions the user has installed from their integrations.
| Tool | What it does |
|---|---|
| queryProviders | List the integrations Noded supports. |
| listFunctions | List the workspace's installed functions and their inputs. |
| listQueries | List the workspace's installed live searches and their criteria. |
| executeQuery | Run an installed search live against its source system (read-only). |
| pinQueryResult | Save one result from a live search into the Noded graph. |
Drafts & approvals human-in-the-loop
Every tool here produces a reviewable recommendation, never a direct action.
| Tool | What it does |
|---|---|
| draftEmail | Draft an email for the user's review - never sends. |
| draftMessage | Draft a Slack or Teams message for review. |
| draftNote | Discover the workspace's note templates, or draft a note for review. |
| recommendFunction | Propose running an installed function, with its inputs filled in, for review. |
| listRecordRecommendationTargets | List where external records (tickets, cases, opportunities) can be created, with their fields. |
| createRecordRecommendation | Draft an external record (a Jira issue, a Salesforce case) for review. |
| getRecommendationReview | Fetch a draft's full review detail. |
| approveRecommendation | Execute a draft the user has approved, with any edits they made. |
| dismissRecommendation | Dismiss a draft the user rejected. |
In-chat display
| Tool | What it does |
|---|---|
| renderQueryResults | Show records in an interactive widget inside supported assistants. |
| search / fetch | The standard knowledge-search pair some hosts (like ChatGPT company knowledge) use to search and retrieve Noded content. |
Workspace setup configuration
These tools let the assistant customize a Noded workspace conversationally - the surface behind the Workspace Setup skill. They change configuration only (never customer data), work additively, and confirm with the user before every change. Integrations themselves are always connected in Noded, never from here.
| Tool | What it does |
|---|---|
| getWorkspaceSetup | Read the workspace's full current configuration - the starting point for any setup work. |
| listProviderCatalog | See what connected integrations can bring in, and what is already installed. |
| installProviderTable | Bring a table from a connected integration into Noded, choosing the visible fields. |
| updateTableFields | Hide, rename, or re-prompt fields on an installed table. |
| defineInsights | Define the AI-watched insights on company or person pages. |
| testInsight | Try an insight on one real account before installing it - nothing saved. |
| createTag | Add a company or person to the graph. |
| linkTagToExternalRecord | Link a company or person to its record in a connected system. |
| createWorkspaceFolder | Create a sidebar folder that groups accounts or people. |
| addToSidebar | Pin a company or person to the sidebar or into a folder. |
| upsertRecordType | Set what Noded may do with a table - create, read, update - and which fields. |
| createNoteTemplate | Create a reusable note template for the workspace. |
| upsertAgent | Create or update a Noded agent: its goal, schedule, and what it watches. |
| runAgentNow | Run an agent immediately to test it. |
The Workspace Setup skill
For end users, the setup tools are best driven by the Workspace Setup skill - a downloadable Claude skill that interviews the user about their business, proposes a complete configuration, and builds it with the tools above, one approval at a time. Assistants without the skill can still use the tools; the server's instructions carry the same confirm-first rules.
Supported hosts
| Host | How to connect |
|---|---|
| Claude | Add the server URL as a connector; Claude registers itself and opens Noded sign-in. Guide. |
| ChatGPT | Add as a custom connector from the server URL; also supports company-knowledge search. Guide. |
| Copilot Studio | Manual OAuth with credentials from Noded. Guide. |
| Gemini | Enterprise and CLI setups. Guide. |
Support
Questions, a host that won't connect, or a tool behaving unexpectedly: contact us and include the host you're using and roughly when the problem happened. For building on Noded's APIs directly, see the developers hub, the SDK quickstart and the Graph API reference.