setlog-mcp
Related Servers
Alternatives to setlog-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables MCP clients to browse Velog posts, safely create drafts and private posts, validate Markdown, and maintain a local searchable Markdown archive.914 npmMIT
- AlicenseNot gradedqualityBmaintenanceLocal stdio MCP tools for timestamped video search and opt-in, recoverable FFmpeg editing jobs. Requires a separately running ReelPilot API for media and execution; default discovery is read-only.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to manage multiple named YouTube accounts through one local stdio server, covering video upload and scheduling, metadata, captions, playlists, comments, live broadcasts and chat, channel branding, and analytics reporting via the official Google APIs. It also offers optional FFmpeg-based local media tools for probing, muxing audio, normalizing loudness, trimming, burning subtitles, and extracting thumbnails.MIT
- AlicenseAqualityBmaintenanceEnables multi-account posting, replying, threading, deletes and image/GIF/video uploads through the official X API v2, plus likes, reposts, bookmarks, follows, timelines, search, DMs, Lists and trends. It runs locally over stdio so OAuth tokens and refresh stay on the user's own machine.2431 npmMIT

@reelspan/mcpofficial
AlicenseNot gradedqualityBmaintenanceEnables MCP clients such as Claude, Cursor, and Windsurf to publish videos, photos, and text to 22 social networks, schedule or cancel posts, and review analytics and post history through a local stdio bridge to a hosted endpoint. Supports read-only and tool-filtering modes for restricted, reporting-only use.448 npmMIT- AlicenseAqualityCmaintenanceEnables local video inspection and offline transcription with timestamped JSON and Markdown output, enforced filesystem boundaries, and reproducible content-addressed caching.2MIT
TDQS
Scored across 17 tools
Most tools target clearly different steps of the posting lifecycle (login, key transfer, prepare, send, schedule, list), but the pair send_prepared_video vs send_prepared_videos differs only by plurality and will be easy to misselect, and prepare_video vs prepare_video_batch overlap for a single item. list_posts vs search_posts_by_date and get_status vs get_profile are distinguishable only by careful reading of the descriptions.
All names follow a snake_case verb_noun pattern (get_profile, list_collections, prepare_video, schedule_videos, cancel_scheduled_post), which is highly predictable. Minor deviations: prepare_video_batch uses a trailing qualifier rather than a batch_ prefix, and the singular/plural send pair makes the naming itself a source of confusion.
17 tools across several legitimate sub-areas (email login, key transfer, profile/status, collections, prepare, send, schedule, history) so each roughly earns its place. It is on the heavy side, and a handful of tools (single vs batch prepare, single vs multi send) exist only to save round trips rather than to cover new capability.
The core lifecycle is well covered: authenticate, transfer an existing key, list destinations, prepare (single or batch), send, schedule, cancel, verify, and read history/scheduled state. Gaps are minor: no way to discard or inspect an unspent prepared job, no post deletion or edit, and no key revocation/logout despite key transfer being supported.