How to integrate One drive MCP with LangChain

Framework Integration Gradient
One drive Logo
LangChain Logo
divider

Introduction

This guide walks you through connecting One drive to LangChain using the Composio tool router. By the end, you'll have a working One drive agent that can share project folder with my team, download the latest version of report.docx, check who can access budget.xlsx, list my remaining onedrive storage space through natural language commands.

This guide will help you understand how to give your LangChain 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.

TL;DR

Here's what you'll learn:
  • Get and set up your OpenAI and Composio API keys
  • Connect your One drive project to Composio
  • Create a Tool Router MCP session for One drive
  • Initialize an MCP client and retrieve One drive tools
  • Build a LangChain agent that can interact with One drive
  • Set up an interactive chat interface for testing

What is LangChain?

LangChain is a framework for developing applications powered by language models. It provides tools and abstractions for building agents that can reason, use tools, and maintain conversation context.

Key features include:

  • Agent Framework: Build agents that can use tools and make decisions
  • MCP Integration: Connect to external services through Model Context Protocol adapters
  • Memory Management: Maintain conversation history across interactions
  • Multi-Provider Support: Works with OpenAI, Anthropic, and other LLM providers

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.

Supported Tools & Triggers

Tools
Triggers
Copy ItemTool to copy a driveitem (file or folder) to a new location asynchronously.
Create Sharing LinkTool to create a sharing link for a driveitem (file or folder) by its unique id.
Delete ItemTool to delete a driveitem (file or folder) by its unique id from the authenticated user's onedrive.
Download a fileDownloads a file from a user's onedrive using its item id, which must refer to a file and not a folder.
Get DriveRetrieves the properties and relationships of a drive resource by its unique id.
Get Item MetadataRetrieves the metadata of a driveitem by its unique id.
Get Item PermissionsRetrieves the permissions of a driveitem by its unique id or path within a specific drive.
Get Item ThumbnailsTool to retrieve the thumbnails associated with a driveitem.
Get Item VersionsTool to retrieve the version history of a driveitem by its unique id.
Get Drive QuotaTool to retrieve the quota information for the authenticated user's onedrive.
Get Recent ItemsRetrieves a list of items that have been recently used by the authenticated user.
Get Shared ItemsTool to retrieve a list of items that have been shared with the authenticated user.
Get SharePoint List ItemsTool to get the items (list items) within a specific sharepoint list on a site.
Get Site DetailsRetrieves metadata for a specific sharepoint site by its id.
Get SharePoint Site Page ContentGets the content of a modern sharepoint site page.
Invite User to Drive ItemTool to invite users or grant permissions to a specific item in a onedrive drive.
List Drive Item ActivitiesTool to list recent activities for a specific item in a onedrive drive.
List DrivesTool to retrieve a list of drive resources available to the authenticated user, or for a specific user, group, or site.
List Root Drive ChangesTool to list changes in the root of the user's primary drive using a delta token.
List SharePoint List Items DeltaTool to track changes to items in a sharepoint list using a delta query.
List Site ColumnsTool to list all column definitions for a sharepoint site.
List Site Drive Items DeltaTool to track changes to driveitems in the default document library of a sharepoint site.
List Site ListsTool to list all lists under a specific sharepoint site.
List Site SubsitesTool to list all subsites of a sharepoint site.
List SubscriptionsTool to list the current subscriptions for the authenticated user or app.
Move ItemTool to move a file or folder to a new parent folder in onedrive.
Create folderCreates 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 fileCreates a new text file with specified content in a onedrive folder, using either the folder's unique id or its absolute path (paths are automatically resolved to ids); note that onedrive may rename or create a new version if the filename already exists.
Find ItemNon-recursively finds an item (file or folder) in a specified onedrive folder; if `folder` is provided as a path, it must actually exist.
Find FolderFinds folders by name within an accessible parent folder in onedrive, or lists all its direct child folders if no name is specified.
List OneDrive itemsRetrieves all files and folders as `driveitem` resources from the root of a specified user's onedrive, automatically handling pagination.
Upload fileUploads a file to a specified onedrive folder, automatically renaming on conflict and supporting large files via chunking.
Preview Drive ItemGenerates or retrieves a short-lived embeddable url for a preview of a specific item.
Search ItemsSearches for driveitems in onedrive that match the specified query.
Update Drive Item MetadataTool to update the metadata of a specific item (file or folder) in onedrive.

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

What is Tool Router?

Composio's Tool Router 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 Tool Router

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

How the Tool Router works

The Tool Router 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

Prerequisites

Before starting this tutorial, make sure you have:
  • Python 3.10 or higher installed on your system
  • A Composio account with an API key
  • An OpenAI API key
  • Basic familiarity with Python and async programming

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key. You'll need credits to use the models, or you can connect to another model provider.
  • 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.

Install dependencies

pip install composio-langchain langchain-mcp-adapters langchain python-dotenv

Install the required packages for LangChain with MCP support.

What's happening:

  • composio-langchain provides Composio integration for LangChain
  • langchain-mcp-adapters enables MCP client connections
  • langchain is the core agent framework
  • python-dotenv loads environment variables

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_composio_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates your requests to Composio's API
  • COMPOSIO_USER_ID identifies the user for session management
  • OPENAI_API_KEY enables access to OpenAI's language models

Import dependencies

from langchain_mcp_adapters.client import MultiServerMCPClient
from langchain.agents import create_agent
from dotenv import load_dotenv
from composio import Composio
import asyncio
import os

