Ext Ops Panel
Open dashboard
Comparison

OfficeAgent.NET vs Microsoft Office

OfficeAgent.NET is an MCP server published by ilia-sokolov. Marketplaces we read that list it: 1 (Official MCP Registry). Microsoft Office is an MCP server published by mindstone. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceOfficeAgent.NETMicrosoft Office
Official MCP Registry Listed
Version: 1.2.0
Forks (GitHub): 8
Stars (GitHub): 27
Not marked · First seen
Listed
Version: 0.3.0
Downloads/month (npm): 646
Downloads/week (npm): 127
Forks (GitHub): 4
Stars (GitHub): 14
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

OfficeAgent.NET vs Microsoft Office
FactOfficeAgent.NETMicrosoft Office
Marketplaces that list it11
Stars (GitHub) (differs)27 (better)14 (worse)
Forks (GitHub) (differs)8 (better)4 (worse)
Last release (differs)2026-10-14Not published
Where it runs (differs)On your machine (OfficeAgent.Mcp)On your machine (@mindstone/mcp-server-office)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)3, secrets among them: 05, secrets among them: 0
LicenceNot statedNot stated
Repository (differs)github.com/ilia-sokolov/officeagent.netgithub.com/mindstone/mcp-servers
Changes in the last 7 days00
First seen2026-10-112026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

OfficeAgent.NET

In its own words, on Official MCP Registry:

Create and edit Word, PowerPoint, and Excel files with typed plans and safe previews

Microsoft Office

In its own words, on Official MCP Registry:

Microsoft Office MCP server: read and edit Word documents, Excel workbooks, and PowerPoint files

How to run each

OfficeAgent.NET

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Microsoft Office As a local MCP server: npm package

Claude Code
claude mcp add --env "MCP_OFFICE_SIDECAR_STATE=<YOUR_MCP_OFFICE_SIDECAR_STATE>" --transport stdio mcp-server-office -- npx -y @mindstone/mcp-server-office

Requires: MCP_OFFICE_SIDECAR_STATE

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Only OfficeAgent.NET asks for

  • OfficeAgent__AllowCreation
  • OfficeAgent__FileSystemConnections__0__ConnectionId
  • OfficeAgent__FileSystemConnections__0__RootPath

Only Microsoft Office asks for

  • MCP_OFFICE_ADDIN_DIR
  • MCP_OFFICE_SIDECAR_DISABLE
  • MCP_OFFICE_SIDECAR_STATE
  • MCP_OFFICE_SIDECAR_STATE_DIR
  • REBEL_DISABLE_OFFICE_SIDECAR

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: OfficeAgent.NET · What it can do: Microsoft Office · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built