Egnyte MCP server icon

Egnyte

by Egnyte

HIPAA CompliantSOC2 ReadyISO 27001 Ready
Finance23 tools

Search, read and write enterprise content in an Egnyte domain from an AI agent. Anthropic lists 23 read-only tools; Egnyte documents 21 including five writes the directory omits — one of which creates a public share link. OAuth 2.0, no application scopes.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Connect Egnyte via MCP

https://mcp-server.egnyte.com/mcp

Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.

Egnyte Tools & Capabilities (23)

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • Anthropic's directory listing omits every write tool. Its 23 names are all read-shaped and its permissions field says Read, while Egnyte documents five writes including create_link. The directory entry dates from 12 November 2025 and the writes shipped 29 January 2026. Do not use the directory listing to reason about what this connector can change.
  • Ten directory names appear in no Egnyte documentation. ask_copilot, download_file_by_path, download_file_by_id, list_filesystem_by_id, get_folder_stats, search_projects_by_folder, get_project_details, get_workflow_details, list_workflows and list_workflow_tasks are absent from Egnyte's tool tables and from the page HTML. We could not establish whether they are live, renamed or retired.
  • No OAuth scopes exist to constrain anything. Neither the RFC 9728 resource descriptor nor the authorization server metadata declares scopes_supported. Consent cannot separate reading a document from creating a public share link, and there is no scope list to cross-check the tool names against.
  • We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request, so no readOnlyHint or destructiveHint is published here. The read/write labels are Egnyte's documentation, not the server's declaration.
  • The tool set varies by plan, so no single number is right. Egnyte states Platform plans without the AI add-on get three tools — list_filesystem_by_path, advanced_search and get_file_content. On those plans Egnyte says document Q&A and summarisation, knowledge base queries, and link sharing and project folder tools are unsupported.
  • Uploads are text-only. Egnyte restricts MCP uploads to text formats such as .txt, .csv, .json, .md and .html, states binary uploads including .docx, .xlsx, .pptx and .pdf are not supported, and caps a file at 8 MB.
  • fetch truncates at 10,000 characters. An agent summarising a long contract through fetch may be reading a fraction of it. get_file_content paginates instead.
  • AI tool rate limits are tight. 100 calls per day and 10 per minute per token, against 1,000 per day for standard calls. Six of the tools are AI-powered, so a research session can exhaust the daily AI quota well before the standard one. No per-call charge is documented; the constraint is the quota and the add-on, not metered spend.
  • The directory's nominated documentation URL does not serve the documentation. developers.egnyte.com/docs/Remote_MCP_Server returns HTTP 200 with a 2,138-byte JavaScript shell that is byte-identical to the response for a nonsense path we invented as a control. The real page is at /integration/cfs/api-docs/remote-mcp-server, found via sitemap.xml.
  • Egnyte's help centre publishes a prompt addressed to AI clients. Its overview article asks users to paste a diagnostic-collection prompt into their AI client when a tool misbehaves. It is benign vendor troubleshooting, but it is instruction-shaped text living inside content an agent may retrieve. We report it rather than acting on it.

Frequently asked questions

It cannot delete one, and it can overwrite one. No tool in either enumeration carries a delete, remove, trash, move or rename verb, even though Egnyte's REST API has a documented DELETE endpoint for files and folders. But upload_file adds a new version when a file already exists at the path, and set_file_metadata replaces every value in a namespace rather than merging.

Yes, and this is the highest-consequence tool on the server. Egnyte documents create_link with an accessibility parameter whose values include anyone, meaning a URL that needs no Egnyte account. Its send_email and recipients parameters make Egnyte email that link to outside addresses. A distributed link is not recallable, so treat this tool as a send.

No tool in either enumeration changes permissions. Egnyte's REST API exposes a permissions endpoint that accepts POST to grant folder access, and no MCP tool maps to it. Sharing is reachable only through create_link, which grants access to one file or folder by URL without altering any user's or group's standing permissions.

Neither published number is complete. Anthropic's directory lists 23 names and Egnyte's documentation tables list 21, but only 13 names appear in both. Egnyte's release notes date five write tools to 29 January 2026, after the directory entry was added on 12 November 2025, so the directory snapshot predates them. Your own count also depends on plan.

It reaches domain-wide scope bounded by the signed-in user's own permissions. list_comments returns all comments in the domain, list_projects lists all project folders, and list_links accepts a username filter for links another person created. Egnyte states all access is limited to files and folders the authenticated user has permission to access, so the ceiling is that user's rights.

None are published. The RFC 9728 resource descriptor at mcp-server.egnyte.com omits scopes_supported entirely, and the authorization server metadata at mcp-oauth.egnyte.com omits it too. There is therefore no second enumeration of the verb surface, and no consent-screen boundary separating reading a document from creating a public share link.

Gen 4 Essential, Elite and Ultimate, or Gen 3 Platform plans with the AI add-on. Egnyte states that Platform plans without the AI add-on get only three tools: list_filesystem_by_path, advanced_search and get_file_content. On those plans Egnyte says AI question-answering, knowledge base queries, and link sharing and project folder tools are not supported.

Yes, through a domain setting. Egnyte documents a toggle under Settings, AI Powered Features, MCP Server that allows or blocks external LLM clients, plus a per-app allowlist. ChatGPT, Claude, Microsoft Copilot, Gemini Enterprise and local CLI tools are enabled by default. An unregistered web client option exists, disabled by default, which Egnyte calls highly permissive.

Yes, enforced per access token rather than per API key. Egnyte documents 1,000 standard calls per day and 2 per second per token. The AI-powered tools are much tighter at 100 calls per day and 10 per minute. Responses carry X-Accesstoken-Qps-Allotted and X-Accesstoken-Quota-Current headers so a client can throttle before hitting the ceiling.

Sources

Use in Agentman

Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio

Resources

Server Info

Category
Finance
Developer
Egnyte
Tools
23
Domain
mcp-server.egnyte.com

Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.

Similar MCP Servers for Finance

Stripe logo

Stripe

by Stripe

Coming Soon
Finance23 tools
View detailsConnect
PayPal logo

PayPal

by PayPal

Finance28 tools
View detailsConnect
Square logo

Square

by Square, Inc.

Coming Soon
Finance3 tools
View detailsConnect

Related Resources

Browse All MCP ServersClaude & ChatGPT Setup GuideBrowse AI Skills