OfficeAgent.NET

OfficeAgent.NET

OfficeAgent.NET is a .NET document-automation library built on the Open XML SDK. Its direct .NET API turns document intent into typed, validated operations for Word .docx, PowerPoint .pptx, and Excel .xlsx packages.

Use it to generate documents and presentations, make targeted edits, update tables, styles, and images, or manage comments and review state. An MCP server and adapters for Microsoft Agent Framework and Microsoft.Extensions.AI are optional interfaces to the same engine. Applications can use the engine directly without MCP.

One example is a targeted Word edit whose result remains reviewable:

What this project does

An Office Open XML file is a package of related XML parts. A small change can affect runs, styles, numbering, comments, content controls, or revision markup. OfficeAgent.NET handles that document-specific work. The model works with structured document data and JSON-serialisable operations such as "replace this clause as a tracked change" or "add a row to this table."

The same engine is available in three forms:

• an MCP server for agents that support the Model Context Protocol;
• tools for Microsoft Agent Framework and Microsoft.Extensions.AI;
• a .NET API for applications that want to control the workflow directly.

It supports Word .docx, PowerPoint .pptx, and Excel .xlsx; one client routes each document to the module that handles it. See Scope and limitations before choosing it for a workflow that depends on Office's layout or calculation engine.

What you can build

Choose a starting point

Try a Word edit

This small workflow demonstrates that OfficeAgent can change an existing OOXML file without flattening its structure. It uses tracked changes because the result is easy to verify in Word; review is one part of the broader document operation set.

Install the exact server version documented by this release:

dotnet tool install --global OfficeAgent.Mcp --version 1.2.0

Make a folder for the agent to work in and download the sample contract into it — a fictional services agreement with a clause to change, a table, an open comment, and a pending redline:

mkdir -p ~/officeagent-documents

curl -Lo ~/officeagent-documents/services-agreement.docx \ https://raw.githubusercontent.com/ilia-sokolov/OfficeAgent.NET/v1.2.0/samples/documents/services-agreement.docx

PowerShell:

$officeAgentDocuments = Join-Path $env:USERPROFILE "officeagent-documents"

New-Item -ItemType Directory -Force $officeAgentDocuments | Out-Null Invoke-WebRequest https://raw.githubusercontent.com/ilia-sokolov/OfficeAgent.NET/v1.2.0/samples/documents/services-agreement.docx -OutFile (Join-Path $officeAgentDocuments "services-agreement.docx")

Any .docx of your own works too — the sample just gives you something with a comment and a pending revision already in it.

Register the server with Claude Code, pointed at that folder and nothing else:

claude mcp add \

--env OfficeAgentFileSystemConnections0ConnectionId=documents \ --env OfficeAgentFileSystemConnections0RootPath=$HOME/officeagent-documents \ --transport stdio \ officeagent -- officeagent-mcp --stdio

PowerShell:

claude mcp add `

--env OfficeAgentFileSystemConnections0ConnectionId=documents ` --env "OfficeAgentFileSystemConnections0RootPath=$officeAgentDocuments" --transport stdio officeagent -- officeagent-mcp --stdio

For this review-specific workflow, you can optionally install the word-document-review skill before starting the client.

Then ask:

In services-agreement.docx, change the payment terms from thirty days to forty-five days.

Expected result when the client invokes OfficeAgent correctly: apply_plan reports writeOutcome: "committed" and returns an output id, and clause 3 reads forty-five days as a tracked change you can accept or reject. Open that output in Word and verify the change. The regression test also verifies that the sample's existing table, comment, earlier payment redline, and heading remain present with their tested XML semantics. It does not claim byte-for-byte identity for every unrelated OOXML part; see the bounded preservation evidence.

If the agent did not call apply_plan, or if writeOutcome is not committed, do not report the edit as complete. For unknown or writtenNotRegistered, preserve possibleOutput and follow storage recovery instead of retrying blindly.

What else the sample is good for — reviewing comments, accepting revisions, editing the table.

Next, try creating a Word document, generating a PowerPoint deck, or using the direct .NET workflow.

If it does not work

Configure broader workflows

The quick start above is deliberately the smallest thing that works. Four settings extend it:

| OfficeAgent__EphemeralConnectionId=session | Names the in-memory session connection