XiaoHongShu guide is misleading for Docker flow: localhost root can 404 and login cookies are not auto-shared into MCP

[islandznfc]

Summary

The current XiaoHongShu setup guide in Agent Reach is misleading for the Docker flow.

What the current guide says

The guide currently tells the user:

• run Docker xiaohongshu-mcp
• open http://localhost:18060
• scan a QR code there
• cookies will then be saved automatically inside the Docker container

What I observed locally

On macOS arm64, with the current release flow:

1. Docker xiaohongshu-mcp was healthy on http://localhost:18060/mcp
2. GET / on http://localhost:18060 returned 404, not a login page
3. the successful login path came from the separate standalone binary xiaohongshu-login-darwin-arm64
4. that login tool wrote cookies.json to the host current working directory
5. the Docker MCP service still showed 未登录 until that host-side cookies.json was manually copied into the container as /app/cookies.json

So the current guide describes a much smoother Docker login flow than what actually happens in practice.

Why this matters

This creates a confusing setup experience:

• the user follows the documented Docker flow
• root page is 404
• standalone login may succeed
• Docker MCP still says not logged in

From an operator perspective it looks broken, even though the pieces are individually working.

Suggested fix

Please update the XiaoHongShu guide to reflect the real current behavior.
At minimum:

1. mention that http://localhost:18060/ may not be a QR login page
2. mention the standalone login binary path when applicable
3. document where cookies.json is written
4. document how Docker MCP should consume that cookie file

I also filed the corresponding upstream issue to xiaohongshu-mcp, but the Agent Reach guide itself is currently inaccurate enough to deserve its own doc fix.