@emit/xhs-cover-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| XHS_API_KEY | No | 你的 API Key（别名） | |
| XHS_API_URL | No | API 服务地址（别名） | |
| XHS_COVER_API_KEY | No | 你的 API Key | |
| XHS_COVER_API_URL | No | API 服务地址 |
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 |
|---|---|
| xhs_generate_coverA | 生成小红书风格封面图片。输入文案，返回生成的图片 URL。 |
| xhs_get_creditsA | 查询当前账户的 credit 余额 |
| xhs_get_historyA | 获取最近的封面生成历史记录 |
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 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.