Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"Egnyte Document Retriever": {
"args": [
"--directory",
"/path/to/egnyte-mcp-server",
"run",
"server.py"
],
"command": "uv"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
An MCP (Model Context Protocol) server that connects to your Egnyte domain and exposes document search and retrieval functionality for use in AI agents like Cursor, Claude, or OpenAI.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
uvx 'egnyte' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked egnyte against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in productivity / cloud
Persistent memory using a knowledge graph
Dynamic problem-solving through sequential thought chains
mini cli search engine for your docs, knowledge bases, meeting notes, whatever. Tracking current sota approaches while being all local
MCP Server for GCP environment for interacting with various Observability APIs.
MCP Security Weekly
Get CVE alerts and security updates for Egnyte Mcp Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
An MCP (Model Context Protocol) server that connects to your Egnyte domain and exposes document search and retrieval functionality for use in AI agents like Cursor, Claude, or OpenAI.
This server uses Egnyte’s public APIs and Python SDK to support secure, real-time access to your Egnyte content, enabling smart AI-driven workflows while respecting existing permissions.
Model Context Protocol (MCP) is a framework to help AI agents securely query external systems for real-time context.
The Egnyte MCP Server allows agents to:
| Tool Name | Description |
|---|---|
search_for_document_by_name | Searches for a document in your Egnyte domain using its filename. |
git clone https://github.com/egnyte/egnyte-mcp-server.git
cd egnyte-mcp-server
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
uv pip install egnyte
📄 Egnyte SDK Documentation
🔗 Egnyte SDK GitHub
.env FileCreate a .env file inside the root directory with the following content:
DOMAIN=your-egnyte-domain.egnyte.com
ACCESS_TOKEN=your-access-token-here
Replace your-egnyte-domain.egnyte.com with your actual Egnyte domain.
Replace your-access-token-here with your actual Egnyte API access token.
This .env file is necessary for the server to authenticate and connect securely to your Egnyte domain.
uv run server.py --python 3.11
This will start the MCP server locally and make the tools available to MCP-compliant clients.
This is a sample MCP (Model Context Protocol) client that connects to a locally running MCP server using fastmcp.
It uses Python Stdio Transport to communicate with the server and call specific tools by name.
server.py) via Python Stdio.fastmcp library installed:
uv pip install fastmcp
server.py) running locally.env file configuredpython client.py
{
"mcpServers": {
"Egnyte Document Retriever": {
"command": "uv",
"args": [
"--directory",
"/path/to/egnyte-mcp-server",
"run",
"server.py"
]
}
}
}
✅ Replace /path/to/egnyte-mcp-server with your actual directory path.
![Cursor MCP Config](https://raw.githubusercontent.com/egnyte/egnyte-mcp-server/HEAD/images/