How to integrate One drive MCP with LlamaIndex

This guide walks you through connecting One drive to LlamaIndex using the Composio tool router. By the end, you'll have a working One drive agent that can share project folder with your team, download the latest version of report.docx, check who can access budget.xlsx through natural language commands. This guide will help you understand how to give your LlamaIndex agent real control over a One drive account through Composio's One drive MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Get started for free Get a demo

One drive

Oauth2S2s Oauth2

OneDrive is Microsoft’s cloud storage for storing, syncing, and sharing files across devices. Access your files securely anywhere with real-time collaboration and offline support.

60 Tools9 Triggers

Managed auth

Connect One drive without auth hassles

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

Try for free

Introduction

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

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

Also integrate One drive with

ChatGPT OpenAI Agents SDK Claude Agent SDK Claude Code Claude Cowork Codex OpenCode Cursor VS Code OpenClaw Hermes CLI Google ADK LangChain Vercel AI SDK Mastra AI CrewAI

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 One drive
Connect LlamaIndex to the One drive MCP server
Build a One drive-powered agent using LlamaIndex
Interact with One drive 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 One drive MCP server, and what's possible with it?

The One drive MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your OneDrive account. It provides structured and secure access to your cloud files and folders, so your agent can perform actions like uploading documents, sharing files, managing storage, and retrieving version histories on your behalf.

File and folder management: Effortlessly copy, move, or delete files and folders, keeping your OneDrive organized with just a prompt.
Easy sharing and collaboration: Instantly generate secure sharing links for documents or folders, making collaboration with others seamless.
File download and preview: Have your agent fetch files or retrieve visual thumbnails for quick previews and streamlined access.
Access control and permissions review: Check who can view or edit any file or folder, and manage sharing permissions without manual clicks.
Version tracking and quota monitoring: Retrieve version histories for files and monitor your storage quota to stay on top of changes and space usage.

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 One drive account and project
Basic familiarity with async Python/Typescript

Getting API Keys for OpenAI, Composio, and One drive

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 One drive 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 one drive_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: ["one_drive"],
    },
  );

  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 One drive 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, one drive)
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 One drive 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 One drive
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 One drive 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 One drive

Run the agent

npx ts-node llamaindex-agent.ts

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

Complete Code

Here's the complete code to get you started with One drive 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: ["one_drive"],
    },
  );

  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 One drive 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 One drive to LlamaIndex through Composio's Tool Router MCP layer. Key takeaways:

Tool Router dynamically exposes One drive 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 & TRIGGERS

Supported Tools and Triggers

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

Check In Drive Item

Tool to check in a checked out driveItem resource, making the version of the document available to others.

Checkout Drive Item

Tool to check out a driveItem to prevent others from editing it and make your changes invisible until checked in.

Copy Item

Tool to copy a DriveItem (file or folder) to a new location asynchronously.

Create Drive Item Permission

Tool to create a new permission on a OneDrive drive item.

Create Sharing Link

Tool to create a sharing link for a DriveItem (file or folder) by its unique ID.

Delete Item

Tool to delete a DriveItem (file or folder) by its unique ID from the authenticated user's OneDrive.

Permanently Delete Drive Item

Tool to permanently delete a driveItem by its ID without moving it to the recycle bin.

Delete Drive Item Permission

Tool to delete a permission from a drive item.

Delete Shares Permission

Tool to delete the permission navigation property for a shared drive item.

Discard Checkout

Tool to discard the checkout of a driveItem, releasing it and discarding any changes made while checked out.

Download a file

Downloads a file from a user's OneDrive using its item ID, which must refer to a file and not a folder.

Download file by path

Downloads the contents of a file from OneDrive by its path.

Download item as format

