Skip to main content
Glama
launchapp-dev

animus-document-engine

by launchapp-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to animus-document-engine

No user-submitted related servers found.

    Related Servers

    • TianshangScribe

      Tianshang301
      A
      license
      A
      quality
      A
      maintenance
      MCP server for Office documents — create, edit, fill templates, convert, and extract Word/Excel/PowerPoint. LaTeX-style markup, math formulas, PDF export, template loops, and document diff. stdio / SSE / Streamable HTTP with auth and rate limiting.
      12
      Apache 2.0
    • opendocswork-mcp by Aimino-Tech

      opendocswork-mcpofficial

      Aimino-Tech
      A
      license
      Not graded
      quality
      D
      maintenance
      Rust-native MCP server for Office document processing (Excel, Word, PowerPoint) enabling sub-millisecond, local-first document manipulation and export to PDF.
      162
      GPL 3.0

    • HiveMCP

      traxonLp
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server that generates and edits PowerPoint, Word, and Excel files for OpenWebUI, exposing both MCP and OpenAPI interfaces for document creation and editing.
      1
      MIT

    • mcp-genoffice

      criptogus
      A
      license
      A
      quality
      B
      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
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct operation: editing a spec, converting format, parsing, previewing, and rendering. No overlap or ambiguity.

    Naming Consistency4/5

    Four tools follow a consistent 'verb_document' pattern, but 'apply_edits' breaks the pattern slightly. Still all are verb_noun and clear.

    Tool Count5/5

    With 5 tools, the set is well-scoped for a document engine covering editing, conversion, parsing, preview, and rendering without bloat.

    Completeness4/5

    Core workflows are covered: create (render from spec), edit (apply_edits), convert, parse, preview. Minor gap: no tool to initialize a new spec, but agent can write one directly.

    Resources