| Ecosystem | 0 | 0 |
| Match Graph | 0 | 0 |
| Pricing | Free | Free |
| Capabilities | 14 decomposed | 14 decomposed |
| Times Matched | 0 | 0 |
Exposes Xiaohongshu social platform capabilities as a set of 13 standardized MCP tools consumable by AI clients (Claude, Cursor, Gemini CLI, Cline, VSCode). The service implements the Model Context Protocol specification on a /mcp endpoint with streamable HTTP transport, translating MCP tool calls into internal service method invocations. Each tool is registered in mcp_server.go with JSON schema definitions and dispatched through mcp_handlers.go to the underlying XiaohongshuService layer.
Unique: Implements full MCP protocol stack in Go with dual interface design (MCP + REST API on same port 18060), allowing both MCP clients and direct HTTP consumers to invoke the same underlying service methods without code duplication. Uses go-rod/rod for browser automation rather than direct API calls because Xiaohongshu lacks a public API.
vs alternatives: First open-source MCP server for Xiaohongshu with 12k+ GitHub stars; competitors either use REST-only APIs or require proprietary integrations, whereas this exposes the full platform through standardized MCP tooling.
Implements a two-phase authentication system: xiaohongshu-login binary handles interactive QR code scanning via headless Chrome, persisting authenticated session cookies to cookies.json; the main xiaohongshu-mcp service reads these cookies on startup and injects them into every subsequent browser session opened via go-rod/rod. This approach bypasses the need for API credentials by reusing the user's authenticated browser context across all platform operations.
Unique: Separates authentication (xiaohongshu-login) from service operation (xiaohongshu-mcp) into two distinct binaries, allowing one-time interactive login followed by unattended service execution. Uses go-rod/rod for headless Chrome automation rather than Selenium or Puppeteer, providing tighter Go integration and lower memory overhead.
vs alternatives: Avoids credential storage entirely by leveraging browser session cookies; competitors using direct API calls require API keys or OAuth tokens, which introduce credential management overhead and security risk.
Manages headless Chrome browser instances through go-rod/rod, implementing session pooling to reuse browser contexts across multiple operations. The service opens a browser instance on startup, injects authenticated cookies into each session, and reuses the browser for subsequent tool invocations. Browser lifecycle is tied to the service lifecycle — the browser is closed when the service shuts down. This approach reduces startup latency compared to opening a new browser for each operation.
Unique: Uses go-rod/rod for browser automation with session pooling, reusing browser instances across multiple operations to reduce startup latency. Injects authenticated cookies into each session, maintaining authentication state without re-authenticating for each operation.
vs alternatives: Browser pooling reduces latency compared to spawning new browsers for each operation; go-rod/rod provides tighter Go integration and lower memory overhead compared to Selenium or Puppeteer.
Extracts post metadata, user information, and engagement metrics by parsing the Xiaohongshu DOM through go-rod/rod's element selection and text extraction APIs. The service uses CSS selectors and XPath queries to locate elements, extract text content, and construct structured data objects. This approach enables operation without reverse-engineering proprietary APIs, but is brittle to HTML structure changes.
Unique: Uses go-rod/rod for DOM parsing and element selection, providing a Go-native approach to web scraping without external dependencies like BeautifulSoup or Cheerio. Extracts structured data directly from the live Xiaohongshu web interface, enabling operation without API reverse-engineering.
vs alternatives: DOM-based extraction works against the live platform without API maintenance; competitors using outdated or reverse-engineered APIs may break when Xiaohongshu updates its backend.
Implements consistent error handling and response serialization across MCP and REST interfaces. The service layer returns structured error objects with error codes, messages, and optional context; mcp_handlers.go and handlers_api.go translate these into protocol-specific responses (MCP error format or HTTP status codes). This design ensures that clients receive consistent error information regardless of which interface they use.
Unique: Implements error handling at the service layer with protocol-agnostic error types, allowing mcp_handlers.go and handlers_api.go to translate errors into protocol-specific formats. This design ensures consistent error semantics across MCP and REST interfaces.
vs alternatives: Centralized error handling reduces code duplication and ensures consistency; competitors with separate error handling paths for each protocol may have inconsistent error messages or codes.
Implements a stateless HTTP server (using Gin framework) where each MCP or REST request opens a fresh browser page/tab within the pooled browser instance, executes the operation, and closes the page. This approach isolates state between requests, preventing cross-request contamination while reusing the browser instance for performance. The server maintains no per-request state — all context is passed through request parameters.
Unique: Implements per-request browser page isolation within a pooled browser instance, balancing performance (reusing browser) with isolation (fresh page per request). Stateless HTTP server design enables horizontal scaling without session affinity or distributed state management.
vs alternatives: Per-request page isolation prevents cross-request state leakage compared to competitors that reuse the same page across multiple requests; stateless design enables horizontal scaling without session management overhead.
Provides two distinct publishing tools: publish_content for text-based posts with optional image attachments, and publish_with_video for video content. Both tools operate through browser automation, constructing the Xiaohongshu post creation form via DOM manipulation and submitting it through the live web interface. The service handles image/video file uploads, caption composition, and hashtag injection before form submission.
Unique: Implements publish_content and publish_with_video as separate MCP tools with distinct parameter schemas, allowing AI clients to choose the appropriate tool based on content type. Uses DOM-based form construction and submission rather than API calls, enabling operation against the live Xiaohongshu web interface without reverse-engineering proprietary APIs.
vs alternatives: Supports both text and video publishing through a single service, whereas most Xiaohongshu automation tools focus only on text; browser automation approach works against the live platform without requiring API maintenance as Xiaohongshu's web UI evolves.
Implements get_feed tool that retrieves the authenticated user's Xiaohongshu feed with cursor-based pagination. The service navigates the feed DOM, extracts post metadata (title, author, engagement metrics, timestamps), and returns paginated results. Cursor tokens encode the position in the feed, enabling clients to request subsequent pages without re-fetching earlier content.
Unique: Uses cursor-based pagination (opaque tokens) rather than offset-based pagination, reducing the risk of duplicate or skipped results when the feed is updated between requests. Extracts feed data via DOM parsing rather than API calls, making it resilient to Xiaohongshu's lack of a public feed API.
vs alternatives: Cursor-based pagination is more robust than offset-based approaches for dynamic feeds; competitors using offset pagination risk returning duplicate posts if new content is inserted during pagination.
+6 more capabilities
Converts natural language application descriptions into executable database schemas by parsing user intent through an LLM pipeline, inferring entity relationships, cardinality, and data types without manual schema definition. The system likely uses prompt engineering to constrain schema generation to Bubble's supported data model, then validates and materializes schemas in Bubble's backend database layer.
Unique: Integrates LLM-driven schema inference directly into Bubble's visual database builder, allowing non-technical users to generate normalized schemas through conversational prompts rather than manual table/field creation or SQL DDL statements
vs alternatives: Faster than traditional database design tools (Lucidchart, dbdiagram.io) for non-technical users because it eliminates the need to learn ER diagram syntax or database normalization rules
Translates natural language descriptions of application workflows (user actions, conditional logic, data transformations, multi-step processes) into executable Bubble workflows without requiring visual workflow builder expertise. The system maps user intent to Bubble's workflow primitives (actions, conditions, loops, API calls) through LLM-guided code generation, then validates and deploys workflows to Bubble's serverless execution layer.
Unique: Generates complete workflow definitions including conditional branching, loops, and API calls from natural language, mapping user intent to Bubble's visual workflow primitives without requiring users to interact with the workflow builder UI
vs alternatives: More accessible than Zapier or Make for complex multi-step workflows because it generates logic from natural language rather than requiring users to manually chain actions and configure conditions through a visual interface
Bubble AI scores higher at 71/100 vs xiaohongshu-mcp at 34/100. xiaohongshu-mcp leads on ecosystem, while Bubble AI is stronger on adoption and quality.
Need something different?
Search the match graph →© 2026 Unfragile. Stronger through disorder.
Automatically generates data entry forms with built-in validation rules, error messages, and user feedback mechanisms inferred from the database schema and workflow requirements. The system maps schema field types and constraints to appropriate form inputs (text fields, dropdowns, date pickers, etc.), generates validation rules, and creates error handling workflows that provide users with clear feedback on submission failures.
Unique: Automatically generates form components with validation rules and error handling inferred from database schema constraints and workflow requirements, eliminating manual form configuration and validation logic implementation
vs alternatives: Simpler than manual form development in traditional frameworks because it automatically generates validation rules from schema constraints, whereas traditional development requires explicit validation configuration in form code
Automatically generates user authentication systems (signup, login, password reset) and role-based access control (RBAC) workflows based on natural language descriptions of user types and permissions. The system infers authentication requirements from application descriptions, generates secure authentication flows, and creates authorization rules that restrict access to features and data based on user roles.
Unique: Automatically generates complete authentication and authorization systems including signup, login, password reset, and role-based access control from natural language descriptions, eliminating manual implementation of security-critical authentication logic
vs alternatives: More secure than manual authentication implementation for non-technical users because it uses Bubble's built-in security features, whereas manual implementation is prone to security vulnerabilities (weak password hashing, SQL injection, etc.)
Automatically generates reports and data export functionality that allows users to export application data in standard formats (CSV, PDF, Excel) and view summarized data through generated dashboards and charts. The system infers reporting requirements from the application schema and workflows, generates report templates, and creates export workflows that transform application data into user-friendly formats.
Unique: Automatically generates reports, dashboards, and data export workflows from natural language descriptions, inferring aggregations and visualizations from application schema without requiring manual report design or data transformation logic
vs alternatives: Faster than manual report development in traditional BI tools (Tableau, Power BI) because it automatically generates reports from application data, whereas traditional BI tools require separate data modeling and report configuration
Enables multiple users to collaborate on application development through shared editing of generated applications, with real-time synchronization of changes and conflict resolution. The system maintains a shared application state that updates in real-time as team members make modifications through the visual editor or natural language prompts, allowing teams to build applications collaboratively without version control complexity.
Unique: Provides real-time collaborative editing of generated applications with automatic synchronization across team members, eliminating version control complexity and merge conflict management required in traditional development
vs alternatives: Simpler than traditional collaborative development (Git, GitHub) for non-technical teams because it provides real-time synchronization without version control concepts, whereas traditional development requires understanding branching, merging, and conflict resolution
Automatically generates responsive web UI components (pages, forms, tables, navigation, layouts) from natural language descriptions of application screens and user interactions. The system infers component hierarchy, styling, and responsive breakpoints through LLM analysis, then materializes components in Bubble's visual design system with built-in mobile responsiveness and accessibility features.
Unique: Generates complete responsive UI layouts from natural language by inferring component hierarchy, spacing, and breakpoints, then materializes them in Bubble's visual design system with automatic mobile responsiveness rather than requiring manual component placement and styling
vs alternatives: Faster than traditional UI design tools (Figma, Adobe XD) for non-technical users because it eliminates design tool learning curve and automatically handles responsive breakpoints, whereas design tools require manual layout work for each breakpoint
Orchestrates end-to-end application generation by coordinating database schema creation, workflow generation, and UI component generation from a single natural language application description. The system decomposes user intent into sub-tasks (data modeling, business logic, interface design), executes each through specialized LLM pipelines, then integrates outputs into a cohesive, deployable application with pre-configured data bindings and workflow triggers.
Unique: Coordinates multi-stage LLM-driven generation (schema → workflows → UI) from a single prompt, automatically integrating outputs with data bindings and event triggers, eliminating the need for users to manually connect database to business logic to UI
vs alternatives: Dramatically faster than traditional full-stack development (weeks to months) because it generates database, backend logic, and frontend UI simultaneously from natural language, whereas traditional development requires sequential phases of design, implementation, and integration
+6 more capabilities