xhs-mcp-light
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| xhs_loginA | 打开浏览器窗口，扫码登录小红书。 首次使用必须调用。登录成功后浏览器状态会保存到本地， 后续调用无需重新登录。 |
| xhs_check_loginA | 检查当前登录状态。 返回 logged_in=True 表示可以发布笔记。 |
| xhs_publish_noteB | 发布一篇小红书图文笔记。 |
| xhs_search_feedsC | 搜索小红书笔记（简要信息）。 |
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 4 tools
Each tool serves a distinct purpose: checking login status, logging in, publishing a note, and searching feeds. There is no overlap; even login and check_login are clearly separated by action.
All tools use the 'xhs_' prefix and snake_case, with a verb_noun pattern for most (check_login, publish_note, search_feeds). The odd one out is 'xhs_login', which is a single verb, but the pattern is still clear and consistent.
With 4 tools, the set is compact and well-scoped for a lightweight server focused on core operations: authentication, publication, and search. Each tool earns its place without unnecessary bloat.
The set covers login, publish, and search, but lacks tools for managing published notes (e.g., update, delete, list) or handling media uploads. For a 'light' server, it's acceptable but has notable gaps for a full note lifecycle.