How to integrate Egnyte MCP with LlamaIndex

Connect LlamaIndex to Egnyte MCP. List all files in your egnyte projects folder, share the latest contract with the legal team, and more using natural language, with authentication handled for you.

Get started for free Get a demo

Egnyte

Oauth2

Egnyte is a cloud-based platform for secure file sharing, storage, and governance. It helps teams collaborate efficiently while maintaining data compliance and security.

60 Tools

Managed auth

Connect Egnyte without auth hassles

We manage OAuth, API keys, token refresh, and scopes — you just build.

Book a call

Explore the MCP Gateway

Introduction

This guide walks you through connecting Egnyte to LlamaIndex using the Composio tool router. By the end, you'll have a working Egnyte agent that can list all files in your egnyte projects folder, share the latest contract with the legal team, search egnyte for documents about q2 planning through natural language commands.

This guide will help you understand how to give your LlamaIndex agent real control over a Egnyte account through Composio's Egnyte MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Egnyte with

Claude Code Claude Cowork OpenAI Agents SDK Claude Agent SDK Grok Bot Codex OpenClaw Hermes Atomic Agent Google ADK LangChain Vercel AI SDK Mastra AI CrewAI Pydantic AI AutoGen

TL;DR

Here's what you'll learn:

Set your OpenAI and Composio API keys
Install LlamaIndex and Composio packages
Create a Composio Tool Router session for Egnyte
Connect LlamaIndex to the Egnyte MCP server
Build a Egnyte-powered agent using LlamaIndex
Interact with Egnyte through natural language

What is LlamaIndex?

LlamaIndex is a data framework for building LLM applications. It provides tools for connecting LLMs to external data sources and services through agents and tools.

Key features include:

ReAct Agent: Reasoning and acting pattern for tool-using agents
MCP Tools: Native support for Model Context Protocol
Context Management: Maintain conversation context across interactions
Async Support: Built for async/await patterns

What is the Egnyte MCP server, and what's possible with it?

The Egnyte MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Egnyte account. It provides structured and secure access to your files, folders, shared links, users, groups, notes, and metadata, so your agent can search content, manage files, create shared links, organize users and groups, and review account information on your behalf.

File search and retrieval: Instruct your agent to search files using metadata filters, inspect file or folder details, and download the content you need.
File uploads and updates: Have your agent upload a new file or update an existing file at a chosen location in Egnyte.
Secure content sharing: Let the agent create shared links for files or folders with access and expiration settings, list existing links, and review your domain's sharing rules.
User and group administration: Direct your agent to create users or groups, add group members, list people and groups, and retrieve user details.
Content governance and cleanup: Have your agent review file metadata, remove metadata namespaces, or delete notes and comments that are no longer needed.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step10 STEPS

Prerequisites

Before you begin, make sure you have:

Python 3.8/Node 16 or higher installed
A Composio account with the API key
An OpenAI API key
A Egnyte account and project
Basic familiarity with async Python/Typescript

Getting API Keys for OpenAI, Composio, and Egnyte

OpenAI API key (OPENAI_API_KEY)

Go to the OpenAI dashboard
Create an API key if you don't have one
Assign it to OPENAI_API_KEY in .env

Composio API key and user ID

Log into the Composio dashboard
Copy your API key from Settings
- Use this as COMPOSIO_API_KEY
Pick a stable user identifier (email or ID)
- Use this as COMPOSIO_USER_ID

Installing dependencies

npm install @composio/llamaindex @llamaindex/openai @llamaindex/tools @llamaindex/workflow dotenv

Create a new Typescript project and install the necessary dependencies:

@composio/llamaindex: Composio's LlamaIndex integration
@llamaindex/openai: OpenAI LLM integration
@llamaindex/tools: MCP client for LlamaIndex
@llamaindex/workflow: Workflow framework for LlamaIndex
dotenv: Environment variable management

Set environment variables

bash

OPENAI_API_KEY=your-openai-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id

Create a .env file in your project root:

These credentials will be used to:

Authenticate with OpenAI's GPT-5 model
Connect to Composio's Tool Router
Identify your Composio user session for Egnyte access

Import modules

import "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();

