cosplaytele-mcp
Related Servers
Alternatives to cosplaytele-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceProvides AI assistants with access to Civitai's collection of AI models, enabling users to browse, search, and discover AI models through MCP-compatible AI assistants.21412MIT
- AlicenseAqualityDmaintenanceMCP server for the Zerochan anime image board API. Browse the global feed, search by tags, and retrieve full entry metadata — directly from any MCP-compatible AI assistant.3MIT
- AlicenseAqualityCmaintenanceMCP server for searching cosmos.so, returning direct CDN image URLs without page scraping.338 npmMIT
- FlicenseNot gradedqualityBmaintenanceProvides an MCP interface to a unified image generation gateway, enabling AI agents to generate images through multiple free and low-cost providers, list sessions and history, and manage provider configurations.-
- AlicenseAqualityDmaintenanceMCP server for the DeepGHS anime AI ecosystem. Dataset discovery, tag search, character dataset finder, and training pipeline code generation.81MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to search, filter, and manage a private local photo library with CLIP-based text and similarity search, EXIF/GPS metadata, duplicate detection, albums, and folder indexing, returning ranked results and optional contact sheets.MIT
TDQS
Scored across 7 tools
Tools are mostly distinct: list_sources is metadata, browse is for ranked/listing views, search is keyword-based across sources, browse_tag is tag-specific, related expands from a set, open_url handles full URLs, and get_gallery fetches details. Some overlap exists between browse with a query and search, and browse_tag could be seen as a specialized browse, but descriptions clarify boundaries.
Most tools follow verb_noun naming (list_sources, open_url, get_gallery, browse_tag), while browse and search are bare verbs, and related deviates entirely. The mixed styles are still readable, but the pattern is not uniform.
Seven tools is well-scoped for a gallery aggregator server. Each tool covers a distinct interaction mode (discovery, search, browsing, detail fetch), and none feel redundant or extraneous.
The surface covers the core read-only lifecycle: discover sources, search/browse, drill into tags, open URLs, and fetch gallery details. Minor gaps exist such as explicit pagination for browse results, but the described workflows are largely complete.