Egnyte MCP connector

First, connect Egnyte in Elaichi. Egnyte requires an OAuth application registered inside your own Egnyte domain, so an admin brings that application's client ID and secret once, then signs in to Egnyte in the usual browser window and approves access. Second, in Claude go to Customize, then Connectors, then Add, and paste the Elaichi endpoint https://api.elaichi.ai/mcp. Claude then sees Egnyte alongside anything else your organization has connected.

Yes. Once Egnyte is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client, and the Elaichi Agent. You connect Egnyte once and every client your team uses picks it up.

With this connector, an AI agent can look up a specific Egnyte user account or a specific Egnyte group and report back what it finds, such as the account's name, email, and status, or the group's name and details. It cannot browse or open files and folders, and it cannot create, edit, or delete anything in Egnyte. It is a lookup connector for people and groups, useful for access questions and account checks.

No. Every request to Egnyte runs as the person who signed in, so the AI can only look up the Egnyte users and groups that person is already allowed to see. Elaichi can narrow that further with restrictions, but it can never widen it beyond what Egnyte itself grants that person.

Yes. One admin connects Egnyte in Elaichi and shares the connection with a team, and nobody else ever handles the client ID, secret, or any credential. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every Egnyte lookup.

This Egnyte connector only looks things up, so an agent cannot delete, move, or change anything in Egnyte through it. Beyond that, Elaichi restrictions work per action, and a restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor, Microsoft Copilot, or any other client cannot run it, whatever the prompt says. If you want to restrict even the group lookup for a particular role, you can.

When you offboard someone in Elaichi, their access to Egnyte through Elaichi ends at once, in every client they had set up. A shared Egnyte connection keeps working for everyone else on the team. If you ever want to remove Egnyte entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot, and every other client at the same time.

Yes. Egnyte is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Yes. Both let Claude, ChatGPT or Cursor use Egnyte. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Egnyte call.

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Egnyte: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.