xiaohongshu-mcp login fails for Rednote users: check_login_status always not logged in
I'm using xiaohongshu-mcp v2026.03.09.0605 on macOS ARM64 with an account registered after 2025-12-08 using a non-+86 phone number (a Rednote account). The xiaohongshu-login tool opens xiaohongshu.com, which redirects me to rednote.com, so the session cookie gets the domain .rednote.com while the MCP server checks xiaohongshu.com. As a result, check_login_status always returns not logged in. Is there a supported way to use rednote.com with this MCP server?
Originally asked on GitHub: https://github.com/xpzouying/xiaohongshu-mcp/issues/579
4 answers
Status: the issue is closed as completed, but the thread contains no fix or workaround, and users were still reporting it unresolved as of July 2026. The root cause is clearly explained: after Xiaohongshu's Dec 8, 2025 terms update, accounts registered with a non-+86 phone number belong to a separate Rednote product line. Rednote users are force-redirected to rednote.com on the web, and the login cookie is scoped to .rednote.com, while the MCP server checks xiaohongshu.com.
Two workarounds were attempted in the thread and both failed. Running xiaohongshu-login normally (v2026.03.09.0605, macOS ARM64) opens xiaohongshu.com; a Rednote account gets redirected to rednote.com, so the cookie domain is .rednote.com and check_login_status always returns not logged in. Manually rewriting the cookie domain to .xiaohongshu.com and injecting it also fails, because the session itself is bound to the Rednote platform, not just the cookie domain. The reporter's requested fix — an optional rednote.com backend for login and API calls, or a config option to choose xiaohongshu.com vs rednote.com — was not implemented in this thread.
One commenter also saw a "system upgrade, overseas users temporarily cannot log in" message on the web platform, so the limitation may exist beyond the MCP tool. Note that session cookies are scoped to the platform that issued them; don't expect a cookie from rednote.com to authenticate against xiaohongshu.com endpoints.
Did this work for you?What a GitHub user tried on GitHub (Didn't work)
Ran xiaohongshu-login from xiaohongshu-mcp v2026.03.09.0605 on macOS ARM64; the tool opens xiaohongshu.com, a Rednote account is redirected to rednote.com, and the resulting cookie has domain .rednote.com while the server checks xiaohongshu.com.
Source: https://github.com/xpzouying/xiaohongshu-mcp/issues/579 (opens external site)
Did this work for you?What a GitHub user tried on GitHub (Didn't work)
Manually changed the cookie domain to .xiaohongshu.com and injected it; this still failed because the session itself belongs to the Rednote platform, not just the cookie domain.
Source: https://github.com/xpzouying/xiaohongshu-mcp/issues/579 (opens external site)
Did this work for you?What @seasidespace tried on GitHub (Outcome unclear)
Another user confirmed the same behavior and said no good solution was available at the time.
Did this work for you?
Related questions
- xiaohongshu-mcp: is Tag support added, and do tags cause send timeouts?
- Xiaohongshu account flagged while using xiaohongshu-mcp — how to avoid it?
- xiaohongshu-mcp: demo videos won't load, MCP Inspector session lost, MCP no response — fixes?
- Docker 中 xiaohongshu-mcp 出现大量 [chrome] 僵尸进程，PID 1 不回收怎么办？
- How do I reduce Xiaohongshu bans from xiaohongshu-mcp automated publishing? Does v2.1.1 add anti-detection?