# Egnyte MCP server

> Search, read, upload and manage files in your Egnyte account from your AI assistant.

- Listing: https://mcp.tc/i/egnyte
- Connect: use the server's own URL `https://mcp-server.egnyte.com/mcp` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: OAuth sign-in
- Category: [Productivity & Projects](https://mcp.tc/c/productivity)
- Vendor: Egnyte
- Homepage: <https://www.egnyte.com/>

## About

Connects an assistant to your Egnyte content cloud account. It supports searching content, uploading files and managing files and folders in the account, with access governed by your Egnyte permissions.

Runs as a hosted streamable HTTP endpoint at https://mcp-server.egnyte.com/mcp. Users sign in with OAuth 2.0, and the sign-in flow first asks for your Egnyte domain. No local install is needed.

## What it can do

- Search files in your Egnyte account
- Upload files to Egnyte
- Manage files and folders in your account
- Sign in with your own Egnyte domain through OAuth

## Example prompts

- "Search Egnyte for the latest vendor contract"
- "Upload this report to my Egnyte project folder"
- "Find files in Egnyte that mention the Q3 budget"
- "Move the draft proposal into the Archive folder in Egnyte"

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http egnyte https://mcp-server.egnyte.com/mcp
```

2. Start Claude Code, type `/mcp`, pick **egnyte** and choose **Authenticate**. A browser window opens for the Egnyte sign-in.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Settings → Connectors** and click **Add custom connector**.

2. Name it **Egnyte** and paste this URL:

```url
https://mcp-server.egnyte.com/mcp
```

3. Click **Add**, then **Connect**, and sign in when Egnyte asks.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Egnyte&connectorUrl=https%3A%2F%2Fmcp-server.egnyte.com%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://mcp-server.egnyte.com/mcp` and click **Add**.

3. Click **Connect** and sign in when Egnyte asks.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, open **Settings → Security and login** and turn on **Developer mode**.

2. Go to `chatgpt.com/plugins` and click **+** to create an app for a remote MCP server.

3. Paste `https://mcp-server.egnyte.com/mcp` as the server URL and choose **OAuth**. ChatGPT sends you to Egnyte to sign in.

Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts.

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=egnyte&config=eyJ1cmwiOiJodHRwczovL21jcC1zZXJ2ZXIuZWdueXRlLmNvbS9tY3AifQ%3D%3D>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "egnyte": {
      "url": "https://mcp-server.egnyte.com/mcp"
    }
  }
}
```

Cursor shows **Needs login** next to the server. Click it to sign in.

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=egnyte&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fmcp-server.egnyte.com%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"egnyte","type":"http","url":"https://mcp-server.egnyte.com/mcp"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "egnyte": {
      "type": "http",
      "url": "https://mcp-server.egnyte.com/mcp"
    }
  }
}
```

VS Code asks you to sign in the first time the server starts.

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "egnyte": {
      "serverUrl": "https://mcp-server.egnyte.com/mcp"
    }
  }
}
```

2. Refresh the MCP server list in Cascade and sign in when asked.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add egnyte --url https://mcp-server.egnyte.com/mcp
codex mcp login egnyte
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.egnyte]
url = "https://mcp-server.egnyte.com/mcp"
```

### Gemini CLI

```bash
gemini mcp add --transport http egnyte https://mcp-server.egnyte.com/mcp
```

Then, inside Gemini CLI, run `/mcp auth egnyte` to sign in.

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "egnyte": {
      "type": "http",
      "url": "https://mcp-server.egnyte.com/mcp"
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://mcp-server.egnyte.com/mcp`.

## Details

- Server version: 1.0.0
- Last checked: 2026-10-03 (reachable, asks for credentials)
- Listed: 2026-10-03
- Updated: 2026-10-03

---
Source: https://mcp.tc/i/egnyte (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report