Egnyte Remote

io.github.ptyagiegnytePublished by GitHub account ptyagiegnytev1.0.2Updated Oct 25, 2026

Secure integration between AI tools and Egnyte content with search, analysis, and workflow tools.

The publisher's own server: Egnyte Remote MCP Server

VerifiedStreamable HTTPWeb executableProductivity & WorkflowKnowledge & Memory

Overview

AI-generated overview

A remote MCP endpoint that connects AI tools to Egnyte content for search, analysis and workflow tasks.

What you can do
Search and analyze content stored in Egnyte through the assistant. Support workflow tasks over that content. The registry lists no individual tools, so the exact operations are not documented here.
When to use it
Consider it when your organization keeps documents in Egnyte and you want an assistant to search, analyze or act on that content without leaving the chat.
Requirements
A remote MCP endpoint reached over streamable HTTP; no local package or runtime is needed. The manifest declares no authentication, environment variables or headers, so how access to Egnyte content is granted is not stated.
Before you install
The server is described as a secure integration with Egnyte content, but the manifest declares no authentication, so confirm how access is controlled before connecting. Workflow tools may change or act on stored content; verify what they can write before use.

Installation

In SourceWeft

  1. Open Egnyte Remote in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.ptyagiegnyte%2Fegnyte-remote/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "egnyte-remote": {
      "type": "http",
      "url": "https://ptyagiegnyte.github.io/egnyte-remote/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.2LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Egnyte integrations