Create a new file called egnyte_llamaindex_agent.ts and import the required modules:

Key imports:

dotenv.config loads .env at runtime
readline gives us a simple CLI chat loop
Composio is the main Composio SDK client
mcp connects to an MCP endpoint
createAgent builds a LlamaIndex agent
openai configures the LLM backend

Load environment variables and initialize Composio

const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

if (!OPENAI_API_KEY) throw new Error("OPENAI_API_KEY is not set");
if (!COMPOSIO_API_KEY) throw new Error("COMPOSIO_API_KEY is not set");
if (!COMPOSIO_USER_ID) throw new Error("COMPOSIO_USER_ID is not set");

What's happening:

This ensures missing credentials cause early, clear errors before the agent attempts to initialise.

Create a Tool Router session and build the agent function

async function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

  const composio = new Composio({
    apiKey: COMPOSIO_API_KEY,
    provider: new LlamaindexProvider(),
  });

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["egnyte"],
    },
  );

  const mcpUrl = session.mcp.url;
  console.log(`Composio Tool Router MCP URL: ${mcpUrl}`);

  const server = mcp({
    url: mcpUrl,
    clientName: "composio_tool_router_with_llamaindex",
    requestInit: {
      headers: {
        "x-api-key": COMPOSIO_API_KEY!,
      },
    },
    // verbose: true,
  });

  const tools = await server.tools();

  const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" });

  const agent = createAgent({
    name: "composio_tool_router_with_llamaindex",
        description : "An agent that uses Composio Tool Router MCP tools to perform actions.",
    systemPrompt:
      "You are a helpful assistant connected to Composio Tool Router."+
"Use the available tools to answer user queries and perform Egnyte actions." ,
    llm,
    tools,
  });

  return agent;
}

What's happening here:

We create a Composio client using your API key and configure it with the LlamaIndex provider
We then create a tool router MCP session for your user, specifying the toolkits we want to use (in this case, egnyte)
The session returns an MCP HTTP endpoint URL that acts as a gateway to all your configured tools
LlamaIndex will connect to this endpoint to dynamically discover and use the available Egnyte tools.
The MCP tools are mapped to LlamaIndex-compatible tools and plug them into the Agent.

Create an interactive chat loop

async function chatLoop(agent: ReturnType<typeof createAgent>) {
  const rl = readline.createInterface({ input, output });

  console.log("Type 'quit' or 'exit' to stop.");

  while (true) {
    let userInput: string;

    try {
      userInput = (await rl.question("\nYou: ")).trim();
    } catch {
      console.log("\nAgent: Bye!");
      break;
    }

    if (!userInput) {
      continue;
    }

    const lower = userInput.toLowerCase();
    if (lower === "quit" || lower === "exit") {
      console.log("Agent: Bye!");
      break;
    }

    try {
      process.stdout.write("Agent: ");

      const stream = agent.runStream(userInput);
      let finalResult: any = null;

      for await (const event of stream) {
        // The event.data contains the streamed content
        const data: any = event.data;

        // Check for streaming delta content
        if (data?.delta) {
          process.stdout.write(data.delta);
        }

        // Store final result for fallback
        if (data?.result || data?.message) {
          finalResult = data;
        }
      }

      // If no streaming happened, show the final result
      if (finalResult) {
        const answer =
          finalResult.result ??
          finalResult.message?.content ??
          finalResult.message ??
          "";
        if (answer && typeof answer === "string" && !answer.includes("[object")) {
          process.stdout.write(answer);
        }
      }

      console.log(); // New line after streaming completes
    } catch (err: any) {
      console.error("\nAgent error:", err?.message ?? err);
    }
  }

  rl.close();
}

What's happening:

We're creating a direct terminal interface to chat with Egnyte
The LLM's responses are streamed to the CLI for faster interaction.
The agent uses context to maintain conversation history
The agent processes the request, selects appropriate Egnyte tools, and returns a result
We extract the answer from the result data structure and display it to the user
You can type 'quit' or 'exit' to stop the chat loop gracefully
Agent responses and any errors are streamed in a clear, readable format

Define the main entry point

async function main() {
  try {
    const agent = await buildAgent();
    await chatLoop(agent);
  } catch (err) {
    console.error("Failed to start agent:", err);
    process.exit(1);
  }
}

main();

What's happening here:

We're orchestrating the entire application flow
The agent gets built with proper error handling
Then we kick off the interactive chat loop so you can start talking to Egnyte

Run the agent

npx ts-node llamaindex-agent.ts

When prompted, authenticate and authorise your agent with Egnyte, then start asking questions.

Complete Code

Here's the complete code to get you started with Egnyte and LlamaIndex:

import "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";
import { LlamaindexProvider } from "@composio/llamaindex";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();

const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

if (!OPENAI_API_KEY) {
    throw new Error("OPENAI_API_KEY is not set in the environment");
  }
if (!COMPOSIO_API_KEY) {
    throw new Error("COMPOSIO_API_KEY is not set in the environment");
  }
if (!COMPOSIO_USER_ID) {
    throw new Error("COMPOSIO_USER_ID is not set in the environment");
  }

async function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

  const composio = new Composio({
    apiKey: COMPOSIO_API_KEY,
    provider: new LlamaindexProvider(),
  });

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["egnyte"],
    },
  );

  const mcpUrl = session.mcp.url;
  console.log(`Composio Tool Router MCP URL: ${mcpUrl}`);

  const server = mcp({
    url: mcpUrl,
    clientName: "composio_tool_router_with_llamaindex",
    requestInit: {
      headers: {
        "x-api-key": COMPOSIO_API_KEY!,
      },
    },
    // verbose: true,
  });

  const tools = await server.tools();

  const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" });

  const agent = createAgent({
    name: "composio_tool_router_with_llamaindex",
    description:
      "An agent that uses Composio Tool Router MCP tools to perform actions.",
    systemPrompt:
      "You are a helpful assistant connected to Composio Tool Router."+
"Use the available tools to answer user queries and perform Egnyte actions." ,
    llm,
    tools,
  });

  return agent;
}

async function chatLoop(agent: ReturnType<typeof createAgent>) {
  const rl = readline.createInterface({ input, output });

  console.log("Type 'quit' or 'exit' to stop.");

  while (true) {
    let userInput: string;

    try {
      userInput = (await rl.question("\nYou: ")).trim();
    } catch {
      console.log("\nAgent: Bye!");
      break;
    }

    if (!userInput) {
      continue;
    }

    const lower = userInput.toLowerCase();
    if (lower === "quit" || lower === "exit") {
      console.log("Agent: Bye!");
      break;
    }

    try {
      process.stdout.write("Agent: ");

      const stream = agent.runStream(userInput);
      let finalResult: any = null;

      for await (const event of stream) {
        // The event.data contains the streamed content
        const data: any = event.data;

        // Check for streaming delta content
        if (data?.delta) {
          process.stdout.write(data.delta);
        }

        // Store final result for fallback
        if (data?.result || data?.message) {
          finalResult = data;
        }
      }

      // If no streaming happened, show the final result
      if (finalResult) {
        const answer =
          finalResult.result ??
          finalResult.message?.content ??
          finalResult.message ??
          "";
        if (answer && typeof answer === "string" && !answer.includes("[object")) {
          process.stdout.write(answer);
        }
      }

      console.log(); // New line after streaming completes
    } catch (err: any) {
      console.error("\nAgent error:", err?.message ?? err);
    }
  }

  rl.close();
}

async function main() {
  try {
    const agent = await buildAgent();
    await chatLoop(agent);
  } catch (err: any) {
    console.error("Failed to start agent:", err?.message ?? err);
    process.exit(1);
  }
}

main();

Conclusion

You've successfully connected Egnyte to LlamaIndex through Composio's Tool Router MCP layer. Key takeaways:

Tool Router dynamically exposes Egnyte tools through an MCP endpoint
LlamaIndex's ReActAgent handles reasoning and orchestration; Composio handles integrations
The agent becomes more capable without increasing prompt size
Async Python provides clean, efficient execution of agent workflows

You can easily extend this to other toolkits like Gmail, Notion, Stripe, GitHub, and more by adding them to the toolkits parameter.

TOOLS

