Release / / with v2.1.1, v2.2.0, v2.2.1, v2.2.2, v2.2.3, v2.2.4, v2.2.5, v2.2.6, v2.2.7, v2.3.0, v2.4.0, v2.4.1, v2.4.2
xiaohongshu-mcp v2.4.3
Read and respond to Xiaohongshu notifications from MCP or HTTP.
Before you upgrade to v2.4.3
1 to fixHomepage lists now contain only note cards, excluding live cards and hot-query entries.
Read the evidence
For a reverse proxy forwarding to a loopback listener, send a loopback Host header, for example `proxy_set_header Host localhost`, to avoid HTTP 403.
Read the evidence
What changed in v2.4.3
Notification tools read unread counts and lists, reply, and like comments. This group also changes browser selection, cookie storage, comment limits and client connection behavior.
Also: Profile tabs, video metadata, nested replies and direct MCP calls are available; browser and cookie changes require upgrade attention.
Through v2.4.3. Native support is macOS Apple Silicon, Windows x64 and Linux x64; the bundled browser is required.
New things you can do
Read unread counts and notifications, reply to comments, and like or unlike notification comments.
Read the evidence
Fixed and improved
`get_my_profile` reads your own profile through MCP; `tab` selects `note`, `fav` or `liked` on own or other profiles.
Read the evidence
Comment scrolling advances in the correct container; `click_more_replies` also expands replies on short comment lists.
Read the evidence
Replies can find nested comments and comments in short lists; user-ID targeting no longer selects the containing parent thread.
Read the evidence
Filters match visible text instead of node order, and search waits for the result set to change after filtering.
Read the evidence
MCP accepts direct single-POST tool calls without initialization and supports clients declaring protocol version `2025-11-25`.
Read the evidence
Repeated QR requests replace the prior pending session; saving cookies creates missing parent directories.
Like and unlike operations are available through `POST /api/v1/feeds/like`; success is checked against the resulting state.
Favorite and unfavorite operations are available through `POST /api/v1/feeds/favorite`; success is checked against the resulting state.
Publishing waits for the content editor instead of panicking when it appears late, and verifies arrival at a success page.
Read the evidence
Seeded by @iluxav with Codex, from the release's public sources. Each change links to its evidence.