Remote MCP Server
The Egnyte MCP Server is a fully-managed Model Context Protocol (MCP) server that enables secure integration between your Egnyte content and AI tools like Claude, ChatGPT, and other OAuth-compatible MCP clients. It provides a standardized way for LLM clients to access and interact with your Egnyte data while maintaining enterprise-grade security through OAuth 2.0 authentication.
Note: Available tools and capabilities vary based on your Egnyte plan. See Availability for details.
Tip: Not sure whether to use MCP or the REST APIs? See Choosing Between MCP and the REST APIs.
MCP Server URL
https://mcp-server.egnyte.com/mcp
Use this URL when configuring any MCP-compatible AI client to connect to your Egnyte domain.
Prerequisites
Before connecting to the Egnyte MCP Server, ensure you have:
- An active Egnyte account on one of the following plans:
- Gen 4: Essential, Elite, or Ultimate
- Gen 3: Platform Team, Platform Business, Platform Enterprise Lite, or Platform Enterprise on AFS (Advanced File System) or CFS (Cloud File System)
- An MCP-compatible AI client that supports OAuth 2.0 authentication (Claude, ChatGPT, etc.)
- Your Egnyte domain name (e.g.,
apidemo.egnyte.com) - Valid Egnyte user credentials
Authentication
The Egnyte MCP Server uses OAuth 2.0 for secure authentication. The authentication flow works as follows:
- Your AI client initiates a connection to
https://mcp-server.egnyte.com/mcp - You are redirected to Egnyte's OAuth authorization page
- Enter your Egnyte domain and authenticate with your credentials
- Review and approve the requested permissions
- The MCP server receives an access token and establishes the connection
Access tokens are managed automatically by the MCP server and refreshed as needed. All data access is limited to files and folders the authenticated user has permission to access in Egnyte.
Note: The MCP server acts as a secure conduit and does not store or cache any accessed content.
Connecting AI Clients
ChatGPT
Egnyte is available as an app in ChatGPT, enabling secure access to your Egnyte files for natural language searches, summaries, and insights while respecting your organization's permissions.
Key Benefits:
- Search and retrieve permitted files using natural language queries
- Generate summaries, analyses, or drafts grounded in your Egnyte content
- Maintain security as ChatGPT enforces Egnyte permissions and compliance
Setup Steps:
- Navigate to ChatGPT Settings and select Apps
- Find and enable the Egnyte app for your workspace
- Authenticate with your Egnyte credentials when prompted
- Start interacting with your Egnyte content directly in ChatGPT prompts
Tip: Start with prompts like "Summarize the latest project report from Egnyte" to test file access and insights. For enterprise rollout, review access controls beforehand to balance productivity and governance.
For more information, see the ChatGPT Apps documentation.
Claude
Egnyte is available as a connector in Claude, allowing you to seamlessly access your Egnyte content directly within your Claude conversations.
Setup Steps:
- Open Claude or navigate to the Claude web app
- Go to Settings → Connectors
- Find Egnyte in the available connectors list, or add as a custom connector with URL:
https://mcp-server.egnyte.com/mcp - Click Add and Connect
- You will be redirected to the Egnyte authentication page
- Enter your Egnyte domain and authenticate with your credentials
- All Egnyte tools should appear in Claude
For detailed instructions, see the official Claude + Egnyte documentation.
Claude Code
Claude Code is a command-line tool for agentic coding that allows developers to delegate coding tasks to Claude directly from their terminal. It supports MCP servers for enhanced functionality.
Setup:
Run the following command to add the Egnyte MCP server to Claude Code:
claude mcp add --transport http egnyte https://mcp-server.egnyte.com/mcp
For more information about Claude Code and MCP integration, see the official Claude Code MCP documentation.
Other MCP-Compatible Clients
Any AI client that supports the Model Context Protocol with OAuth 2.0 authentication can connect to the Egnyte MCP Server. Configure your client with the server URL https://mcp-server.egnyte.com/mcp and follow the standard OAuth authentication flow.
Available Tools
The Egnyte MCP Server provides a comprehensive set of tools for interacting with your Egnyte content. Tools are organized by functionality and marked with Read (requires read permissions) or Write (requires write permissions) access types.
Gen 3 Tool Availability
Customers on Platform Team, Platform Business, Platform Enterprise Lite, or Platform Enterprise plans without the AI Add-On have access only to the following tools:
list_filesystem_by_pathadvanced_searchget_file_contentget_upload_urlget_download_urlwhoami
Customers with the AI Add-On retain access to the full tool catalog described below.
Search and Discovery Tools
| Tool Name | Description | Key Parameters | Access Type |
|---|---|---|---|
search | Search for files by full-text query. Returns ranked documents with content snippets. The search index covers file names, document content across all supported file types, and metadata. | query | Read |
advanced_search | Advanced search with extensive filtering options including custom metadata, date ranges, folder paths, file/folder query fields, and similarity search. Date filters are Unix timestamps in milliseconds, and folder is a plain path (not URL-encoded). | query, folder, type, custom_metadata, modified_before, modified_after, uploaded_before, uploaded_after, sort_by, file_query_fields, folder_query_fields, namespaces | Read |
fetch | Fetch content of a specific document using its unique identifier. Content is truncated to 10,000 characters. | id (group_id/entry_id format) | Read |
AI-Powered Tools
| Tool Name | Description | Key Parameters | Access Type |
|---|---|---|---|
ask_document | Ask questions about a specific document using Egnyte AI | entry_id, question, include_citations | Read |
summarize_document | Generate an AI-powered summary of a document | entry_id | Read |
ask_ai_assistant | Submit a question to Egnyte AI Assistant. Returns an executionId immediately; poll get_ai_assistant_status for the answer. Scope the question with up to 20 files and folders combined, or set search_all_egnyte to search all content the user can access. The two modes cannot be combined. | question, folder_ids, file_entry_ids, search_all_egnyte | Write |
get_ai_assistant_status | Check the status of an ask_ai_assistant request. Poll while the status is IN_PROGRESS. On COMPLETED, returns responseText and citations. | execution_id, include_citations | Read |
Note: Some domains are still being moved to the asynchronous AI Assistant tools. On those domains, ask_ai_assistant returns its answer in a single call and accepts include_citations, and get_ai_assistant_status is not listed.
Agent Tools
Egnyte Agents are AI assistants configured for a specific purpose, with their own instructions and content sources. These tools let LLM clients discover the Agents available to the user and send them questions. The Agent responds as it does in Egnyte.
| Tool Name | Description | Key Parameters | Access Type |
|---|---|---|---|
list_agents | List the active Agents the user created or that are shared with the user, with each Agent's ID, name, description, and category. Egnyte's built-in Agents are not included. | (none required) | Read |
ask_agent | Submit a question to an Agent. Returns agentId, requestId, and conversationId immediately; poll get_agent_ask_status for the answer. Optional folder_ids and file_entry_ids add content to the Agent's configured scope for this question only. Questions can be up to 35,000 characters. | agent_id, question, folder_ids, file_entry_ids | Write |
get_agent_ask_status | Check the status of an ask_agent request. Poll while the status is PLANNING or IN_PROGRESS; responses can take up to two minutes. On COMPLETED, returns responseText and citations. | agent_id, request_id | Read |
Request status values
PLANNING and IN_PROGRESS mean the request is still running. COMPLETED means the answer is ready. FAILED and COMPLETED_FAILED mean the request did not succeed. AWAITING_USER_CONFIRMATION is a final state for MCP clients: the Agent is waiting for a confirmation or an external app sign-in that cannot be given through MCP. Run that Agent in the Egnyte web UI instead.
Note: Agent tools are available to customers with the AI Add-On or a Gen 4 plan, on domains where Agents are enabled. Agents are available to Power Users and Admins; standard users cannot use them.
Knowledge Base Tools (Deprecated)
| Tool Name | Description | Key Parameters | Access Type |
|---|---|---|---|
ask_knowledge_base | Query a specific Knowledge Base for information | kb_id, question, include_citations | Read |
list_knowledge_bases | List available Knowledge Bases with filtering and sorting options | sort_by, sort_direction, status, page, size, created_before, created_after | Read |
Deprecated: Egnyte Knowledge Bases are being converted to Agents, and the migration is rolling out to all domains in October 2026. Each Knowledge Base keeps its file sources, behavior, and settings, and its ID is preserved: pass the former kb_id as the agent_id in ask_agent. After a domain is migrated, ask_knowledge_base and list_knowledge_bases return an error that points to the Agent tools. Update integrations to use list_agents and ask_agent.
File System Operations
The MCP Server supports uploading and downloading binary files, including PDFs, images, spreadsheets, presentations, and archives. All file types supported by Egnyte work with these tools. For reliable transfers, keep uploads under 200 MB; larger files may not transfer reliably depending on connection speed.
| Tool Name | Description | Key Parameters | Access Type |
|---|---|---|---|
list_filesystem_by_path | List files and folders by path with comprehensive metadata options | path, sort_by, sort_direction, include_perm, list_custom_metadata, count, offset, includeStats | Read |
get_file_content | Get text content of a file with pagination support. Returns markdown/plain-text representation. Provide either group_id or path to identify the file. | group_id or path, entry_id (optional), offset, limit | Read |
create_folder | Create a new folder in Egnyte. Fails if folder already exists or parent folders do not exist. | path | Write |
upload_file | Upload a text file to Egnyte. Creates a new file or adds a new version if file already exists at the path. Supports plain text content only (UTF-8). Suitable file types include .txt, .csv, .json, .xml, .md, .html, .css, .js, .py, and similar. Maximum file size is 8 MB. | path, content | Write |
get_upload_url | Generate a single-use signed URL for direct binary file upload. Supports all file types compatible with Egnyte. Creates a new file or adds a new version if the file already exists at the path. For reliable transfers, keep files under 200 MB; larger files may not transfer reliably depending on connection speed. | path | Write |
get_download_url | Generate a single-use signed URL for direct binary file download. Use when get_file_content cannot be used or when the raw binary stream is required (e.g. PDFs, images, archives). | path | Read |
set_file_metadata | Set custom metadata on a file in Egnyte. Replaces all existing metadata in the specified namespace — it does not merge or append. Use list_metadata_namespaces first to discover valid namespaces and fields. To change one field, first read the file's current values (with list_filesystem_by_path and list_custom_metadata: true), then send every value you want to keep. The Metadata API Set Values call keeps keys you leave out, if you need to change one field without resending the rest. | group_id or entry_id, namespace, values | Write |
list_metadata_namespaces | Returns all available metadata namespaces and their field definitions for the current domain. Call this before using set_file_metadata to discover valid namespace keys and field names. | (none required) | Read |
Project Management Tools
| Tool Name | Description | Key Parameters | Access Type |
|---|---|---|---|
list_projects | List project folders in the Egnyte domain. Without folderId, returns all projects in the domain. With folderId (a root folder ID, not a path), returns only projects rooted at that folder. | folderId (optional) | Read |
Note: list_projects is the only project tool. Creating projects and reading or writing project custom fields require the Project Folder API and the Project Custom Metadata API.
Paths and IDs
Tools identify content in different ways. Use list_filesystem_by_path to move between a path and the IDs of an item.
| Identifier | Tools |
|---|---|
| Folder or file path | advanced_search (folder), list_filesystem_by_path, get_file_content (path), create_folder, upload_file, get_upload_url, get_download_url, list_comments, create_comment, list_links, create_link |
| Folder ID | ask_ai_assistant (folder_ids), ask_agent (folder_ids), list_projects (folderId) |
| File entry ID or group ID | fetch, ask_document, summarize_document, ask_ai_assistant (file_entry_ids), ask_agent (file_entry_ids), get_file_content (group_id), set_file_metadata |
Collaboration Tools
| Tool Name | Description | Key Parameters | Access Type |
|---|---|---|---|
list_comments | List comments for a specific file or all comments in the domain | file_path, start_time, end_time, count, offset | Read |
get_comment | Get detailed information for a specific comment by its unique identifier | comment_id | Read |
create_comment | Create a new comment (note) on an existing file in Egnyte | file_path, message | Write |
list_links | List Egnyte links with filtering and pagination support | type, accessibility, path, username, created_before, created_after | Read |
get_link_details | Get detailed information about a specific Egnyte link | link_id | Read |
create_link | Create a share link for a file or folder in Egnyte. Returns the created link URL and details. | path, type, accessibility, expiry_date, password, recipients, protection, send_email, notify | Write |
Identity Tools
| Tool Name | Description | Key Parameters | Access Type |
|---|---|---|---|
whoami | Return the Egnyte identity this connector is authenticated as: the username and domain. Use to confirm which account and domain the connector is bound to. | (none required) | Read |
Data Privacy and Security
When using the Egnyte MCP Server, data security and privacy are maintained through the following measures:
Data Access and Responsibilities
Customer Responsibilities:
- Customers maintain control over which AI clients are granted access to their Egnyte content
- Customers must ensure compliance with their organization's data governance policies
AI Client Responsibilities:
- AI clients must adhere to their own privacy policies and data handling practices when processing Egnyte content
Egnyte Responsibilities:
- Egnyte ensures secure OAuth 2.0 authentication
- Egnyte respects existing user permissions
- Egnyte does not store or cache any content accessed through the MCP server
Note: All data access through the MCP server is limited to the files and folders the authenticated user has permission to access in Egnyte. The MCP server acts as a secure conduit and does not retain any accessed content.
Availability
The Egnyte MCP Server is available for Egnyte customers on the following plans:
- Gen 4: Essential, Elite, and Ultimate plans
- Gen 3: Platform Team, Platform Business, Platform Enterprise Lite, or Platform Enterprise on AFS (Advanced File System) or CFS (Cloud File System)
Note: Available MCP tools and capabilities may vary based on your Egnyte domain's plan and configuration. Contact your Egnyte account manager or visit the Egnyte Plans page for details on the features included in your plan.
Rate Limiting
The same rate limits that apply to Egnyte APIs also apply to the MCP Server. Default rate limits are based on your plan. Some AI APIs have stricter limits, including a daily limit per token. An agent that calls AI-Powered or Agent tools in a loop over many files can reach that limit quickly, so scope requests to the files that matter. For details on rate limits and best practices, refer to: