Skip to main content
Glama
Anselmoo

io.github.Anselmoo/mcp-ooxml-ledger

Related Servers

Alternatives to io.github.Anselmoo/mcp-ooxml-ledger

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables an AI assistant to read and write a local, file-based .emd document through shaped tools — 28 for any document, 85 with the ledger pack — rather than a general query, with every write a dry run until committed, a copy kept beside the document first, and values that break a declared type or rule refused as they are written. On hosts that support MCP Apps it also draws sheets, boards and roadmaps directly in the conversation, falling back to text elsewhere.
      4 npm
      2
      AGPL 3.0
    • A
      license
      A
      quality
      D
      maintenance
      An MCP server for byte-preserving, surgical editing of Office documents (docx, pptx) via the GenOffice engine, enabling extraction, patching, creation, deletion, watermarking, and app/CDP-driven operations without breaking layout.
      15
      5
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Structure-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.
      63
      6 npm
      10
      AGPL 3.0
    • A
      license
      D
      quality
      D
      maintenance
      Enables reading, writing, editing, and converting Office documents (ODT, DOCX, ODS, XLSX, PDF, etc.) using MCP tools, with no external dependencies.
      11
      100 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables creating and editing Microsoft Word (.docx) documents on Linux: native OMML formulas, tables, headers/footers, track changes, comments, footnotes, and document protection. Files are loaded from S3-compatible storage or URLs and saved results come back as HTTPS links with a sha256 checksum.
      MIT

    TDQS

    A4.1/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool targets a distinct operation—digest/verify, session lifecycle, receipt management, content discovery, and editing. Even closely related tools like list_receipts and verify are clearly differentiated by their outputs and intent.

    Naming Consistency4/5

    The overwhelming majority of tools follow a readable verb_noun snake_case pattern (open_document, list_receipts, delete_paragraph). The exceptions—verify, digest, and server_info—are minor deviations that do not obscure meaning.

    Tool Count5/5

    14 tools map cleanly onto the server's purpose: capability inspection, digest/verify, session lifecycle, receipt export/listing, content search, and edit operations. Each tool earns its place without redundancy or bloat.

    Completeness4/5

    The core workflow of opening a document, finding content, previewing and applying edits, committing, verifying, and exporting receipts is well covered. Minor gaps exist around receipt store management and editing support beyond paragraph/text-level operations, but agents can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive