How to integrate One drive MCP with Mastra AI

BOOK A CALLGET STARTED FOR FREE
Framework Integration Gradient
One drive Logo
Mastra AI Logo
divider

Introduction

This guide walks you through connecting One drive to Mastra AI 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 Mastra AI 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:
  • Set up your environment so Mastra, OpenAI, and Composio work together
  • Create a Tool Router session in Composio that exposes One drive tools
  • Connect Mastra's MCP client to the Composio generated MCP URL
  • Fetch One drive tool definitions and attach them as a toolset
  • Build a Mastra agent that can reason, call tools, and return structured results
  • Run an interactive CLI where you can chat with your One drive agent

What is Mastra AI?

Mastra AI is a TypeScript framework for building AI agents with tool support. It provides a clean API for creating agents that can use external services through MCP.

Key features include:

  • MCP Client: Built-in support for Model Context Protocol servers
  • Toolsets: Organize tools into logical groups
  • Step Callbacks: Monitor and debug agent execution
  • OpenAI Integration: Works with OpenAI models via @ai-sdk/openai

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, make sure you have:
  • Node.js 18 or higher
  • A Composio account with an active API key
  • An OpenAI API key
  • Basic familiarity with TypeScript

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key.
  • You need credits or a connected billing setup to use the models.
  • Store the key somewhere safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Go to Settings and copy your API key.
  • This key lets your Mastra agent talk to Composio and reach One drive through MCP.

Install dependencies

bash
npm install @composio/core @mastra/core @mastra/mcp @ai-sdk/openai dotenv

Install the required packages.

What's happening:

  • @composio/core is the Composio SDK for creating MCP sessions
  • @mastra/core provides the Agent class
  • @mastra/mcp is Mastra's MCP client
  • @ai-sdk/openai is the model wrapper for OpenAI
  • dotenv loads environment variables from .env

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_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
  • COMPOSIO_USER_ID tells Composio which user this session belongs to
  • OPENAI_API_KEY lets the Mastra agent call OpenAI models

Import libraries and validate environment

typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

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

const composio = new Composio({
  apiKey: composioAPIKey as string,
});
What's happening:
  • dotenv/config auto loads your .env so process.env.* is available
  • openai gives you a Mastra compatible model wrapper
  • Agent is the Mastra agent that will call tools and produce answers
  • MCPClient connects Mastra to your Composio MCP server
  • Composio is used to create a Tool Router session

Create a Tool Router session for One drive

typescript
async function main() {
  const session = await composio.create(
    composioUserID as string,
    {
      toolkits: ["one_drive"],
    },
  );

  const composioMCPUrl = session.mcp.url;
  console.log("One drive MCP URL:", composioMCPUrl);
What's happening:
  • create spins up a short-lived MCP HTTP endpoint for this user
  • The toolkits array contains "one_drive" for One drive access
  • session.mcp.url is the MCP URL that Mastra's MCPClient will connect to

Configure Mastra MCP client and fetch tools

typescript
const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      nasdaq: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

console.log("Fetching MCP tools from Composio...");
const composioTools = await mcpClient.getTools();
console.log("Number of tools:", Object.keys(composioTools).length);
What's happening:
  • MCPClient takes an id for this client and a list of MCP servers
  • The headers property includes the x-api-key for authentication
  • getTools fetches the tool definitions exposed by the One drive toolkit

Create the Mastra agent

typescript
const agent = new Agent({
    name: "one_drive-mastra-agent",
    instructions: "You are an AI agent with One drive tools via Composio.",
    model: "openai/gpt-5",
  });
What's happening:
  • Agent is the core Mastra agent
  • name is just an identifier for logging and debugging
  • instructions guide the agent to use tools instead of only answering in natural language
  • model uses openai("gpt-5") to configure the underlying LLM

Set up interactive chat interface

typescript
let messages: AiMessageType[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end.\n");

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

rl.prompt();

rl.on("line", async (userInput: string) => {
  const trimmedInput = userInput.trim();

  if (["exit", "quit", "bye"].includes(trimmedInput.toLowerCase())) {
    console.log("\nGoodbye!");
    rl.close();
    process.exit(0);
  }

  if (!trimmedInput) {
    rl.prompt();
    return;
  }

  messages.push({
    id: crypto.randomUUID(),
    role: "user",
    content: trimmedInput,
  });

  console.log("\nAgent is thinking...\n");

  try {
    const response = await agent.generate(messages, {
      toolsets: {
        one_drive: composioTools,
      },
      maxSteps: 8,
    });

    const { text } = response;

    if (text && text.trim().length > 0) {
      console.log(`Agent: ${text}\n`);
        messages.push({
          id: crypto.randomUUID(),
          role: "assistant",
          content: text,
        });
      }
    } catch (error) {
      console.error("\nError:", error);
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    console.log("\nSession ended.");
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main().catch((err) => {
  console.error("Fatal error:", err);
  process.exit(1);
});
What's happening:
  • messages keeps the full conversation history in Mastra's expected format
  • agent.generate runs the agent with conversation history and One drive toolsets
  • maxSteps limits how many tool calls the agent can take in a single run
  • onStepFinish is a hook that prints intermediate steps for debugging

Complete Code

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

typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

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

const composio = new Composio({ apiKey: composioAPIKey as string });

async function main() {
  const session = await composio.create(composioUserID as string, {
    toolkits: ["one_drive"],
  });

  const composioMCPUrl = session.mcp.url;

  const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      one_drive: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

  const composioTools = await mcpClient.getTools();

  const agent = new Agent({
    name: "one_drive-mastra-agent",
    instructions: "You are an AI agent with One drive tools via Composio.",
    model: "openai/gpt-5",
  });

  let messages: AiMessageType[] = [];

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

  rl.prompt();

  rl.on("line", async (input: string) => {
    const trimmed = input.trim();
    if (["exit", "quit"].includes(trimmed.toLowerCase())) {
      rl.close();
      return;
    }

    messages.push({ id: crypto.randomUUID(), role: "user", content: trimmed });

    const { text } = await agent.generate(messages, {
      toolsets: { one_drive: composioTools },
      maxSteps: 8,
    });

    if (text) {
      console.log(`Agent: ${text}\n`);
      messages.push({ id: crypto.randomUUID(), role: "assistant", content: text });
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main();

Conclusion

You've built a Mastra AI agent that can interact with One drive through Composio's Tool Router. You can extend this further by:
  • Adding other toolkits like Gmail, Slack, or GitHub
  • Building a web-based chat interface around this agent
  • Using multiple MCP endpoints to enable cross-app workflows

How to build One drive MCP Agent with another framework

OpenAI Agents SDK

OpenAI Agents SDK

Use One drive MCP with OpenAI Agents SDK

Claude Agent SDK

Claude Agent SDK

Use One drive MCP with Claude Agent SDK

Google ADK

Google ADK

Use One drive MCP with Google ADK

LangChain

LangChain

Use One drive MCP with LangChain

Vercel AI SDK

Vercel AI SDK

Use One drive MCP with Vercel AI SDK

LlamaIndex

LlamaIndex

Use One drive MCP with LlamaIndex

CrewAI

CrewAI

Use One drive MCP with CrewAI

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 Mastra AI?

Yes, you can. Mastra AI 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
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
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.

Book a call↗Get started for free