Skip to main content
Glama
Sign In
fanqie-autopub-mcp

fanqie-autopub-mcp

by yangmi829
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to fanqie-autopub-mcp

No user-submitted related servers found.

    Related Servers

    • fanqie-writer-mcp

      CommitByRyan
      A
      license
      A
      quality
      B
      maintenance
      Enables 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.
      9
      1
      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
      16 npm
      MIT

    • trip-mcp

      Bill666666
      A
      license
      A
      quality
      C
      maintenance
      Enables locally running MCP clients to log into Ctrip and Trip.com/Trip Moments, query notes, prepare image-text posts, and submit them through browser automation without a central server. It also supports destination lookup, preview screenshots, account-slot isolation, and local publish-status tracking.
      10
      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.6/5.0

    Scored across 19 tools

    Disambiguation4/5

    Tools target distinct resources (novels, chapters, short stories, local articles, auth) and single vs. batch operations are clearly separated. Minor overlap exists between get_publish_status and get_stats (both do environment self-checks) and between create_short_story_tomato and publish_short_story_tomato (both can create), but descriptions clarify the boundaries.

    Naming Consistency4/5

    A predictable verb_noun pattern with a _tomato suffix for remote/backend tools and no suffix for local tools is largely followed (list_novels_tomato, create_short_story_tomato, save_article, delete_article). Deviations like set_tomato_cookies (tomato in the middle), batch_publish_chapters (missing suffix), and get_publish_status are minor but noticeable.

    Tool Count4/5

    19 tools is on the heavier side but justified by the server's broad scope: authentication, novel creation, chapter upload (single + batch), short-story lifecycle, local article library, and diagnostics. Each tool earns its place, though the set could be trimmed slightly by merging the two diagnostic tools.

    Completeness4/5

    Core workflows are well covered: auth, novel creation, chapter publishing, batch upload, short-story CRUD + cover + publish, local article library CRUD, and status/stats. Gaps are minor — there is no update/edit for novels or chapters and no update for local articles, but the publishing lifecycle itself is complete.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources