# Connect Claude to Nodary Add Nodary to Claude as a custom connector, and Claude reads and writes your workspace’s documents with your permissions, on claude.ai and in Claude Desktop. Checked against each vendor’s documentation on 22 October 2026. ## Before you start - A Claude plan that allows custom connectors: Free, Pro, Max, Team or Enterprise. On Free, Claude allows one custom connector. - On Team and Enterprise, an Owner adds the connector for the organisation first; each member then connects with their own account. - A Nodary account. The MCP server is in every plan; on Free, while the workspace stays within the free plan: 1 project, 10 documents and folders, 2 members. Claude spends no Comets: it uses its own model. No workspace yet? Create one, then come back to connect. [Create a free workspace](https://nodary.ai/sign-up) ## Add the connector 1. In Claude, open Customize, then Connectors, and choose Add custom connector. 2. Name it Nodary and enter the server address: ``` https://nodary.ai/api/mcp ``` 3. If Claude asks how people sign in, choose Sign in now. If it asks which OAuth client to use, choose Register automatically: Nodary registers Claude itself and does not read Claude’s published identity. Leave the client ID and secret empty. 4. Select Add, then Connect. Nodary’s sign-in and consent page opens in your browser. ### On a Team or Enterprise plan 1. An Owner opens Organization settings, then Connectors, selects Add, then Custom, and chooses Web if Claude asks for the type. 2. The Owner enters the same address and the same sign-in choices, then selects Add. 3. Each member opens Customize, then Connectors, finds Nodary with the Custom label and selects Connect. ## Sign in and choose workspaces Nodary’s consent page names the app that asks and the address it will be sent back to. Sign in if you are not already, then choose the workspaces Claude may reach: with one workspace you pick it, and with several none is ticked for you, so tick each one Claude may use. If you signed in more than 10 minutes ago, Nodary asks for your password again. Approve, and the browser hands you back to Claude. Claude then acts as you: it sees and changes only what your role allows, in the workspaces you ticked. Its access lasts 60 minutes at a time and Claude renews it on its own. ## Use Nodary in a chat In a conversation, open the + menu, then Connectors, and check that Nodary is on. Claude asks before it uses a tool: choose Always allow only for tools you trust. A few requests to start with: - List my Nodary projects and the documents that changed this week. - Read the onboarding guide in the Team project and turn its open questions into a checklist. - Write a summary of the notes below, file it under Meetings and link it to the roadmap. ## With an API key instead Claude’s request headers, which send a fixed credential instead of a sign-in, are a beta open to some organisations only. Where you have them, choose No sign-in, then add the header authorization with the value Bearer followed by a space and your key. Create the key in Nodary under Profile, API keys and MCP. It starts with gdc_, is shown once, acts with your permissions, can be limited to one project, and expires after 30, 90 or 365 days, or never, as you choose. ![The API keys and MCP section of a Nodary profile: the address of the MCP server to paste into an AI client, and an agent key with its scope.](https://nodary.ai/marketing/mcp-connect.webp) ## If something does not work - The connection fails as soon as you add it: Claude probably used its published identity, which Nodary does not read. Claude cannot change the sign-in settings of a connector, so remove it and add it again with Register automatically. - Claude will not add a second custom connector: its Free plan allows one. - A first request answered 401 is expected: it tells the client where to sign in. - quota_locked: the workspace is above the free plan after its trial and is locked until the owner subscribes. It works again at once after that. - billing_locked: a payment failed, so the workspace is locked until the owner settles it in the workspace’s billing settings. It works again once the payment goes through. - workspace_suspended: Nodary has suspended the workspace, so nothing reaches it, agents included. The owner can write to support@nodary.ai. - workspace_required: the connection reaches several workspaces, so name the one to work in, or connect again and tick only one. - To keep Claude from using one tool, open Customize, then Connectors, select Nodary and set that tool to Blocked. ## Questions ### Does connecting Claude cost anything? Not on Nodary’s side. The MCP server is in every plan, Free included within its limits, and Claude spends no Comets: Comets count Studio AI only. Your Claude plan decides whether you can add the server. ### Can Claude delete or overwrite my documents? Only where your role lets you, and a change can be put back: each editing session of up to ten minutes makes a version, and so does every agent write. A document keeps its 50 newest versions by people and its 50 newest by agents (an agent’s never push out people’s), which you compare and restore, and a deleted document comes back for 30 days. Share links, access, members, roles, keys, billing and deleting a project stay human decisions: no agent can do them. ### Can I use the same connection in Claude Code? Yes, when you sign in to Claude Code with your claude.ai account: the connectors you added on claude.ai appear there too. With an API key or another provider, add Nodary to Claude Code with its own command. ### How do I disconnect it? In Nodary, open Profile, Security, Connected apps and disconnect it: it stops at once. In Claude, remove the connector under Customize, Connectors. A key is revoked under Profile, API keys and MCP, and owners and admins can revoke any key of the workspace in its settings, under MCP. ### Does Nodary use my documents to train AI? No. Nodary does not use workspace content to train AI models. What Claude does with what it reads is set by its maker’s own terms. ## Read next - [Connect Claude Code to Nodary](https://nodary.ai/docs/mcp/claude-code): One command adds Nodary to Claude Code, then /mcp signs you in. - [Connect ChatGPT to Nodary](https://nodary.ai/docs/mcp/chatgpt): Add Nodary to ChatGPT as a custom MCP server from Plugins, on Business, Enterprise and Edu. - [The Nodary MCP server](https://nodary.ai/docs/mcp): The server, signing in, the 98 tools, safety and every client at a glance. - [MCP (Model Context Protocol)](https://nodary.ai/glossary/model-context-protocol): The Model Context Protocol (MCP) is an open standard that connects AI applications to outside tools and data through one common interface. - [OAuth](https://nodary.ai/glossary/oauth): OAuth is a standard that lets an app act for you in another service, with access you approve, without ever seeing your password. https://nodary.ai/docs/mcp/claude