Skip to main content
Glama
CommitByRyan

fanqie-writer-mcp

by CommitByRyan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to fanqie-writer-mcp

No user-submitted related servers found.

    Related Servers

    • fanqie-autopub-mcp

      yangmi829
      A
      license
      A
      quality
      B
      maintenance
      Enables automated publishing to the Fanqie Novel (fanqienovel.com) author backend by driving a real browser through confirmed two-step form submissions, covering login, novel creation, chapter upload with scheduled release, short-story drafting and publishing, and a local manuscript library for batch uploads.
      19
      97 npm
      MIT

    • tomato-writer-mcp

      itsyhx
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants such as Claude and Cursor to manage a Fanqie Novel author account directly — listing books, publishing or scheduling chapters, tracking per-chapter read and completion stats, checking review notices and violations, and pulling hot-word inspiration. It works over plain HTTP with cookie and CSRF-token authentication, requiring no browser automation.
      20
      1
      MIT

    • qimao-autopub-mcp

      yangmi829
      A
      license
      A
      quality
      B
      maintenance
      Enables authors to automate publishing and managing their own Qimao (七猫) novel author-backend works through an MCP client, covering login and status, book creation and metadata, chapter add/edit/delete and batch publishing, short stories, read-only statistics and income, plus a local manuscript library, originality checks, and a genre knowledge base. Write operations follow a two-stage preview-then-confirm flow and it runs over stdio or Streamable HTTP with 30 tools and 8 read-only resources.
      30
      58 npm
      MIT

    • Pure Writer MCP

      guofudamo2007-lab
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to read, search, patch, create, and export chapters in local Windows manuscript databases through stdio, with dry-run previews, revision checks, atomic batch edits, idempotent retries, automatic backups, native history, and operation-level undo. It also covers outline navigation, volume/category management, and TXT comparison or export.
      MIT

    • webnovel-mcp

      zhaopq123
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to draft long-form web novels with persistent, disk-backed memory, assembling a pre-writing task brief from structured settings, outlines, foreshadowing ledgers, and timelines, then committing post-chapter fact increments. It also audits pacing, checks per-chapter six-dimension consistency, gates commits on unresolved review findings, and can replay the commit chain to rebuild state when records and manuscripts disagree.
      1
      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

    A3.9/5.0

    Scored across 9 tools

    Disambiguation4/5

    Each tool targets a distinct action: auth check, book listing, state selection (use_book), volume/chapter listing, single upload, batch upload, update, and local preview. The only mild overlap is upload_chapter vs batch_upload, but the descriptions clearly differentiate single-chapter vs. multi-file workflows and the dry_run semantics.

    Naming Consistency4/5

    Names are uniformly snake_case with a verb_noun shape (check_auth, list_books, use_book, list_volumes, list_chapters, upload_chapter, update_chapter, preview_html). batch_upload breaks the verb-first pattern slightly and use_book is a setter rather than a lister, but both remain readable and predictable.

    Tool Count5/5

    Nine tools is well within the sweet spot and each earns its place: discovery (auth, books, volumes, chapters), action (single/batch upload, update), and a safe local preview helper. Nothing feels redundant or missing for the stated workflow.

    Completeness3/5

    The upload lifecycle is well covered (list, preview, dry-run batch, upload draft/publish, update), but there is no delete_chapter, no way to create books/volumes, and no tool to read back a chapter's existing content for verification or diffing. These gaps will force workarounds when a chapter must be removed or its current text inspected.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources