Resources · Claude connector

Claude Egnyte connectorWhat Claude can do in your Egnyte account.

The Claude Egnyte connector exposes 23 tools. 16 read your Egnyte content (search, documents, knowledge bases, comments, links), 0 change anything by default, 7 are undocumented. Here: what Claude finds, what an admin must enable, and where the sources disagree.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What changes when Claude can reach your Egnyte files

Your contracts, reports and policies already live in Egnyte. With the connector, Claude can search them, read them and put questions to Egnyte AI while it answers you, instead of you digging through folders and pasting extracts. Anthropic's own tutorial for this connector frames it for data rooms: search, read, ask, then summarize with citations to the actual files.

Contract review in one conversation. advanced_search finds every PDF contract in a client folder for a given period, ask_document asks each one about its termination clause, and summarize_document gives you the key terms side by side.

Due diligence without the folder hunt. Claude runs search over the deal room, pulls the documents that matter with fetch, and builds a summary of financial highlights and risks drawn from the files themselves.

Policy questions answered from the source. An employee asks about the leave policy: ask_knowledge_base queries the HR knowledge base, or ask_copilot asks Egnyte's assistant within the handbook folder.

Now the part the sheet leaves out. Nothing on it uploads, moves or edits a file, even though Egnyte documents such tools elsewhere. Seven tools, three of them with workflow in their name, are described by no official source. An Egnyte admin must switch on external AI access first. Claude sees only what your Egnyte rights show you. And nothing runs on its own: no tool fires when a file lands. For that, you want an automation tool, a different job; the Egnyte Make integration covers that side, and the Integrations hub lists the rest.

Vocabulary

The vocabulary in one minute

Five words you will run into while plugging Egnyte in.

Connector
The link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
Tool
One named thing a connector lets Claude do. Claude picks the ones it needs on its own, and the directory lists them by name.
Authorization
The sign-in screen of Egnyte itself, where you hand Claude the access it will use. Granted once per person, and you can take it back.
Approval
The confirmation Claude waits for before it goes ahead with something that changes your account, shown right in the chat.
MCP
The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as Egnyte.
Connect

Plug Egnyte into Claude in three steps

  1. 01

    Find Egnyte in Claude

    In Claude's settings, open Customize, then Connectors, and look for Egnyte in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to switch the connector on before each member can connect.

  2. 02

    Start the connection

    Click Connect on the Egnyte row, then sign in to Egnyte in the window the service opens itself. If the link ever breaks, use Disconnect and plug it back in.

  3. 03

    Read the authorization screen

    Read the authorization screen before you approve it. It belongs to Egnyte, not to Claude, and it decides what the access covers. You can also withdraw that access later from your Egnyte account.

Tools

The 23 tools of the Claude Egnyte connector

Egnyte gives Claude 23 tools: 16 that read your account, 0 that change something in it, and 7 no official source describes.

Two groups: what Claude reads in your Egnyte domain, and what no official source describes. The names stay the ones Claude shows, in English.

  • 16 read
  • 7 not documented

What Claude reads (16)

16 tools

Sixteen tools that search, read, question or list your content without changing it.

fetch

Pulls the content of one document by its ID into the conversation, so Claude can read it, compare it with another file or quote a passage.

When it helps
an auditor wants the text of a policy memo placed next to the procedure it is supposed to match.
Watch out
very long documents may be cut to fit response limits.

Sourcelearn.microsoft.com · July 22, 2026 ↗

ask_document

Puts a question about one document to Egnyte AI and brings back the answer, which saves reading a whole contract to find one clause.

When it helps
a buyer asks what the termination conditions are in a framework agreement.
Watch out
Egnyte says document Q&A is not supported on its Platform offers.

Sourcelearn.microsoft.com · July 22, 2026 ↗

summarize_document

Asks Egnyte AI for a summary of a document, so Claude can hand you the main provisions of a long file in a few lines.

When it helps
a partner reviews a batch of due diligence reports the night before a meeting.
Watch out
summaries are not available on Egnyte's Platform offers, according to Egnyte.

Sourcelearn.microsoft.com · July 22, 2026 ↗

list_filesystem_by_path

Lists the files and folders sitting at a path you give, so Claude can see what a folder holds before it opens anything.

When it helps
an office manager checks what is filed under the HR onboarding folder.
Watch out
Claude sees only the folders your account can open.

Sourcelearn.microsoft.com · July 22, 2026 ↗

download_file_by_path

Downloads a file located by its path in Egnyte, giving Claude the file itself rather than a summary of it.

When it helps
an accountant wants the exact spreadsheet stored in the month-end folder.
Watch out
the path must match what your permissions let you reach.

Sourcelearn.microsoft.com · July 22, 2026 ↗

download_file_by_id

Retrieves the original file that matches an Egnyte ID, handy when a search already returned the ID and the path is long or unknown.

When it helps
Claude found the right deck through search and you want the original file.
Watch out
it hands over the whole file, so the permission rules of your Egnyte account still decide what can be reached.

Sourcelearn.microsoft.com · July 22, 2026 ↗

ask_copilot

Asks the Egnyte AI Assistant a question, optionally scoped to specific files or folders, and brings its answer back into Claude.

When it helps
an HR lead asks what the handbook folder says about remote work allowances.
Watch out
the answer comes from Egnyte's assistant, not from Claude reading every file.

Sourcelearn.microsoft.com · July 22, 2026 ↗

ask_knowledge_base

Queries one of the knowledge bases your organization built in Egnyte, a curated collection of reference content.

When it helps
a support agent asks the product knowledge base how a warranty claim works.
Watch out
knowledge base queries are not supported on Egnyte's Platform offers.

Sourcelearn.microsoft.com · July 22, 2026 ↗

list_knowledge_bases

Lists the knowledge bases available in your Egnyte domain, with filtering, so Claude knows which collection to query.

When it helps
a new hire wants to know which curated collections exist before asking anything.
Watch out
if your organization never built one, the list will be empty.

Sourcelearn.microsoft.com · July 22, 2026 ↗

list_projects

Lists the project folders of your domain, so Claude can point you to the right project before searching inside it.

When it helps
an architect's assistant wants the project folders opened this quarter.
Watch out
project folder tools are not supported on Egnyte's Platform offers.

Sourcelearn.microsoft.com · July 22, 2026 ↗

get_comment

Retrieves one comment by its ID, so Claude can bring the exact remark left on a file into the discussion.

When it helps
a reviewer wants to reread the objection a colleague left on a draft.
Watch out
it reads comments; adding one is not among the tools on the Claude sheet.

Sourcelearn.microsoft.com · July 22, 2026 ↗

list_comments

Lists the comments left on a file or across the domain, which gives Claude the review history of a document.

When it helps
a manager wants every open remark on a tender response before the deadline.
Watch out
only comments on files you can see come back.

Sourcelearn.microsoft.com · July 22, 2026 ↗

Undocumented (7)

7 tools

The directory publishes these seven names and nothing else. No official text says what they do, and this page will not guess from a name.

list_filesystem_by_id

This name is on the directory sheet, next to its by-path sibling, but no official source describes it: Egnyte's own tool list skips it, and so does the Claude tutorial.

Watch out
the general approval rule below covers it like any other tool.

get_folder_stats

Same silence here. The sheet shows the name, and none of the Egnyte or Claude pages read for this guide documents it, so the page will not guess from the wording.

Watch out
Egnyte admins can review MCP session activity in their reports.

search_projects_by_folder

Listed on the sheet, absent from every official text available today. Its effect on your domain is therefore unknown, whatever the name suggests, and the page leaves it there.

Watch out
Egnyte says project folder tools are not supported on its Platform offers.

get_project_details

One more entry the directory names without a word of explanation. Egnyte describes a tool that lists project folders, but not this one: no official source documents it, so the page stops at the name.

Watch out
the default approval rule applies to it.

get_workflow_details

The first of three names on the sheet that mention workflows. No official source says what any of them covers or returns, and this page does not fill the gap.

Watch out
treat it under the default approval rule, as for any tool without a description.

list_workflows

Second workflow name on the list, just as silent as the first: no official source documents it. Neither Egnyte's tool table nor the Claude tutorial mentions it anywhere, so nothing more is said here.

Watch out
an admin can still restrict the connector for the whole organization.

list_workflow_tasks

The last name on the sheet, and the last undocumented one: no official text describes it, so its effect on your content is unknown here.

Watch out
if an Egnyte answer mentions tasks, check with your admin what the connector exposes.
Approvals

What Claude asks before it acts

By default, Claude stops and asks for your go-ahead before each action it carries out on an account for you. The request shows up in the conversation, at the moment it matters.

On a Team or Enterprise workspace, the owners decide whether a member can let some actions through without being asked every time. They can also limit what a connector may do for the whole organization, for instance keep reading open and close writing. That setting applies to everyone, and nobody gets around it from their own account. Claude also works with your Egnyte rights and nothing more: a folder you cannot open in Egnyte stays closed to it, as both Anthropic's tutorial and Egnyte confirm.

Plans

Which plans include it

Out of the 819 sheets in the official directory, not one shows availability by plan. The connector by connector answer is published nowhere: that is a real gap in the catalogue.

The general rule is public: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, while desktop extensions install on Claude Desktop. On Team and Enterprise, an Owner or Primary Owner turns the connector on for the organization before each member can connect. For the current status, check the Egnyte sheet in the official directory from your own account.

Limits

Where this connector stops

A connector is not an automation. Claude calls these tools while it answers you: nothing starts when a file is uploaded, a folder changes or a workflow step is due.

The tool list is an observed floor, not a promise, since an admin can open actions that no public sheet shows. The directory's partner badge is not a security audit either, and Anthropic says so on every sheet: it does not choose the tools a publisher exposes and does not guarantee they behave as announced. Plug in what comes from a publisher you trust, here Egnyte itself. Anthropic's tutorial explains what the connector is for; the practical limits below come from Egnyte's own pages.

Two official sources disagree

Can Claude write to Egnyte with this connector?

What this page followsNeither side is stale: both describe Egnyte's server, but for different clients. For Claude, the directory sheet of your own account is the one that counts, and today it shows reading only. That is a floor, not a ceiling, so check the sheet again before you plan on writing.

Need help

Need help connecting Egnyte to Claude?

A person reads every message.

FAQ

Questions about the Claude Egnyte connector

01What can Claude do with the Egnyte connector?
Claude can search, read and question the content of your Egnyte domain while it answers you. Sixteen documented tools cover basic and advanced search, fetching and downloading files, asking Egnyte AI about a document or summarizing it, querying knowledge bases and the Egnyte assistant, and listing folders, projects, comments and share links. Seven more tools, three of them with workflow in their name, are listed on the sheet without any official description, so what they do stays unknown.
02Can Claude upload, edit or delete files in Egnyte?
Not with the tools on the Claude directory sheet today. The 23 tools there search, read or list content, and seven are undocumented. Egnyte's own connector page on Microsoft Learn lists tools to upload files, create folders, set metadata, create share links and add comments, but those are not on the Claude sheet. Treat the current list as a floor rather than a promise, and check the sheet from your account before you count on writing.
03Does Claude ask before using an Egnyte tool?
By default, Claude asks for confirmation before each action it takes on an account for you. No source describes a confirmation specific to any Egnyte tool, so that default rule covers all 23. On Egnyte's side, admins also decide whether external AI clients can connect at all. On Team and Enterprise, Claude owners decide whether members can let some actions through without a prompt, and they can restrict the connector for everyone.
04Which Claude plans include the Egnyte connector?
No official source publishes availability plan by plan for a given connector, and none of the directory sheets shows it. The general rule is that remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, with an Owner or Primary Owner switching the connector on first on Team and Enterprise. Egnyte adds its own condition on its side: the AI add-on on your Egnyte offer. The directory sheet is where to check your Claude account.
05Does Claude see every file in our Egnyte domain?
No, only the files and folders your own account can open. Anthropic's Egnyte tutorial says every access through the connector respects your organization's Egnyte permissions, so Claude only reaches the files and folders your user account may view. A colleague with broader rights will get more back from the same question. Egnyte admins can review session activity in MCP Server Reports. On Team and Enterprise, a Claude owner can also restrict what the connector may do for the whole organization.
06Why does Claude get an access error with Egnyte?
Usually because Egnyte has not opened the door yet. Egnyte says a domain without the feature returns an error saying MCP Server connectivity is not enabled. An admin must turn on the setting that lets external AI clients connect and keep Claude in the allowed apps. If that is done and access is still refused, Egnyte's AI Safeguards may be blocking the client, and the admin has to update that configuration.
07Claude or an automation tool for Egnyte: which one fits?
They do different jobs, so choose by use rather than by ranking. The connector fits when you want to question, compare or summarize files during a conversation, with you reading the answer. An automation tool fits when something should happen each time a file is added or changed, such as copying it to another system or alerting a team. Nothing in the connector starts on its own, so event-driven jobs belong to automation.