Sign in Book a demo
Back to Tools
Productivity & Docs OAuth
Build Your Agent View Word Documentation
microsoft-word logo

Microsoft Word MCP Tools for AI Agents

Let an agent create Word documents in OneDrive, read .docx content, and append text to existing files.

Available Tools

5 tools available in this integration

MicrosoftWord.AddTextToDocument

Append text to the end of a Word document (supports only `.docx`, 4MB limit).

MicrosoftWord.CreateDocument

Create a new Word document in OneDrive (4MB upload limit).

MicrosoftWord.GetDocument

Get a Word document's metadata and content (`.docx` only).

MicrosoftWord.InsertTextAtEnd

Append text to the end of a Word document (supports only `.docx`, 4MB limit).

MicrosoftWord.WhoAmI

Get information about the current user and their Microsoft Word environment.

Why agent-optimized tools matter

Built for intent, not API schemas

Ask the agent to "create a Word document in OneDrive with a project brief and append the latest decisions." Arcade picks the right Microsoft Word actions without guessing document IDs or upload details.

Up to 100x fewer tokens

Microsoft Word reads are limited to the document you request, so the agent can inspect one .docx without loading an entire OneDrive into the model.

Complete the workflow end to end

Create a document, read its contents, append text, request approval, and save the update through one toolkit designed around the complete document task.

Make actions predictable and controlled

Arcade tools return structured results and useful errors across users and runs. Teams can apply scope restrictions, redaction, and approval policies so agents follow the same controls every time.

Securing Microsoft Word

The more capabilities agents get, the more useful they are. However, more capabilities bring more risks of undesired effects such as data loss and exfiltration.

This is why Arcade provides you with contextual rules that dictate how and when a tool is allowed to run. Arcade’s contextual access lets you govern tool visibility and behavior at every stage of execution and control who can see a tool, what inputs are allowed, and what comes back.

Learn about Contextual Access Policies

For Microsoft Word, you can implement some of these policies:

Access when tools are listed for a user
  • Hide MicrosoftWord.CreateDocument from agents unless the roles your IDP marks as document owners are active, so unauthorized agents cannot create files in users' OneDrive accounts.
  • Restrict MicrosoftWord.InsertTextAtEnd to agents operating under your document-editor role, so a regular user cannot append unreviewed text to shared documents.
  • Hide MicrosoftWord.AddTextToDocument from agents without your approved document-editor role, so they cannot append unreviewed language to shared Word files.
Pre-execution before each tool call
  • Require human approval before MicrosoftWord.CreateDocument runs, so an agent cannot create an unsolicited document in a user's OneDrive.
  • Block MicrosoftWord.InsertTextAtEnd when the target document is marked read-only or legally held, so automation cannot alter records that must remain unchanged.
  • Require human approval before MicrosoftWord.AddTextToDocument appends text to a document in a shared OneDrive folder, so an agent cannot change team content without review.
Post-execution after the tool returns
  • Redact the document body MicrosoftWord.GetDocument returns when it contains credentials, access tokens, or personal identification numbers before the content reaches the model.
  • Strip personal profile fields and tenant identifiers from MicrosoftWord.WhoAmI results, so the model receives only the account context needed to choose the right document.

How to use Microsoft Word with your agent

Connect Microsoft Word to your MCP client and give your agent access to OneDrive documents. Follow the walkthrough from authorization to its first document action.

Your questions, answered

A Microsoft Word MCP server exposes Word document capabilities as structured tools that an AI agent can call through the Model Context Protocol. After a user authorizes their Microsoft account, the agent can create, read, and append text to permitted .docx files in OneDrive.

Microsoft does not provide a first-party Microsoft Word MCP server here. Arcade provides the MCP runtime, per-user OAuth, approval workflows, redaction, and access controls for agents that need to create, read, or update Word documents.

Arcade agents can create new .docx documents in OneDrive, retrieve document metadata and content, and append text to the end of existing documents. The document operations support .docx files up to 4 MB.

Microsoft Word access uses per-user OAuth permissions for the OneDrive and Word document actions the agent needs. The exact permissions depend on whether the workflow only reads documents or also creates and appends content; grant the narrowest access that supports it.

Yes. Each user authorizes their own Microsoft account through OAuth. Word actions run under that user's authorization, so the agent can access only the documents and permissions that user has approved.

Yes. Contextual Access policies can require human approval before consequential Microsoft Word actions, such as creating a document or appending text to an existing one. The call proceeds only after the policy's conditions have been satisfied.

Arcade proxies Microsoft Word API calls and does not persist your document content as part of normal tool execution. OAuth credentials are brokered and stored encrypted at rest, and the model never receives raw credentials.

Any framework or client that can connect to Arcade's MCP gateway or tool APIs works, including LangChain, OpenAI Agents, CrewAI, Claude Desktop, Claude Code, Cursor, Visual Studio Code, Microsoft Copilot Studio, and GitHub Copilot.

Arcade refreshes access while the user's Microsoft authorization remains valid. If access is revoked, rotated, or can no longer be refreshed, Word actions stop until the user reconnects their account.

Microsoft Graph and OneDrive throttling and account limits still apply to calls made through Arcade. Document operations support .docx files up to 4 MB, and the toolkit does not add a separate rate-limit guarantee.

Ready to actually ship your agent?

Connect your agent to Microsoft Word with managed OAuth, agent-optimized tools and approval controls for consequential actions.

Build Your Agent Read the Microsoft Word Quickstart