qimao-autopub-mcp
Related Servers
Alternatives to qimao-autopub-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables 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.1997 npmMIT
- AlicenseAqualityAmaintenanceEnables agents to batch-upload chapters from local manuscript directories to a Fanqie Novel author backend that only accepts one chapter at a time, with dry-run planning, draft or publish modes, volume routing, chapter range selection, and resumable progress. It also lists books, volumes, and chapters, updates drafts, previews body HTML, and reuses the user's browser login cookies for authentication.91MIT
- AlicenseAqualityBmaintenanceEnables 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.201MIT
- AlicenseNot gradedqualityCmaintenanceEnables 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
- AlicenseAqualityCmaintenanceEnables AI clients to interact with the Fanqie free novel author backend, including listing works, fetching chapter statuses, retrieving statistics, and publishing or drafting chapters.71MIT
- AlicenseNot gradedqualityBmaintenanceEnables long-form web novel writing workflows by ingesting chapters into a state database, running deterministic consistency checks, querying entity histories, replaying extraction results, and retrieving conflict reports via MCP tools.MIT
TDQS
Scored across 30 tools
Most tools split cleanly into remote-backend (suffix _qimao) vs local-only operations, but several overlap: publish_short_story_qimao can also create, duplicating create_short_story_qimao, and set_book_tags reuses update_book_info_qimao's page path while get_publish_status overlaps get_stats's self-check. The very detailed descriptions help an agent choose correctly, but the boundaries are not fully crisp.
Everything is snake_case verb_noun, which is predictable and readable. Minor deviations exist: the _qimao marker for backend tools is inconsistently placed (login_qimao, set_qimao_cookies, update_novel without suffix), and a few names omit the remote/local signal.
30 tools is heavy and above the comfortable 3-15 band, and the count is inflated by redundant pairs (create vs publish short story, set_book_tags vs update_book_info) and internal vs remote mirrors. The domain is genuinely broad (auth, albums, chapters, short stories, local article library, stats), so most tools earn their place, but it is borderline bloated.
Coverage is strong: auth/cookies/status, long-book create/list/update/tags/options, chapter CRUD plus batch publish, short-story lifecycle, a full local article library (save/list/get/delete/export/import), originality checks, stats/income, and genre guidance. Minor gaps remain, e.g. no explicit long-book delete and no single long-book detail getter, but core workflows are covered.