Tool to download the contents of a driveItem converted to a specific format (e.

Download Drive Item Version Content

Tool to download the contents of a specific previous version of a drive item (file).

Follow Drive Item

Tool to follow a driveItem (file or folder) in OneDrive or SharePoint.

Get Drive

Retrieves the properties and relationships of a Drive resource by its unique ID.

Get DriveItem by Sharing URL

Tool to resolve a OneDrive/SharePoint sharing URL (or shareId) to a DriveItem with driveId and itemId.

Get Drives Following

Tool to retrieve a specific followed driveItem from a drive.

Get Group Drive

Tool to retrieve the document library (drive) for a Microsoft 365 group.

Get Item Metadata

Retrieves the metadata of a DriveItem by its unique ID.

Get Item Permissions

Retrieves the permissions of a DriveItem by its unique ID within a specific Drive.

Get Item Thumbnails

Tool to retrieve the thumbnails associated with a DriveItem.

Get Item Versions

Tool to retrieve the version history of a DriveItem by its unique ID.

Get Recent Items

Get files and folders recently accessed by the user.

Get Drive Root Folder

Tool to retrieve metadata for the root folder of the signed-in user's OneDrive.

Get Shared Item by ShareId

Tool to access a shared DriveItem or collection of shared items using a shareId or encoded sharing URL.

Get Shared Items

Tool to retrieve items shared with the authenticated user (not items the user has shared with others).

Get SharePoint List Items

Tool to get the items (list items) within a specific SharePoint list on a site.

Get Site Details

Retrieves metadata for a specific SharePoint site by its ID.

Get SharePoint Site Page Content

Gets the content of a modern SharePoint site page.

Get Drive Special Folder

Tool to retrieve a special folder in OneDrive by name.

Grant Shares Permission

Tool to grant users access to a link represented by a permission using an encoded sharing URL.

Invite User to Drive Item

Tool to invite users or grant permissions to a specific item in a OneDrive drive.

List Drive Activities

Tool to retrieve recent activities on the authenticated user's OneDrive.

List Drive Bundles

Tool to retrieve a list of bundle resources from a specified drive.

List Drives

Tool to retrieve a list of Drive resources available to the authenticated user, or for a specific user, group, or site.

List Folder Children

List the direct children (files/folders) of a OneDrive/SharePoint folder by DriveItem ID or path.

List Drive Item Activities

Tool to list recent activities for a specific item in a OneDrive drive.

List Root Drive Changes

Tool to list changes in the root of the user's primary drive using a delta token.

List Shares Permission

Tool to retrieve permission details for a shared OneDrive or SharePoint item using a share ID.

List SharePoint List Items Delta

Tool to track changes to items in a SharePoint list using a delta query.

List Site Columns

Tool to list all column definitions for a SharePoint site.

List Site Drive Items Delta

Tool to track changes to DriveItems in the default document library of a SharePoint site.

List Site Lists

Tool to list all lists under a specific SharePoint site.

List Site Subsites

Tool to list all subsites of a SharePoint site.

List Subscriptions

Tool to list the current subscriptions for the authenticated user or app.

Move Item

Tool to move a file or folder to a new parent folder in OneDrive.

Create folder

Creates a new folder in the user's OneDrive, automatically renaming on conflict, optionally within a specified parent_folder (by ID or full path from root) which, if not the root, must exist and be accessible.

Create a new text file

Creates a new plain-text file with specified content in the authenticated user's personal OneDrive, using either the folder's unique ID or its absolute path relative to the user's OneDrive root (paths are automatically resolved to IDs); note that OneDrive may rename or create a new version if the filename already exists.

Find Item

Non-recursively finds an item (file or folder) in a specified OneDrive folder; if `folder` is provided as a path, it must actually exist.

Find Folder

Finds folders by name within an accessible parent folder in OneDrive, or lists all its direct child folders if no name is specified.

List OneDrive items

Retrieves all files and folders as `driveItem` resources from the root of a specified user's OneDrive, automatically handling pagination.

Upload file

Uploads a file to a specified OneDrive folder, automatically creating the destination folder if it doesn't exist, renaming on conflict, and supporting large files via chunking.

Preview Drive Item

Generates or retrieves a short-lived, permission-bound embeddable URL for a preview of a specific item.

Restore Deleted Item

Tool to restore a deleted OneDrive driveItem (file or folder) from the recycle bin.

Search Items

Search OneDrive for files and folders by keyword.

Delete Drive Following

Tool to unfollow a driveItem by removing it from the user's followed items collection.

Update Drive Item Metadata

Tool to update the metadata of a specific item (file or folder) in OneDrive.

Update Drive Item Permissions

Tool to update the roles of an existing permission on a OneDrive drive item.

Update File Content

Tool to create an upload session for updating an existing file's content in OneDrive.

FRAMEWORKS

How to build One drive MCP Agent with another framework

ChatGPT

Use One drive MCP with ChatGPT

OpenAI Agents SDK

Use One drive MCP with OpenAI Agents SDK

Claude Agent SDK

Use One drive MCP with Claude Agent SDK

Claude Code

Use One drive MCP with Claude Code

Claude Cowork

Use One drive MCP with Claude Cowork

Codex

Use One drive MCP with Codex

Cursor

Use One drive MCP with Cursor

OpenClaw

Use One drive MCP with OpenClaw

Hermes

Use One drive MCP with Hermes

CLI

Use One drive MCP with CLI

Google ADK

Use One drive MCP with Google ADK

LangChain

Use One drive MCP with LangChain

Vercel AI SDK

Use One drive MCP with Vercel AI SDK

Mastra AI

Use One drive MCP with Mastra AI

CrewAI

Use One drive MCP with CrewAI

OpenCode

Use One drive MCP with OpenCode

VS Code

Use One drive MCP with VS Code

MORE TOOLKITS

Explore Other Toolkits

Toolkit marketplace

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.

Google Docs

Oauth2

Google Docs is a cloud-based word processor that enables document creation and real-time collaboration. Its seamless sharing and version history make team editing and content management a breeze.

Google Super

Oauth2Api Key

Google Super is an all-in-one suite combining Gmail, Drive, Calendar, Sheets, Analytics, and more. It gives you a unified platform to manage your digital life, boosting productivity and organization.

Affinda

Api Key

Affinda is an AI-powered document processing platform that automates data extraction from resumes, invoices, and more. It streamlines document-heavy workflows by turning files into structured, actionable data.

FAQ

Frequently asked questions

With a standalone One drive MCP server, the agents and LLMs can only access a fixed set of One drive tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from One drive 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 One drive tools.

Yes, absolutely. You can configure which One drive 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 One drive data and credentials are handled as safely as possible.

Start with One drive.It takes 30 seconds.

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

Start building

Customer stories

Teams ship real agents on Composio

GET STARTED FOR FREE BOOK A DEMO

Karan skipped his own birthday party to fix our critical issue. It was 10pm and he diverted his Waymo to help us instead. This really sets the bar — it shows the commitment you need when users rely on your software.

Harsha Gaddipati

Co-founder, Slashy

A lot of students tell us that the moment their connected tools start talking to each other inside Opennote feels almost magical. The agent just knows them, and it's immensely helped keep new users on the platform.

Abhi Arya

Co-founder, Opennote

We chose Composio over Pipedream because it delivered depth where it mattered — niche tools and tricky edge cases other platforms simply ignored. That gave us confidence to scale without compromising.

Nirman Dave

CEO, Zams

As a solo builder, shipping fast is life or death. The only way I can outcompete incumbents is by outmanoeuvring them. Getting bogged down managing agent auth would have been a death sentence.

Ryan Yu

Founder, Extra Thursday

Before Composio, adding tool integrations was slow and resource-intensive. Each one could take weeks of engineering time, and maintaining them meant constantly keeping up with API changes.

Tomisin Jenrola

Founder & CEO, SwarmZero

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Jerome Leclanche

Co-Founder, Ingram Technologies