Claude NetDocuments connectorWhat Claude can do in your NetDocuments account.
The Claude NetDocuments connector exposes 2 tools, both on the reading side. 2 read, 0 write, 0 left undocumented. Here is what Claude can find in your firm's repository, what the sheet leaves out, and who decides whether it stays switched on.
Verified Trustpilot reviews · AI, automation & growth agency
What changes once Claude can reach your repository
With the connector, you ask Claude the question in plain words and it looks in the repository for you, then works from what it found inside the same conversation. The directory sheet keeps the promise short: search, retrieve, and stay within your organization's permissions.
Find the precedent first. You ask Claude for the documents in your repository that match a question. It runs search against your NetDocuments content and lists what comes back.
Open the right file, not the whole cabinet. Once a match looks promising, fetch retrieves that document so Claude can read it with you, answer questions about it or compare it with another one.
Draft from what you already have. NetDocuments describes playbooks and new drafts built on your precedents. That drafting happens in the conversation: no listed tool files the result back into the repository.
What the sheet does not give Claude matters as much. By default it exposes no tool that creates, edits, moves or deletes a document, so nothing Claude writes lands in NetDocuments unless you put it there. That is an observed floor, not a promise: an administrator can open more than any public sheet shows. Nothing runs on its own either. A new document in a workspace does not wake Claude up. If you want hands-off flows of that kind, they belong to an automation tool, which does a different job; the Integrations hub is where that side lives.
Five words before you connect
The vocabulary around this connector, in one minute.
- Connector
- A link you set up once between Claude and an account you already have, so Claude can work in that account while it answers you.
- Tool
- One named thing a connector lets Claude do. Claude picks the tools it needs by itself, and the directory sheet lists them by name.
- Authorization
- The sign-in screen of NetDocuments itself, where you grant the access Claude will use. Granted once per person, and it can be withdrawn.
- Approval
- The confirmation Claude waits for before doing something that changes an account, shown in the conversation at the moment it matters.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as NetDocuments.
Connect NetDocuments to Claude in three steps
- 01
Find NetDocuments in Claude
Open Claude's settings, then Customize and Connectors, and look up NetDocuments in the list. On a Team or Enterprise workspace, an Owner or Primary Owner must enable it before each member can sign in.
- 02
Start the connection
Click Connect on its row and sign in to NetDocuments in the window the service opens itself. If the link breaks later, Disconnect and connect again from the same row.
- 03
Read the authorization screen
Review what NetDocuments asks before you accept. That screen belongs to the service, not to Claude, and it sets what the access covers. You can also withdraw the access later from the NetDocuments side.
The 2 tools of the NetDocuments connector
NetDocuments gives Claude 2 tools: 2 that read your account, 0 that change something in it.
Two tools, both reading. Their names stay exactly as Claude shows them.
- 2 read
What Claude reads (2)
2 toolsBoth tools look at your documents and leave them as they are.
search
Looks through your NetDocuments repository for documents that match what you asked, and hands the results to Claude. The source describes searching, nothing about how results are ranked.
fetch
Retrieves a document from the repository so Claude can actually read its content, answer questions on it or draft something new from it as a precedent.
What Claude checks with you first
By default, Claude stops and asks before any action it takes on an account for someone. The prompt shows up in the conversation when it matters.
Here, both listed tools read, so that default rarely comes up. On Team and Enterprise, owners decide whether members may let some actions through without being asked each time, and they can restrict a connector for the whole organization, for example keeping reading and closing writing. Nobody overrides that from a personal account. Claude also works with the rights of the person who connected and nothing more.
Which plans include it
Not one of the 819 sheets in the official directory states plan availability. For NetDocuments, as for every other connector, that answer is published nowhere.
The published rule is general: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner opens a connector for the organization before members can each connect. For the live state of this one, check the NetDocuments sheet in the official directory, the only place that shows it.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you, so nothing starts when a document is filed or a matter is opened.
This connector is documented only by its publisher: no Claude help article covers it, and the documentation link on the sheet leads to the NetDocuments support home rather than to a page about Claude. The verification badge in the directory is not a security audit, and Anthropic states on every sheet that it neither chooses the tools a publisher exposes nor guarantees they behave as announced. Connect it only because you trust NetDocuments itself. The other connectors we have documented sit in the Claude connectors hub.
Need help connecting NetDocuments to Claude?
A person reads every message.