Supported Tools

Every Egnyte action and event your agent gets out of the box.

Create Permissions Audit Report

Tool to generate a permissions audit report for specified date range and filters.

Create user audit report

Tool to create a user audit report in Egnyte.

Create Bookmark

Tool to create a bookmark on a folder using either path or folder_id.

Create Comment

Tool to create a new comment/note on a file in Egnyte.

Create File Audit Report

Tool to generate a file activity audit report for specified date range and filters.

Create Group

Tool to create a new group with display name and members.

Create Shared Link

Tool to create a shared link for a file or folder with accessibility and expiration settings.

Create Login Audit Report

Tool to generate a login audit report for specified date range and filters.

Create User

Tool to create a new user in the Egnyte domain.

Delete Audit Report

Tool to delete an audit report from Egnyte.

Delete Bookmark

Tool to delete a bookmark from the user's bookmarks.

Delete File By ID

Delete a file using persistent file ID.

Delete file or folder

Tool to delete a file or folder at the specified path.

Delete Group

Tool to delete a group from the Egnyte domain.

Delete Shared Link

Tool to delete a shared link by its ID.

Delete Metadata Key

Tool to delete a metadata key from a namespace.

Delete Metadata Namespace

Tool to delete a metadata namespace.

Delete Note

Tool to delete a note/comment in Egnyte by its UUID.

Delete User

Tool to delete a user from the Egnyte domain using the SCIM-compliant endpoint.

Download File

Tool to download file content from a specified path in Egnyte.

Download File By ID

Tool to download file content using persistent file ID from Egnyte.

Get Audit Report

Tool to retrieve an audit report by type and ID.

Get audit job status

Tool to check the status of an audit report generation job.

Get Audit Stream

Tool to stream audit events starting from a specific date.

Get Bookmark

Tool to retrieve details for a specific bookmark by its ID.

Get Events Cursor

Tool to get the latest event cursor position for starting event polling.

Get Events V2

Tool to poll for events (v2) including permission_change event type in addition to file_system and note types.

Get File Metadata by ID

Tool to retrieve file metadata using persistent file ID (group_id) instead of path.

Get file or folder metadata

Tool to get file or folder metadata from Egnyte.

Get File Metadata Values

Tool to retrieve custom metadata values for a file or file version within a specific namespace.

Get Folder By ID

Tool to get folder metadata using a persistent folder ID instead of a path.

Get Folder Statistics

Tool to get statistics for a folder by ID including file counts, folder counts, and size information.

Get Group Details

Tool to retrieve details for a specific group including members and attributes.

Get Link Details

Tool to get detailed information about a shared link by its ID.

Get Link Settings

Tool to retrieve domain link settings including default expiration and allowed link types.

Get Folder Permissions

Tool to get effective permissions for a folder including users and groups with their permission levels.

Get User by ID

Tool to retrieve details for a single user by ID.

Get User Info

Tool to get information about the currently authenticated user.

List Bookmarks

Tool to list all bookmarked folders for the authenticated user with pagination support.

List Comments

Tool to list all comments/notes on a file in Egnyte.

List Groups

Tool to list all custom groups in the Egnyte domain.

List Insights Files

Tool to list recently accessed files for the authenticated user.

List Links V2

Tool to list all shared links using the v2 API with extended response fields.

List Metadata Namespaces

Tool to list all custom metadata keys in a namespace.

List Users

Tool to retrieve all users or a filtered subset from the Egnyte domain.

List workflows

Tool to list all workflows in Egnyte.

List Workflow Tasks

Tool to list all workflow tasks.

Lock File

Tool to lock a file to prevent edits by other users.

Replace Group (PUT)

Tool to fully replace a group's attributes including display name and members.

Advanced Search with Metadata Filters

Tool to perform advanced search with custom metadata filtering in Egnyte using v2 API.

Set File Metadata Values

Tool to set custom metadata values for a file or file version within a specific namespace.

Set Folder Metadata Values

Tool to set custom metadata values for a folder within a namespace.

Set Folder Permissions

Tool to set folder permissions for users or groups.

Stream Audit Events

