Connect Egnyte to Claude Code

Let Claude create folders, upload files, and manage shared links in Egnyte. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect Egnyte to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Egnyte, you add a Egnyte MCP server: a small hosted service that exposes Egnyte's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Egnyte account. No API keys pasted into config files.

claude mcp add --transport http egnyte https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Egnyte once connected?

Full read-write Egnyte access lets Claude create and organize folders, upload and move documents into the right location, update file metadata, and generate or revoke shared links once you approve. The filing and organizing that used to mean manual uploads happen where your content already lives.

Create a new folder structure for a project inside a workspace
Upload a document to a specific folder path
Move or rename files to keep a folder organized
Generate a shared link for a file after you approve it
Update file or folder metadata to support search and governance
Revoke an existing shared link when access should end

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Egnyte access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Egnyte API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Egnyte changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Egnyte connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Egnyte connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Egnyte account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Egnyte's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to Egnyte?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Egnyte account it signs in with. Revoking access is one click in Egnyte.

More on the Egnyte connector

Egnyte connector for claude.ai Amazon S3 + Claude Code Google Cloud Storage + Claude Code Azure Blob Storage + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us