SIGN UPLOG IN
X (Twitter)LinkedInGitHubDiscordYouTube

How to integrate Egnyte MCP with Claude Agent SDK

Connect Claude Agent SDK 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 freeGet a demo
Egnyte logoEgnyte
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

Introduction

This guide walks you through connecting Egnyte to the Claude Agent SDK 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 Claude Agent SDK 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 CodeClaude CoworkOpenAI Agents SDKGrok BotCodexOpenClawHermesAtomic AgentGoogle ADKLangChainVercel AI SDKMastra AILlamaIndexCrewAIPydantic AIAutoGen

TL;DR

Here's what you'll learn:
  • Get and set up your Claude/Anthropic and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for Egnyte
  • Configure an AI agent that can use Egnyte as a tool
  • Run a live chat session where you can ask the agent to perform Egnyte operations

What is Claude Agent SDK?

The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management.

Key features include:

  • Native MCP Support: Built-in support for Model Context Protocol servers
  • Permission Modes: Control tool execution permissions
  • Streaming Responses: Real-time response streaming for interactive applications
  • Context Manager: Clean async context management for sessions

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:

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

Step-by-step Guide

Step by step09 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Composio API Key and Claude/Anthropic API Key
  • Primary know-how of Claude Agents SDK
  • A Egnyte account
  • Some knowledge of Python
2

Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key
  • Go to the Anthropic Console and create an API key. You'll need credits to use the models.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.
3

Install dependencies

npm install @anthropic-ai/claude-agent-sdk @composio/core dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

  • @composio/core provides Composio integration for Anthropic
  • @anthropic-ai/claude-agent-sdk is the core agent framework
  • dotenv/config loads environment variables
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID identifies the user for session management
  • ANTHROPIC_API_KEY authenticates with Anthropic/Claude
5

Import dependencies

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

dotenv.config();
What's happening:
  • We're importing all necessary libraries including the Claude Agent SDK and Composio
  • The dotenv.config() function loads environment variables from your .env file
  • This setup prepares the foundation for connecting Claude with Egnyte functionality
6

Create a Composio instance and Tool Router session

async function chat() {
  const { COMPOSIO_API_KEY, USER_ID } = process.env;
  if (!COMPOSIO_API_KEY || !USER_ID) {
    throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
  }

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

  // Create Tool Router session for Egnyte
  const session = await composio.create(USER_ID, {
    toolkits: ['egnyte'],
  });
  const mcpUrl = session?.mcp.url;
What's happening:
  • The function checks for the required COMPOSIO_API_KEY environment variable
  • We're creating a Composio instance using our API key
  • The create method creates a Tool Router session for Egnyte
  • The returned url is the MCP server URL that your agent will use
7

Configure Claude Agent with MCP

const options: Options = {
  permissionMode: 'bypassPermissions',
  mcpServers: {
    composio: {
      type: 'http',
      url: mcpUrl,
      headers: { 'x-api-key': COMPOSIO_API_KEY }
    }
  },
  systemPrompt: 'You are a helpful assistant with access to Egnyte tools via Composio.',
  maxTurns: 10,
};
What's happening:
  • We're configuring the Claude Agent options with the MCP server URL
  • permissionMode: 'bypassPermissions' allows the agent to execute operations without asking for permission each time
  • The system prompt instructs the agent that it has access to Egnyte
  • maxTurns: 10 limits the conversation length to prevent excessive API usage
8

Create client and start chat loop

const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
  });

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}
What's happening:
  • The readline interface is created to handle user input and output
  • The query function is used to send the user's input to the agent
  • The chat loop continues until the user types 'exit' or 'quit'
9

Run the application

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}
What's happening:
  • The chat function is the entry point for the application
  • The try-catch block is used to handle any errors that occur

Complete Code

Here's the complete code to get you started with Egnyte and Claude Agent SDK:

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

async function chat() {
  const { COMPOSIO_API_KEY, USER_ID } = process.env;
  if (!COMPOSIO_API_KEY || !USER_ID) {
    throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
  }

  const composio = new Composio({ apiKey: COMPOSIO_API_KEY });
  const session = await composio.create(USER_ID, {
    toolkits: ['egnyte']
  });
  const mcp_url = session?.mcp.url;

  const options: Options = {
    permissionMode: 'bypassPermissions',
    mcpServers: {
      composio: {
        type: 'http',
        url: mcp_url,
        headers: { 'x-api-key': COMPOSIO_API_KEY }
      }
    },
    systemPrompt: 'You are a helpful assistant with access to Egnyte tools via Composio.',
    maxTurns: 10,
  };

  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
  });

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}

Conclusion

You've successfully built a Claude Agent SDK agent that can interact with Egnyte through Composio's Tool Router.

Key features:

  • Native MCP support through Claude's agent framework
  • Streaming responses for real-time interaction
  • Permission bypass for smooth automated workflows
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.
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 logo

Claude Code

Use Egnyte MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Egnyte MCP with Claude Cowork

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Egnyte MCP with OpenAI Agents SDK

Grok Bot logo

Grok Bot

Use Egnyte MCP with Grok Bot

Codex logo

Codex

Use Egnyte MCP with Codex

OpenClaw logo

OpenClaw

Use Egnyte MCP with OpenClaw

Hermes logo

Hermes

Use Egnyte MCP with Hermes

Atomic Agent logo

Atomic Agent

Use Egnyte MCP with Atomic Agent

Google ADK logo

Google ADK

Use Egnyte MCP with Google ADK

LangChain logo

LangChain

Use Egnyte MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Egnyte MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Egnyte MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Egnyte MCP with LlamaIndex

CrewAI logo

CrewAI

Use Egnyte MCP with CrewAI

Pydantic AI logo

Pydantic AI

Use Egnyte MCP with Pydantic AI

AutoGen logo

AutoGen

Use Egnyte MCP with AutoGen

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. Claude Agent SDK 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