Skip to main content
Glama

Related Servers

Alternatives to Essay Writer

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      MCP server for HumanPen that lets AI agents work on real documents (.docx, .pptx, .pdf) — humanizing content to lower AI-detection scores, converting citations, condensing, and translating while preserving formatting, tables, images, and citations.
      8
      115 npm
      4
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that enforces evidence-graded, phase-gated, peer-reviewed research workflows for AI agents to conduct rigorous decision-making.
      1
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      An 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.
      10
      100
      1,057 PyPI
      69
      MIT
    • A
      license
      B
      quality
      C
      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
      17 npm
      10
      AGPL 3.0
    • F
      license
      A
      quality
      C
      maintenance
      A local-first MCP server that handles daily work tasks through your AI assistant: converts meeting notes into todos, manages todo lifecycle, tracks work hours, generates daily/weekly reports, organizes files via move-only operations, and diagnoses dev environments, all guarded by a human-maintained preview/apply safety model.
      25
      -

    TDQS

    B3.2/5.0

    Scored across 24 tools

    Disambiguation3/5

    Several research and validation tools overlap in purpose: essay.dig, essay.research.summary, essay.research.full, and essay.download.leftovers all touch sourcing/annotation/download artifacts, while essay.gates and essay.pack.validate both perform validation-like checks. The detailed descriptions and confirm-phase guardrails help, but the boundaries require unusually heavy reading to choose correctly.

    Naming Consistency3/5

    All tools share the essay. prefix and mostly use dotted namespaces, but the operation segment mixes nouns and verbs (essay.projects, essay.stage, essay.dig, essay.gates vs. essay.project.archive, essay.pack.validate, essay.pack.render_word). It remains readable and non-chaotic, but it is not a consistent verb_noun convention.

    Tool Count3/5

    24 tools is heavy for one MCP server, and several are niche phase-specific or operator/debug utilities. The complexity of a 10-stage essay workflow justifies much of the surface, but it sits at the upper bound and could likely be consolidated.

    Completeness4/5

    The surface covers setup, intake, module/sequence management, research, validation, Word rendering, shelf storage, revision, health, and debug operations, so the core lifecycle is present. Some status/retrieval operations are implicit rather than explicit, and overlapping research/pack phases make coverage less clean than it first appears.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues