officeagent-net
Related Servers
Alternatives to officeagent-net
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceStructure-preserving Word DOCX editing MCP server with a .NET Open XML backend and Office.js live sessions. Enables safe, auditable, incremental editing of Microsoft Word documents for AI agents.6317 npm10AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables MCP agents to inspect and edit Word, Excel, PowerPoint, PDF, and text documents locally while preserving formatting, including in-place text replacement, HTML round-tripping of whole files or individual worksheets, slides, or PDF page ranges, and filling Word form fields.MIT
- AlicenseBqualityDmaintenanceAn MCP server for reading, editing, and validating Microsoft Word documents with specialized support for track changes, comments, and footnotes. It enables structural auditing, heading extraction, and precise OOXML-level document manipulation through natural language tools.1010069MIT
- AlicenseNot gradedqualityDmaintenanceEnterprise-grade document editing and management server that enables AI-powered operations on Microsoft Word DOCX files, including creating, editing, formatting, and exporting documents through both MCP protocol and RESTful API.3MIT
- AlicenseAqualityDmaintenanceMCP server for Word document (.docx) creation and manipulation — the production-grade document automation tool for AI agents.946 npmMIT
- AlicenseAqualityDmaintenanceMCP server for creating and reading Word (.docx) documents with rich formatting support.38 npmMIT
TDQS
Scored across 16 tools
The descriptions do a good job of saying which tool to use when, but the set is built in two layers: primitives (register_document, inspect_document, find_in_document, preview_plan, apply_plan) and composites (open_document, edit_document, edit_documents, refresh_document) that redo the same work in one call. Edits have three plausible entry points (apply_plan, edit_document, edit_documents) and refresh_document overlaps apply_plan with bindData, so an agent must read carefully to choose the right one.
Every name is snake_case verb_noun (list_documents, open_document, apply_plan, compare_documents), which is very consistent. The only friction is the minimal pair edit_document/edit_documents, where a single character separates a single-document tool from a bulk tool.
Sixteen tools is on the heavy side, but the domain is broad: three document formats, connections, templates, plans, merge, compare, and workbook refresh. Each tool maps to a recognizable workflow, though the duplicate primitive/composite layers mean a few could be consolidated rather than added.
Read, inspect, find, edit, preview, apply, compare, merge, refresh, and template discovery are all covered, plus removal of a registration. However, create_document is repeatedly referenced by list_documents and find_templates as the consumer of a template source but is not actually present, and there is no delete/export path, leaving a dead end for new-document creation.