# Egnyte MCP connector The Egnyte connector lets Claude, ChatGPT, Cursor, or any MCP client look up a specific Egnyte user account or group, with every lookup running as the person who signed in and recorded in an audit log. Source: https://elaichi.ai/connectors/egnyte/ ## Facts | | | | --- | --- | | Application | Egnyte | | Category | Cloud Storage | | AI tools | 2 | | Authentication | Connects over OAuth | | Needs your own OAuth app | Yes | | MCP endpoint | https://api.elaichi.ai/mcp | | Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent | | Tools advertised by name | Yes | ## What you can ask once Egnyte is connected - Show the Egnyte groups this user belongs to. - Look up the Egnyte user behind this account id. - List members of our Egnyte Finance group. ## Connect Egnyte in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick Egnyte. 2. Optionally set Share with, then press Connect. 3. Supply your own Egnyte app, then approve. Egnyte needs an OAuth app you register yourself, so bring its client ID and secret. One person does this once for the organization. Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Egnyte tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## Connect Egnyte to Claude Endpoint: https://api.elaichi.ai/mcp 1. Open Customize, then Connectors. 2. Press Add. 3. Name it, paste the MCP server URL, then Continue. 4. Sign in and approve. On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves. ## Connect Egnyte to ChatGPT Endpoint: https://api.elaichi.ai/mcp 1. Open Plugins, then press the + button. 2. Name it and paste the endpoint into Server URL. 3. Leave Authentication on OAuth, then tick the risk acknowledgement. 4. Press Create, then sign in and approve. Works on the web today. The plugin directory lives at chatgpt.com/plugins. ## Connect Egnyte to Cursor Endpoint: https://api.elaichi.ai/mcp 1. Open `~/.cursor/mcp.json`. 2. Add the endpoint under `mcpServers`. 3. Reload Cursor, then sign in and approve. Set up per machine, so repeat it on each computer you work from. ## Connect Egnyte to any MCP client Endpoint: https://api.elaichi.ai/mcp 1. Add the endpoint as a remote MCP server. 2. Sign in and approve. The Elaichi Agent already has these tools, with nothing to set up. ## What the consent screen decides Only Read is granted by default, which is not enough to call a Egnyte tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone. ## What teams do with Egnyte through Elaichi ### Confirm who owns an Egnyte account IT. Pull up a single Egnyte user account to check the name, email address, and status behind it before you change anything about the folders that person can reach. ### Check whether a former employee is still active Security. Look up the Egnyte account of someone who has left and confirm it has been disabled, without opening the admin console and hunting through the user list. ### Verify a new hire's Egnyte account HR. After onboarding, check that the new person's Egnyte account exists with the right name and email so they are not locked out on their first day.body_fix ### Answer an auditor's question about a group Compliance. When an auditor asks who sits in a particular Egnyte group, fetch that group's details and give a straight answer with the record to back it up. ### Resolve an access ticket faster Help desk. Someone says they cannot open a shared folder, so you look up their Egnyte account and the group they should belong to, and see at once whether they are in it. ### Check a group before granting folder access Operations. Before pointing a new folder at an Egnyte group, look up that group and confirm it is the one you mean and holds the people you expect. ## Frequently asked questions ### How do I connect Egnyte to Claude? 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. ### Does Egnyte work with ChatGPT and Cursor as well as Claude? Yes. Once Egnyte is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect Egnyte once and every client your team uses picks it up. ### What can an AI agent actually do with my Egnyte data? 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. ### Does connecting Egnyte give the AI access to my whole Egnyte domain? 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. ### Can my team share one Egnyte connection? 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. ### Can I stop an agent from deleting or changing things in Egnyte? 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 blocked action is never shown to Claude, ChatGPT, Cursor, or any other client, so no prompt, however worded, can reach it. If you want to hide even the group lookup from a particular team, you can. ### What happens to an Egnyte connection when someone leaves? 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, and every other client at the same time. ## All 2 Egnyte tools Every tool below is callable through https://api.elaichi.ai/mcp once Egnyte is connected, subject to the toolbox it is in and the restrictions on the caller. - **Get single Egnyte user by ID** (Get). Get details about a specific user in Egnyte. Requires id. Returns fields such as username, email, role, and status for the user. - **Get single Egnyte group by ID** (Get). Get details of a specific group in Egnyte using id. Returns fields such as group_name, members, and permissions associated with the group.