fanqie-writer-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FANQIE_HTTP_TOKEN | No | Access token (a long random string) for the Streamable HTTP transport. Set this when exposing the server beyond localhost (e.g. `FANQIE_HTTP_TOKEN=你的随机长串 node server.js --http 8787 --host 0.0.0.0`); clients then send it as `Authorization: Bearer <token>`. When unset, the endpoint performs no authentication and is only recommended for the local loopback address. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_authA | 检查番茄作家后台登录态是否有效（读取 auth.json 或环境变量中的 Cookie/CSRF，调一次书单接口验证）。返回账号下的小说数量概览。 |
| list_booksA | 列出账号下所有小说（book_id、书名、字数、状态）。批量上传前先用它拿到 book_id。 |
| use_bookA | 设置当前操作的 book_id（后续工具不传 book_id 时默认用它）。 |
| list_volumesA | 列出小说的分卷（volume_id、卷名）。多卷作品批量上传时需要它来做卷映射。 |
| list_chaptersA | 列出某分卷下的章节（item_id、标题、状态、字数），用于确认哪些章已上传、避免重复。 |
| upload_chapterA | 上传单章。内容二选一：① title + content（纯文本，按行分段；也可直接给 HTML）；② file=本地稿件路径（自动解析首行标题）。mode=draft 只存草稿（默认，安全）；mode=publish 提交审核。publish_time 传 ISO 时间则定时发布。 |
| batch_uploadA | 批量上传章节（核心工具）。source 支持三种：① 作品目录（含 chapters.json + chapters/NNNN.md，自动取标题与分卷号）；② 普通目录（*.md 按文件名排序，首行「第N章 …」作标题）；③ manifest .json。默认 dry_run=true 只返回上传计划（标题/字数/段落数），确认后传 dry_run=false 真正上传。mode 默认 draft 存草稿；publish 才提交审核（审核中不可改）。支持 range（如 1-20）、volume_map（稿件卷号→番茄 volume_id）、限速与失败策略。 |
| update_chapterA | 覆盖更新已存在的章节（按 item_id，来自 list_chapters）。仅草稿可改；已提交审核的章节改不了（平台返回 -3027）。 |
| preview_htmlA | 把纯文本转成番茄正文 HTML（ 段落）看效果，不动任何远端数据。用于格式自查。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
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.
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.
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.
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.