Cloud Storage
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.
-
How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Egnyte to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Egnyte once
-
Open Connections, choose Add connection, and pick Egnyte.
-
Optionally set Share with to give a team access, then press Connect.
-
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.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
Egnyte
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect Egnyte to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
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
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
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
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Egnyte to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Egnyte through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
IT
Confirm who owns an Egnyte account
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.
-
Security
Check whether a former employee is still active
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.
-
HR
Verify a new hire's Egnyte account
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
-
Compliance
Answer an auditor's question about a group
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.
-
Help desk
Resolve an access ticket faster
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.
-
Operations
Check a group before granting folder access
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.
Try asking
- “Show the Egnyte groups this user belongs to.”
- “Look up the Egnyte user behind this account id.”
- “List members of our Egnyte Finance group.”
AI tools
Egnyte tools for your AI agents
2 tools are ready to call through Elaichi's MCP endpoint the moment you connect Egnyte, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Egnyte gets you
6 screens from the product, each doing one job for your Egnyte account.
The agent
Ask about Egnyte users in plain language.
Type a question and get answers read from live Egnyte users and groups.
- users
- groups
- folders
- permissions
Ask Elaichi to work across your apps.
Show the Egnyte groups this user belongs to.
Look up the Egnyte user behind this account id.
List members of our Egnyte Finance group.
Also runs in Claude, ChatGPT or Cursor
MCP clients
One Egnyte endpoint for every MCP client.
Claude, ChatGPT and Cursor connect over OAuth, no SDK, no shared API key.
Copy the endpoint
Tool catalog
2 Egnyte tools ready without custom code.
Browse Egnyte tool names, resources and methods, then hand them straight to a client.
- Get single Egnyte user by ID
- Get single Egnyte group by ID
Toolboxes
Every team gets its own Egnyte toolbox.
Scope one toolbox to IT, another to Legal, each with its own Egnyte tools.
- IT
- Security
- Legal
- Finance
Shared connections
Teammates use Egnyte without touching credentials.
See who connected each Egnyte account and how many teams and members share it.
- IT Admin
- Security Review
- Legal EMEA
- Finance
Audit log
Answer who did what in Egnyte.
Every Egnyte call lands in an append only log with actor, action and resource.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule starts real Egnyte work.
Fetch Egnyte users, group them, draft a digest, approve it, post it back.
Egnyte digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch users
Egnyte
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Egnyte
Queued
Collections and dashboards
Egnyte health arrives before anyone asks.
Four metrics, 14 days of records created and a team breakdown, refreshed on schedule.
Egnyte health
Refreshed 4 minutes ago · every 15 minutes · from the users collection
Users
1,284 ↓ 12%
Groups
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Users created
Last 14 days
By team
Share of activity
IT Admin 34%
Security Review 27%
Legal EMEA 21%
Finance 18%
FAQ
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 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.
Put Egnyte in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.