mcp -fanqie

This MCP server implements FanQie (番茄小说) data access via the MCP protocol. It exposes methods to search for books, fetch book details, gather full or simplified directories, retrieve chapter content, obtain media like audio or images, and manage device pools. You can integrate it with MCP-enabled clients (for example Claude Desktop or Cursor) to query novels, chapters, and related metadata using the provided MCP operations such as search_books, get_book_detail, get_book_directory, get_simple_directory, get_chapter_content, get_content, get_comments, and device-related endpoints. Typical workflows include searching for a title, inspecting its details and directory, then requesting specific chapters or content types (text, audio, or images) via the unified get_content interface. The server is designed to work with the FanQie API wrapper included in the project, providing a consistent MCP surface for LLM-driven content retrieval.

Prerequisites:

• Node.js 16.x or higher
• npm (comes with Node.js)

Installation steps:

1. Global installation (recommended for quick setup):

npm install -g mcp-server-fanqie

2. Local installation (no global install):

cd fanqie-mcp
npm install
npm run build

3. Run the server locally:

npm run start

4. If you plan to integrate with Claude Desktop or another MCP client, use one of the provided configuration examples in the README (e.g., using npx or a built node entry).

Notes and tips:

• The project is published as the npm package mcp-server-fanqie; use npx or install globally for quick starts.
• For Claude Desktop integration, you can use npx to run the server directly, or reference the built index.js path after a local build.
• Ensure you adjust any file system paths when using the local build configuration example.
• The MCP interface supports multiple content types via the get_content endpoint (novel, audiobook, short drama, comic, batch). Use batch mode for bulk retrieval.
• If you encounter network or API limits from FanQie, consider rate limiting requests or caching frequent queries.
• Environment variables are not strictly required for the default setup but can be added for API keys or custom FanQie endpoints if needed.