Tool to stream audit events with filtering by audit types (FILE_AUDIT, LOGIN_AUDIT, PERMISSION_AUDIT).

Update Folder Options

Tool to update folder options including description and other settings.

Update Group

Tool to update specific attributes of a group including display name and members.

Update Metadata Key

Tool to update key definitions including display name, help text, data values for enums, and priority.

Update Metadata Namespace

Tool to update key definitions of a metadata namespace.

Update User

Tool to update specific attributes of a user in the Egnyte domain using the SCIM-compliant endpoint.

Upload File

Tool to upload or update a file at the specified path in Egnyte.

FRAMEWORKS

How to build Egnyte MCP Agent with another framework

Claude Code

Use Egnyte MCP with Claude Code

Claude Cowork

Use Egnyte MCP with Claude Cowork

OpenAI Agents SDK

Use Egnyte MCP with OpenAI Agents SDK

Claude Agent SDK

Use Egnyte MCP with Claude Agent SDK

Grok Bot

Use Egnyte MCP with Grok Bot

Codex

Use Egnyte MCP with Codex

OpenClaw

Use Egnyte MCP with OpenClaw

Hermes

Use Egnyte MCP with Hermes

Atomic Agent

Use Egnyte MCP with Atomic Agent

Google ADK

Use Egnyte MCP with Google ADK

LangChain

Use Egnyte MCP with LangChain

Vercel AI SDK

Use Egnyte MCP with Vercel AI SDK

Mastra AI

Use Egnyte MCP with Mastra AI

CrewAI

Use Egnyte MCP with CrewAI

Pydantic AI

Use Egnyte MCP with Pydantic AI

AutoGen

Use Egnyte MCP with AutoGen

MORE TOOLKITS

Explore Other Toolkits

Toolkit marketplace

Gmail

Oauth2

Gmail is Google's email service with powerful spam protection, search, and G Suite integration. It keeps your inbox organized and makes communication fast and reliable.

Google Drive

Oauth2

Google Drive is a cloud storage platform for uploading, sharing, and collaborating on files. It's perfect for keeping your documents accessible and organized across devices.

Outlook

Oauth2S2s Oauth2

Outlook is Microsoft's email and calendaring platform for unified communications and scheduling. It helps users stay organized with powerful email, contacts, and calendar management.

Google Sheets

Oauth2

Google Sheets is a cloud-based spreadsheet tool for real-time collaboration and data analysis. It lets teams work together from anywhere, updating information instantly.

FAQ

Frequently asked questions

With a standalone Egnyte MCP server, the agents and LLMs can only access a fixed set of Egnyte tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Egnyte and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. LlamaIndex fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Egnyte tools.

Yes, absolutely. You can configure which Egnyte scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Egnyte data and credentials are handled as safely as possible.

Start with Egnyte.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Egnyte tool your agent needs.Free to start.

Start building

How to integrate Egnyte MCP with LlamaIndex

Connect Egnyte without auth hassles

Introduction

Also integrate Egnyte with

TL;DR

What is LlamaIndex?

What is the Egnyte MCP server, and what's possible with it?

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

How the Composio SDK works

Step-by-step Guide

Prerequisites

Getting API Keys for OpenAI, Composio, and Egnyte

Installing dependencies

Set environment variables

Import modules

Load environment variables and initialize Composio

Create a Tool Router session and build the agent function

Create an interactive chat loop

Define the main entry point

Run the agent

Complete Code

Conclusion

Supported Tools

How to build Egnyte MCP Agent with another framework

Claude Code

Claude Cowork

OpenAI Agents SDK

Claude Agent SDK

Grok Bot

Codex

OpenClaw

Hermes

Atomic Agent

Google ADK

LangChain

Vercel AI SDK

Mastra AI

CrewAI

Pydantic AI

AutoGen

Explore Other Toolkits

Gmail

Google Drive

Outlook

Google Sheets

Frequently asked questions

What are the differences in Tool Router MCP and Egnyte MCP?+

Can I use Tool Router MCP with LlamaIndex?+

Can I manage the permissions and scopes for Egnyte while using Tool Router?+

How safe is my data with Composio Tool Router?+

Start with Egnyte.It takes 30 seconds.