Integrations · Content

Connect Egnyte to Well

Name: Egnyte entities in Well
Creator: Well

Index Egnyte file, folder, and permission so your agents can search across them alongside the rest of your workspace.

What Well pulls from Egnyte

Egnyte feeds file, folder, permission into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Egnyte’s access.

From Egnyte	In Well	Relation
File	Indexed record	Becomes
Folder	Workspace context	Groups under
Permission	Policy	Captures as

Sync mode: MCP hybrid
Refresh: live + reconciliation reads
Direction: Egnyte → Well

What Well does with your Egnyte connection

Connect

Connect Egnyte over OAuth (MCP DCR): Well registers a client through Egnyte's OAuth Dynamic Client Registration and you approve on Egnyte's side, so the password never reaches Well; Well holds only a scoped token it can refresh.

Sync

Well brings file, folder, and permission in from Egnyte on live events backed by periodic reconciliation reads. The first sync backfills history in the background and the connection stays live after.

Enrich

Well resolves each Egnyte entity into indexed record, workspace context, and policy, assigns categories, and links every record to an audit trail across the rest of your connected tools.

Available

Your data from Egnyte lands in the workspace as indexed record, workspace context, and policy you can search, chart, and automate.

Questions Egnyte unlocks

Ask in plain language. Well answers from your connected Egnyte connection, resolved against the rest of your stack.

Ask Well

Ask anything about your Egnyte connection

Summarise this month

What needs attention?

Find unmatched records

Ask about your Egnyte connection…

Connect Egnyte in three steps

01
Authorise Egnyte via MCP
From Well's Connections panel, search for Egnyte and click Connect. Well discovers Egnyte's MCP OAuth metadata from its .well-known endpoint, registers a client via Dynamic Client Registration, and routes you through the authorize prompt on Egnyte's side. No client credentials to paste.
- AuthOAuth (MCP DCR)
- DiscoveryMCP .well-known
- MCP servermcp-server.egnyte.com/mcp
02
Map your entities
Well's MCP client discovers file, folder, and permission from Egnyte that Egnyte's MCP server exposes and brings them into your workspace using the canonical mappings defined in Well's data-views layer. You can inspect the workspace data model from Settings > Data Model.
- Mappingpreconfigured by Well
03
Use the data
Ask questions in conversation, build records tables, or let agents act on Egnyte records. Because Egnyte ships through MCP, Well treats every entity it exposes as queryable graph state alongside the rest of your connected tools.
- First syncstarts as soon as connect completes

MCP handshake typically completes under a minute on warm connections. Resource enumeration runs immediately after; full backfill of historical Egnyte records happens in the background.

How Egnyte stays secure with Well

Well connects to Egnyte's MCP server (mcp-server.egnyte.com/mcp) via the Model Context Protocol. The MCP server itself handles credential issuance through OAuth Dynamic Client Registration; Well never sees a long-lived Egnyte secret. Tokens are scoped to the file, folder, and permission Egnyte exposes and refreshed server-side. Reads only, Well cannot modify or delete Egnyte records.

OAuth (MCP DCR)Encrypted at restGDPR compliant

Read the full privacy and security policy

Scopes Well requestsmcp-server.egnyte.com/mcp

Read Egnyte records
Resources the Egnyte MCP server exposes, scoped by your OAuth approval.
granted
Resolve file, folder, and permission across your stack
Match identifiers in Egnyte against the same entities your other connected tools expose, so each record carries cross-tool context.
granted
Modify or delete Egnyte records
Not granted; Egnyte is read-only in Well. Write-back is opt-in per connector when a write surface exists.
refused
Store Egnyte passwords or session cookies
Authentication runs through OAuth (MCP DCR) tokens we never see.
refused

Disconnect any time from Well settings or Egnyte’s admin panel.

Frequently asked questions about Egnyte and Well

From Well, open Connections, find Egnyte, and click Connect. Well discovers the OAuth metadata at mcp-server.egnyte.com/mcp/.well-known/oauth-authorization-server, registers a client on the fly via Dynamic Client Registration, and walks you through the authorize prompt on Egnyte's side. No client_id or client_secret to paste; the handshake takes roughly a minute.

Well brings in file, folder, and permission from Egnyte and reshapes each entity into your workspace: file becomes indexed record; folder becomes workspace context. Every record arrives with the source identifier preserved, so Egnyte stays the source of truth while Well lets you query the data alongside the rest of your stack.

Each Egnyte asset carries usage data (which workspace pages reference it, which agents have surfaced it in search, when it was last referenced). Asking "what Egnyte content is going stale or underused" returns the list ranked by last reference, so the content team can refresh or retire.

Yes. Egnyte permissions are indexed in your workspace as policy, so questions like "show me last week's permissions from Egnyte" return them with the original Egnyte link, the workspace context, and any related records (counterparty, period, attached document) joined inline.

Well combines live Egnyte events with periodic reconciliation reads of file, folder, and permission. New rows appear within seconds when Egnyte pushes them; periodic reads catch anything a push missed. The first connect backfills history from Egnyte in the background.

Open Connections > Egnyte in Well and click Disconnect. Well calls Egnyte's token revocation endpoint and stops calling Egnyte immediately on its side; provider-side propagation to Egnyte's admin panel varies by provider. The file, folder, and permission Well already synced stay in your workspace by default; ask Support to purge them if your compliance flow requires it.

Egnyte records are stored in the region Well operates for your workspace. Specific region details and the steps to change region are available from Support. See /privacy for the current data-handling policy.