legado-mcp-server
Related Servers
Alternatives to legado-mcp-server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to search, browse, download, organize, and post-process comics through MCP tools, including account login, favorites, comments, rankings, configuration, and download task control. Supports stdio, SSE, and HTTP transports while exposing knowledge resources for configuration and skill reference.-
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to search, browse, inspect, download, convert, and manage manga albums, chapters, comments, favorites, account sessions, runtime configuration, and asynchronous download tasks through standardized MCP tools and resources.-
- AlicenseAqualityCmaintenanceEnables MCP clients to access WeChat Reading data and actions, including book search, book details, reading progress, highlights, reviews, and reading statistics, via a URL-based SSE or Streamable HTTP server.191Apache 2.0
- AlicenseBqualityCmaintenanceEnables MCP-capable AI clients to search SJTU course.sjtu.plus courses, teachers, and reviews, inspect followed, ignored, and enrolled records plus community points, and, after explicit confirmation, publish or manage reviews, votes, and course notifications through the official user API.28MIT
- AlicenseNot gradedqualityAmaintenanceEnables web-based ChatGPT and Qwen Studio to connect to local agents and projects, providing secure local file read/write, task execution, and approval workflows through a unified MCP bridge.310Apache 2.0
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to search and browse comics, inspect comments and rankings, manage favorites, download albums or covers with task tracking, and convert downloaded content to ZIP, PDF, or long images through MCP tools and resources. It also supports runtime configuration updates and account login with cookie persistence.-
TDQS
Scored across 31 tools
Many tools have very similar names (e.g., book_source_save and book_source_save_many, rss_source_save and rss_source_save_many, etc.) and most lack descriptions, making it difficult to distinguish their distinct purposes. This ambiguity risks tool misselection by an agent.
All tool names follow a consistent <object>_<action> pattern (e.g., book_search, book_delete, book_source_save, legado_ping). No mixing of conventions (camelCase or verb styles) is observed, providing a predictable naming scheme.
With 31 tools, the server covers multiple domains (books, book sources, RSS sources, replace rules, config), which is comprehensive but on the heavier side. Some tools may be redundant (e.g., separate save and save_many), suggesting slight over-scoping.
The tool set covers core CRUD and lifecycle operations for books, sources, and rules, plus debugging and configuration. Minor gaps exist (e.g., no explicit book update tool, though book_save may serve that purpose), but overall the surface is well-rounded.