load_dotenv()
What's happening:
  • We're importing LangChain's MCP adapter and Composio SDK
  • The dotenv import loads environment variables from your .env file
  • This setup prepares the foundation for connecting LangChain with One drive functionality through MCP

Initialize Composio client

async def main():
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))

    if not os.getenv("COMPOSIO_API_KEY"):
        raise ValueError("COMPOSIO_API_KEY is not set")
    if not os.getenv("COMPOSIO_USER_ID"):
        raise ValueError("COMPOSIO_USER_ID is not set")
What's happening:
  • We're loading the COMPOSIO_API_KEY from environment variables and validating it exists
  • Creating a Composio instance that will manage our connection to One drive tools
  • Validating that COMPOSIO_USER_ID is also set before proceeding

Create a Tool Router session

# Create Tool Router session for One drive
session = composio.create(
    user_id=os.getenv("COMPOSIO_USER_ID"),
    toolkits=['one_drive']
)

url = session.mcp.url
What's happening:
  • We're creating a Tool Router session that gives your agent access to One drive tools
  • The create method takes the user ID and specifies which toolkits should be available
  • The returned session.mcp.url is the MCP server URL that your agent will use
  • This approach allows the agent to dynamically load and use One drive tools as needed

Configure the agent with the MCP URL

client = MultiServerMCPClient({
    "one_drive-agent": {
        "transport": "streamable_http",
        "url": session.mcp.url,
        "headers": {
            "x-api-key": os.getenv("COMPOSIO_API_KEY")
        }
    }
})

tools = await client.get_tools()

agent = create_agent("gpt-5", tools)
What's happening:
  • We're creating a MultiServerMCPClient that connects to our One drive MCP server via HTTP
  • The client is configured with a name and the URL from our Tool Router session
  • get_tools() retrieves all available One drive tools that the agent can use
  • We're creating a LangChain agent using the GPT-5 model

Set up interactive chat interface

conversation_history = []

print("Chat started! Type 'exit' or 'quit' to end the conversation.\n")
print("Ask any One drive related question or task to the agent.\n")

while True:
    user_input = input("You: ").strip()

    if user_input.lower() in ['exit', 'quit', 'bye']:
        print("\nGoodbye!")
        break

    if not user_input:
        continue

    conversation_history.append({"role": "user", "content": user_input})
    print("\nAgent is thinking...\n")

    response = await agent.ainvoke({"messages": conversation_history})
    conversation_history = response['messages']
    final_response = response['messages'][-1].content
    print(f"Agent: {final_response}\n")
What's happening:
  • We initialize an empty conversation_history list to maintain context across interactions
  • A while loop continuously accepts user input from the command line
  • When a user types a message, it's added to the conversation history and sent to the agent
  • The agent processes the request using the ainvoke() method with the full conversation history
  • Users can type 'exit', 'quit', or 'bye' to end the chat session gracefully

Run the application

if __name__ == "__main__":
    asyncio.run(main())
What's happening:
  • We call the main() function using asyncio.run() to start the application

Complete Code

Here's the complete code to get you started with One drive and LangChain:

from langchain_mcp_adapters.client import MultiServerMCPClient
from langchain.agents import create_agent
from dotenv import load_dotenv
from composio import Composio
import asyncio
import os

load_dotenv()

async def main():
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))
    
    if not os.getenv("COMPOSIO_API_KEY"):
        raise ValueError("COMPOSIO_API_KEY is not set")
    if not os.getenv("COMPOSIO_USER_ID"):
        raise ValueError("COMPOSIO_USER_ID is not set")
    
    session = composio.create(
        user_id=os.getenv("COMPOSIO_USER_ID"),
        toolkits=['one_drive']
    )

    url = session.mcp.url
    
    client = MultiServerMCPClient({
        "one_drive-agent": {
            "transport": "streamable_http",
            "url": url,
            "headers": {
                "x-api-key": os.getenv("COMPOSIO_API_KEY")
            }
        }
    })
    
    tools = await client.get_tools()
  
    agent = create_agent("gpt-5", tools)
    
    conversation_history = []
    
    print("Chat started! Type 'exit' or 'quit' to end the conversation.\n")
    print("Ask any One drive related question or task to the agent.\n")
    
    while True:
        user_input = input("You: ").strip()
        
        if user_input.lower() in ['exit', 'quit', 'bye']:
            print("\nGoodbye!")
            break
        
        if not user_input:
            continue
        
        conversation_history.append({"role": "user", "content": user_input})
        print("\nAgent is thinking...\n")
        
        response = await agent.ainvoke({"messages": conversation_history})
        conversation_history = response['messages']
        final_response = response['messages'][-1].content
        print(f"Agent: {final_response}\n")

if __name__ == "__main__":
    asyncio.run(main())

Conclusion

You've successfully built a LangChain agent that can interact with One drive through Composio's Tool Router.

Key features of this implementation:

  • Dynamic tool loading through Composio's Tool Router
  • Conversation history maintenance for context-aware responses
  • Async Python provides clean, efficient execution of agent workflows
You can extend this further by adding error handling, implementing specific business logic, or integrating additional Composio toolkits to create multi-app workflows.

How to build One drive MCP Agent with another framework

FAQ

What are the differences in Tool Router MCP and One drive MCP?

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.

Can I use Tool Router MCP with LangChain?

Yes, you can. LangChain 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.

Can I manage the permissions and scopes for One drive while using Tool Router?

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.

How safe is my data with Composio Tool Router?

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.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.