@emit/xhs-cover-mcp-server
Related Servers
Alternatives to @emit/xhs-cover-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceConverts text or markdown into Xiaohongshu (Little Red Book) style image cards with AI cover generation, supporting multiple themes and aspect ratios.421 npm2MIT
- AlicenseAqualityCmaintenanceMCP server for generating and editing images and videos via DashScope/OpenAI-compatible APIs, with tools for text-to-image, image editing, text/video generation, and automatic local download.5MIT
- AlicenseAqualityFmaintenanceEnables generation of Xiaohongshu (Little Red Book) social media content including intelligent outlines, AI-generated images, and multi-page posts through natural language commands.523 npm15MIT
- AlicenseAqualityDmaintenanceMCP server enabling AI assistants to search, analyze, and generate content for Xiaohongshu (RedNote), China's leading lifestyle social media platform.69MIT
- AlicenseNot gradedqualityAmaintenanceEnables generating and editing images from MCP clients with automatic prompt optimization and quality presets, using Gemini, OpenAI, or BytePlus Seedream and saving results to disk.1,984 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables users to generate and edit images through an MCP client, with automatic prompt optimization, quality presets, and support for Gemini, OpenAI, and BytePlus Seedream. It saves generated images to disk and returns them to the assistant as resources.1,984 npmMIT
TDQS
Scored across 3 tools
Each tool has a distinct purpose: generate a cover, check credits, and view history. There is no overlap or boundary confusion between them.
All tools follow the same xhs_ prefix with a clear verb_noun structure: generate_cover, get_credits, get_history. This is a highly consistent and predictable naming scheme.
With 3 tools, the server is tightly scoped to its purpose of cover generation with necessary supporting utilities. Each tool earns its place and the count is within the well-scoped range.
The core workflow of generating covers is covered, and credits/history provide necessary supporting functionality. A minor gap is the lack of actions like deleting history or fetching a specific past cover by ID, but these are not critical.