Egnyte MCP server for AI agents.

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 178 Egnyte actions across audit reports, FS, links and webhooks, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Egnyte.

Your own Egnyte OAuth app, registered with Egnyte (its client id and client secret), and the access and refresh tokens from one admin sign-in. actionlake has no Egnyte app of its own, so this is not a one-step consent. actionlake renews the access token as it expires. Plus your host. The free call account { op: "connections.requirements", service: "egnyte" } lists exactly what to paste.

Only if its key allows it, and only with an explicit confirmation. 21 Egnyte actions are destructive, including delete a user, delete a group and delete Comment. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.

actionlake paces every call to the limits in the Egnyte service file: 2 calls a second, at most 2 at a time per connection. Repeated reads are answered from cache (81 Egnyte actions can be), which never reaches Egnyte.

One upstream call, the only unit actionlake bills. A list that pages bills one call per page (15 Egnyte actions page). Cache hits, searches, dry runs and calls Egnyte refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

The Egnyte Public API (OpenAPI 3.0.3 'Egnyte Public API Reference') at your Egnyte instance's API base URL, which you enter when connecting. It is built from Egnyte's documentation as read on 22 October 2026. 178 actions in 57 areas, each one in the signed service file (version 1.0.0).

actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 5 minutes, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Egnyte credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.

Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.