RedNote Ops Suite
Related Servers
Alternatives to RedNote Ops Suite
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceEnables interaction with Xiaohongshu (Little Red Book) platform through automated browser operations. Supports authentication, content publishing, search, discovery, and commenting using Puppeteer-based automation.167 npm55MIT
- AlicenseNot gradedqualityDmaintenanceEnables automated interaction and data scraping for Xiaohongshu (RedNote), including posting, liking, commenting, following, and retrieving user and note data.5MIT
- FlicenseNot gradedqualityFmaintenanceEnables automated content publishing and management on Xiaohongshu (Little Red Book) platform, supporting image/video posts, content search, user profiles, and interactions through the Model Context Protocol.142-
- AlicenseNot gradedqualityCmaintenanceAn MCP server that enables controlled Xiaohongshu content publishing with an immutable review workflow, requiring explicit human confirmation before any release. It supports content generation, local editing, compliance recall, and one-time authorized posting, defaulting to generate-only mode.Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables automation of Xiaohongshu (Little Red Book) operations including content publishing, searching, and interacting, with MCP protocol support for AI agent integration.1MIT
- FlicenseBqualityDmaintenanceEnables automated interaction with Xiaohongshu (Little Red Book) social media platform through browser automation. Supports login management, status checking, and publishing text content with images to Xiaohongshu accounts.33-
TDQS
Scored across 13 tools
Each tool maps to a distinct action in the content lifecycle: drafting, reviewing, approving, packaging, publishing, and metrics. Even record_publication and record_metrics are clearly separated by their inputs (publication ID vs. metrics data). No two tools perform the same function.
The vast majority follow a consistent verb_noun pattern: save_draft, list_drafts, update_draft, cancel_draft, check_content, record_metrics. Minor deviations are safety_status and operations_summary, which are noun phrases rather than verb commands, but the overall pattern is predictable and readable.
13 tools is well-scoped for the server's purpose of managing a local draft-to-publication workflow. Each tool has a clear role, and the count feels appropriate for the domain without unnecessary bloat or missing critical steps.
The workflow is largely complete: create, read, update, cancel, submit, approve, package, record publication, and record metrics are all covered. The main gap is the lack of a reject_draft or request_changes action for reviewers, but cancel_draft partially covers this, and the rest of the lifecycle is solid.