Skip to main content
Glama

Related Servers

Alternatives to evox-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to convert Markdown documents and multi-file books into PDFs, recover Markdown from PDFs that embed their source, and open notes in a live preview GUI, all without a browser, LaTeX, or Pandoc. Each conversion returns the PDF plus page count and rendering diagnostics, and produces byte-identical output on every run.
      4
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      Enables collaborative document authoring and composition with project-based organization, transforming Markdown and LaTeX content into professional PDFs with conflict-free multi-agent editing capabilities.
      6
      20
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enterprise-grade PDF engine for AI agents. Pure TypeScript, zero-dependency, sandboxed, and local-first. Exposes 28 tools to generate ISO-compliant PDF/A documents, inspect layouts, extract text, handle digital signatures (PKCS#7), and render high-performance tables (10,000+ rows/s).
      28
      392 npm
      2
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to turn Markdown manuscripts and metadata into KDP-ready Kindle EPUBs, print interior PDFs, and full-wrap paperback covers, with spine width calculation and an upload checklist.
      3
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Enables agents to work on academic paper corpora through compact JSON tools, exposing an outline/section/edit/lint loop so a model can scaffold, read and revise one section at a time without loading whole documents. Also covers metadata editing, bibliography checks, citation-key lookup, corpus pinning, research-handoff import, and rendering to PDF via Quarto, Typst or LaTeX.
      23
      MIT

    TDQS

    A3.6/5.0

    Scored across 10 tools

    Disambiguation4/5

    Each tool maps to a distinct resource+action pair: songbook-level (init/get/generate), cover (get/update), and song CRUD (list/get/create/update/delete). There is mild overlap in that get_songbook returns song summaries and cover status, which partially duplicates list_songs and get_cover, but the descriptions make the intended granularity clear.

    Naming Consistency5/5

    All ten tools follow a strict verb_noun snake_case pattern (init_songbook, get_cover, update_song, delete_song, generate_songbook). The only variation is domain-specific verb choice (init vs create, generate), which is still readable and predictable.

    Tool Count5/5

    At 10 tools the surface is well-scoped: one init, one status, one build, two cover operations, and five song operations. No tool appears redundant or out of place for a songbook CLI wrapper.

    Completeness4/5

    Full lifecycle is covered for songs (list/get/create/update/delete) plus project init, status, cover config, and PDF generation. Minor gaps exist: no way to remove the logo image or delete/reset the songbook project, but these are workaroundable and non-blocking for core workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues