trip-mcp
Related Servers
Alternatives to trip-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceAutomates video and image-text publishing on Douyin's creator platform using Chrome DevTools Protocol, exposed as MCP tools.84AGPL 3.0
- 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-
- FlicenseNot gradedqualityDmaintenanceAutomates the Douyin Creator Platform to manage login states and publish image-text content via the MCP protocol. It enables users to check authentication status, manage cookies, and automate article publishing with titles, text, and images.-
- AlicenseNot gradedqualityDmaintenanceEnables automation of Xiaohongshu (Little Red Book) operations including content publishing, searching, and interacting, with MCP protocol support for AI agent integration.1MIT
- FlicenseBqualityBmaintenanceEnables MCP clients to drive browser automation for web navigation, element interaction, and multi-account isolation via DrissionPage 5.0.56-
- FlicenseCqualityDmaintenanceEnables browser automation, including navigation, form filling, login with CAPTCHA handling, and element manipulation, using a Chrome-based MCP server.364-
TDQS
Scored across 10 tools
Each tool has a distinct purpose: login (open_login/check_login), browsing (list_notes/get_note), and the publishing workflow (search_destinations, prepare_note, publish_note, get_publish_status, cancel_prepared_note) are clearly separated. The only mild overlap is the standard list-vs-detail pairing of list_notes/get_note, which the descriptions disambiguate well.
All ten tools follow a consistent snake_case verb_noun pattern (get_capabilities, open_login, check_login, list_notes, get_note, search_destinations, prepare_note, publish_note, get_publish_status, cancel_prepared_note). No mixed conventions or vague standalone verbs.
Ten tools is well-scoped for a travel-note platform: a small auth/browse set plus a complete staged publishing flow. No redundant or filler tools appear.
The surface covers login, note discovery, and a careful prepare/publish/status/cancel lifecycle, which is strong. Minor gaps remain (no update or delete of already-published notes, no comment/social-interaction tools), but core workflows are fully supported.