xhs-mcp-docker

Publish 小红书 content via MCP HTTP API with Dockerized Chromium and QR login.

2|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/MushroomDAO/blog --skill xhs-mcp-docker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: xhs-mcp-docker
Source: https://github.com/MushroomDAO/blog/tree/main/.agents/skills/xhs-mcp-docker
Command: npx skills add https://github.com/MushroomDAO/blog --skill xhs-mcp-docker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of publishing to 小红书 without relying on a pre-logged local Chrome profile, by providing a containerized MCP service that supports fresh QR-code login and persistent cookies.

Core Features & Use Cases

  • QR Code Login in a Dockerized Chromium Session: Obtain a QR code from the MCP server, scan it with your phone, and have the service confirm login status for subsequent publishing.
  • Persistent Session via Cookie Volumes: Save authentication cookies to a mounted host directory so you can restart the container without re-scanning.
  • Image-Aware Publishing Pipeline: Publish content while referencing images that are mounted into the container data directory, enabling end-to-end media submission.
  • Remote Access via Tailscale Proxy (Optional): Expose the local-only service safely to remote clients inside your tailnet.

Real-world use case: You deploy to a new machine or CI-like environment where you cannot reuse a logged-in browser profile, and you still need reliable 小红书 publishing with media uploads after a one-time QR login.

Quick Start

Start the MCP Docker service on your host (via its provided start script), fetch and scan the QR code, then call the publish endpoint with your title, content, tags, and image paths under the mounted data directory.

Frequently Asked Questions about xhs-mcp-docker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I publish to 小红书 in a Docker environment without a pre-logged browser profile?

You can publish to 小红书 in a Docker environment by using a containerized headless Chromium session that supports fresh QR-code login and persistent cookie storage volumes. This enables media publishing workflows without relying on a local browser profile.

Can I persist 小红书 login sessions across Docker container restarts?

Yes, you can persist 小红书 login sessions across container restarts by mounting a host directory to store authentication cookies. This cookie volume approach ensures you do not need to re-scan the QR code after every container restart.

How does QR code login work with headless Chromium for 小红书 automation?

QR code login works with headless Chromium by fetching a QR code from the MCP HTTP server for you to scan with your phone. The service then polls the login status endpoint to confirm authentication for subsequent automated publishing.

Do I need to mount images into the Docker container to publish media to 小红书?

Yes, you need to mount images into the container data directory for 小红书 media publishing. The image-aware publishing pipeline references file paths under this mounted directory to enable end-to-end media submission.

Can I expose the local 小红书 MCP service for remote access?

Yes, you can expose the local 小红书 MCP service for remote access safely by using a Tailscale proxy. This allows remote clients inside your tailnet to reach the HTTP endpoints for login, status polling, and publish actions.

What are the limitations of using a containerized headless Chromium session for 小红书 publishing?

A limitation of using a containerized headless Chromium session for 小红书 publishing is the initial requirement to perform a one-time QR code login scan via phone. Additionally, proper host volume mounting is required for both cookie persistence and image data access.