Office Live MCP
Related Servers
Alternatives to Office Live MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceLets any AI agent read and edit the Excel and Word documents a user already has open, attaching through COM so it sees unsaved edits, recalculated formulas, pivot tables, slicers and charts, and can bridge content between the two apps with journaling, undo, read-only mode and allowed-folder limits.1MIT
- AlicenseNot gradedqualityBmaintenanceSuite of MCP servers for local-first, governed automation of Microsoft Office files (Excel, PowerPoint, Word) via structured tool calls.107 PyPI8MIT
- FlicenseNot gradedqualityDmaintenanceMCP server for driving Office add-ins (Excel, Word, Outlook, PowerPoint, OneNote) through high-level workflow tools and queries, enabling LLM agents to automate document tasks across Microsoft Office applications via a single Go binary.4-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to read and edit live PowerPoint presentations on Windows through a real, visible desktop PowerPoint window, covering slides, text, shapes, notes, tables, and file operations. Supports MCP over stdio and HTTP, plus HTTP/OpenAPI and CLI access, with readback, screenshots, and a Chinese operation log for verifying results.PolyForm Noncommercial 1.0.0
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to route Office and PDF tasks through a single MCP interface, including Word/Excel/PowerPoint reads and edits, zero-loss Excel XML edits, PPTX/DOCX generation, Markdown-to-Word conversion, and multi-strategy PDF parsing, while enforcing workspace and write-safety gates.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to open, read, and edit Word and Excel documents through a local bridge, create Word files in existing SharePoint folders, and work with document content via an Office add-in.GPL 3.0
TDQS
Scored across 88 tools
Across Word, PowerPoint, and Excel the tool purposes are mostly separable, but the PowerPoint inspection cluster (inspect_slide, scan_slide, preview_deck, read_deck_text, inspect_deck) and the XML/edit escape-hatch cluster (edit_slide_xml, edit_slide_zip, edit_shape_paragraphs, execute_officejs) have overlapping use cases. Descriptions help, but misselection is still plausible with 88 tools.
Names are overwhelmingly snake_case with a verb_noun pattern, and domain-specific terms are used consistently within Word, PowerPoint, and Excel. There are minor deviations such as screenshot_slide, freeze_panes, and get_local_copy, but the convention remains readable.
88 tools is an extreme tool count for an MCP surface, even for a multi-application Office server. Many fine-grained operations could be consolidated or handled by the generic execute_* escape hatches, so the set is far beyond a well-scoped count.
Coverage is strong across all three Office domains: Word paragraphs, tables, comments, properties, and content controls; PowerPoint slides, shapes, notes, charts, images, and XML; Excel ranges, sheets, tables, charts, formatting, comments, protection, and PivotTables. A few lifecycle gaps, such as slide/table deletion, likely require the generic execute_* fallback.