Egnyte
Let your AI work with your Egnyte files: browse folders, read file details, versions and small text files, search names and contents, list and create share links after you confirm, read folder permissions and recent file activity. Internal API key from your Egnyte admin.
7 天免费 · 无需信用卡 · EU 托管
问 Egnyte 任何事
通过 AnythingMCP 对 Egnyte 试一个真实提示 — Claude 调用工具并返回答案。在你的消息上按 Enter 即可在 Cloud 安装。
在 Cloud 上安装 EgnyteClaude 是 AI,可能会出错。请核对回答。
2 分钟设置
- 1在 cloud.anythingmcp.com 开始免费试用。
- 2在连接器商店点击 Egnyte。提示时粘贴凭据。
- 3生成 MCP API 密钥,将 AI 客户端指向生成的 MCP URL。
配置 Egnyte
直接来自连接器定义:在哪里获取凭据、需要哪些权限,以及该适配器调用的是哪个 API。 由连接器作者以英文提供。
Egnyte
This connector works with files in Egnyte, the business file sharing and content governance platform, through the official Egnyte Public API (https://<domain>.egnyte.com/pubapi). It lists folders, reads file and folder details and version history, searches names and contents, reads small text files, lists and creates share links, reads folder permissions, and reads the domain's recent activity (file events).
Who can use it: Egnyte gives API access to customers on eligible plans (not on trials, Team or legacy Office plans), and an admin creates the API key. Every key starts as Pending Approval; Egnyte reviews it, which can take a few days.
Setup
- As an Egnyte admin, open Settings, Apps & Integrations, find the Create API Key tile (or register at https://developers.egnyte.com), and create a key of type Internal Application for your own company. Leave the redirect URI empty; internal keys sign in with a username and password.
- Copy the Key into
EGNYTE_CLIENT_IDand the Secret intoEGNYTE_CLIENT_SECRET. - Enter your Egnyte domain, the first part of your address: for
https://acme.egnyte.comthat isacme, intoEGNYTE_DOMAIN. - Enter the username and password of the Egnyte user the connector acts as into
EGNYTE_USERNAMEandEGNYTE_PASSWORD. A dedicated user with only the folders it needs is the safest choice. If your company signs in to Egnyte only through single sign-on, use a user that has an Egnyte password. - Wait until the key is Active, install and run
egnyte_get_user_info. AnythingMCP gets a token with these credentials and asks for a new one when it expires (after 30 days).
Permissions: the connector sees exactly what that user sees in Egnyte. It asks for the scopes Egnyte.filesystem, Egnyte.link, Egnyte.permission and Egnyte.user.
Writes: confirm first. egnyte_create_link makes a file or folder reachable by a link and, with send_email, e-mails it to recipients. Show the user the file, who can open the link (anyone, password, domain or recipients) and the expiry, and wait for a clear yes before calling. egnyte_delete_item is installed switched off; deleted items go to Egnyte's trash.
How to work
egnyte_get_user_infoshows who the connector acts as.- Browse from
/Shared(company folders) or/Private/<username>withegnyte_list_folder;egnyte_get_itemfor one file's or folder's details,egnyte_list_file_versionsfor earlier versions. egnyte_searchfinds files and folders by name, content or comments (3 to 100 characters, 20 results a page).egnyte_read_text_filereturns the beginning of a text file (txt, csv, md, json, xml, html, source code), at most 100000 bytes. It does not convert PDFs or Office documents; send the user a share link instead.- Sharing:
egnyte_list_links,egnyte_get_link,egnyte_create_link. - Access:
egnyte_get_folder_permissionslists who has which permission on a folder;egnyte_get_effective_permissionchecks one user. - Activity:
egnyte_get_events_cursor, thenegnyte_list_eventswithid=latest_event_idandreverse1 for the latest changes (create, delete, move, copy, permission changes). Egnyte keeps events for up to 30 days.
Paths: full paths starting with /Shared or /Private, case-sensitive, with / between folders. Put a name containing #, ? or % as %23, %3F or %25; spaces and other characters can stay as they are.
Rate limits: depending on the plan, 2 requests per second and 1,000 to 4,000 a day per key. Egnyte answers over the limit with 403 or 429 (Developer Over Rate); wait and try again later, and avoid listing the same large folder repeatedly.
Common errors
- Token request refused (401 at sign-in): wrong username or password, the key is still pending, or a wrong key or secret.
- 401 Invalid Access Token: sign in again; the token was revoked, e.g. after a password change.
- 403: the user has no permission there, or the daily or per-second limit is used up.
- 404: the path does not exist (check the case of every name).
Out of scope: uploading or changing files, creating or moving folders, deleting (switched off), locking, comments, metadata editing, users and groups management, project folders, workflows, and Egnyte AI. Egnyte also runs its own remote MCP server for Egnyte AI features.