rednote-gate
Related Servers
Alternatives to rednote-gate
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceA lightweight MCP server that lets AI assistants publish notes to Xiaohongshu (Little Red Book) via browser automation. Supports login, image-text note publishing with up to 9 images, and search.41-
- AlicenseAqualityDmaintenanceMCP server enabling AI assistants to search, analyze, and generate content for Xiaohongshu (RedNote), China's leading lifestyle social media platform.69MIT
- AlicenseNot gradedqualityCmaintenanceThis self-hosted MCP server enables users to read public Xiaohongshu and Douyin content, including post text, images, video frames, and optional audio transcription, from compatible Streamable HTTP MCP clients like Claude and ChatGPT.MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for Xiaohongshu (xiaohongshu.com) enabling login, note/video publishing, search, recommendations, and comment management via CLI or MCP protocol.1MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for automating Xiaohongshu (RED Note). Publish posts, search content, comment, like, and analyze creator data on China's largest lifestyle social platform.19 PyPI31MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that lets ChatGPT or any MCP client securely delegate coding tasks to a local Claude Code instance, with git checkpointing, approval gates, and structured results. Supports code review, test running, and rollback via simple tool calls.7 npmMIT
TDQS
Scored across 15 tools
Most tools target a clearly distinct resource+action (search vs get_note vs my_notes, post_comment vs reply_comment). The main source of overlap is create_post vs create_draft vs create_video_post, but the descriptions clarify the photo/draft/video distinctions. An agent can reliably pick the right tool.
All tools share the rednote_ prefix and use snake_case, with a mostly predictable verb_noun pattern (get_note, create_post, reply_comment). Minor deviation: status tools are noun-first (login_status, queue_status, my_notes), but this reads consistently as a status/list category.
15 tools is well within the ideal range and each one earns its place across read, queued-write, approval, and support operations. No redundant or filler tools are present.
Covers the core lifecycle: login check, search, read note/comments, own-note listing, and queued publish/draft/video/like/comment/reply with a human-approval flow and card rendering. A few gaps exist (no unfollow/delete/update note, no user-profile or notification reads), but core workflows are workable.