mcp-server-fanqie
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| search_booksB | Search for books on FanQie (Tomato) Novel platform by keywords. Supports searching for novels, audiobooks, comics, and short dramas. |
| get_book_detailA | Get detailed information about a specific book including title, author, description, cover, and other metadata |
| get_book_directoryB | Get the complete chapter directory of a book including all volumes and chapters |
| get_simple_directoryA | Get simplified directory information with only chapter titles and IDs |
| get_chapter_contentC | Get content of a specific chapter. This is a simplified interface that directly returns chapter text |
| get_contentB | Unified content retrieval interface supporting novels, audiobooks, short dramas, comics, batch retrieval, and whole-book download |
| get_commentsC | Get comments for a book, chapter, or other content with pagination support |
| get_device_pool_statusB | View the overall status of the device pool including all registered devices |
| register_deviceC | Register a new device to the device pool |
| get_device_statusB | View the status of devices for a specific platform |
| get_raw_contentB | Get the unprocessed raw chapter content, including the complete response data (HTML format, author notes, etc.) |
| get_ios_contentA | Get chapter content using the iOS platform interface (signed with the 8402 algorithm). Note: depends on the iOS device pool and may be temporarily unavailable |
| register_ios_deviceB | Register a new iOS device to the device pool. Note: depends on the upstream iOS service and may be temporarily unavailable |
| get_manga_progressA | Query the progress of a manga download task by its task ID (returned from the comic content interface) |
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 14 tools
Multiple tools have overlapping purposes: get_chapter_content, get_ios_content, get_raw_content, and get_content all retrieve chapter content, making it unclear which to use. Similarly, get_book_directory and get_simple_directory serve the same function with different verbosity. Device registration and status tools are unrelated to the core content domain, adding confusion.
Most tools follow a 'get_X' or 'register_X' verb_noun pattern, but there are minor deviations such as 'search_books' and 'get_simple_directory' (adjective between verb and noun). The naming is mostly consistent and predictable.
With 14 tools, the count is well within the typical 3-15 range for a focused server. Each tool serves a clear purpose in the domain of book content retrieval and device management, though some redundancy exists.
The tool surface covers basic read operations (search, get details, get directory, get content, get comments) for books, audiobooks, manga, etc. However, there are no tools for creating, updating, or deleting content, nor for user authentication or advanced search filtering. The device management tools seem out of place for a content-focused server.