egnyte

This Egnyte MCP Server exposes a tool named search_for_document_by_name which allows MCP-enabled agents to search for documents within your Egnyte domain by filename and retrieve relevant results. The server reads configuration from a local .env file (DOMAIN and ACCESS_TOKEN) to authenticate with Egnyte's API via the Python SDK, and it exposes the tool over the MCP protocol so clients can query it in real time. To use it, start the server with your preferred MCP client (for example via the uv runner shown in the installation notes), then connect an MCP client (such as Cursor or Claude) to the local server. The client can list available tools and invoke search_for_document_by_name by providing the desired filename or partial filename; the server will return matching document references and, if configured, content that can be retrieved or linked for downstream processing.

Prerequisites:

• Python 3.11+
• Internet access to install dependencies

Installation steps:

1. Clone the repository

git clone https://github.com/egnyte/egnyte-mcp-server.git
cd egnyte-mcp-server

2. Install uv (Python environment & dependency manager)

• Mac/Linux:

curl -LsSf https://astral.sh/uv/install.sh | sh

• Windows (PowerShell):

irm https://astral.sh/uv/install.ps1 | iex

3. Install Egnyte SDK

uv pip install egnyte

4. Create and configure environment variables

# Create a .env file at repo root
DOMAIN=your-egnyte-domain.egnyte.com
ACCESS_TOKEN=your-access-token-here

5. Run the MCP server locally

uv run server.py --python 3.11

This starts the MCP server locally and makes the tools available to MCP-compliant clients.

Tips and caveats:

• Ensure DOMAIN and ACCESS_TOKEN are kept secret and not committed to version control.
• The Egnyte API requires proper token permissions; verify that the token has access to the needed files.
• If you encounter network or authentication errors, double-check the .env file and ensure the Egnyte domain is correct.
• The server primarily exposes search_for_document_by_name; if you need retrieval capabilities, ensure the API usage aligns with Egnyte permissions.
• For Claude or Cursor integrations, provide the correct working directory (cwd) and, if needed, environment variables in the MCP client configuration.
• Monitor API rate limits and token expiration; rotate tokens as recommended by Egnyte.