PikoReels MCP
Related Servers
Alternatives to PikoReels MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables MCP clients such as Claude, Cursor, and ChatGPT to use Clip Studio's creative tools—including Video Lab, Topic Shorts, Talking Shorts, Ad Studio, Image Lab, Audio Lab, Story, and Ad Lab—under the same signed-in account and plan, with OAuth authentication and paid generation allowance.1MIT

Ads Optimiser MCP serverofficial
AlicenseAqualityBmaintenanceLets Claude Desktop, Claude Code, or any MCP client generate ad images and videos from chat, including batches from folders of local files, prompt lists, and pipelines. Sign-in uses an OAuth device flow with workspace-scoped, revocable tokens, and finished creatives can be saved back to your machine.1641 npmMIT- AlicenseAqualityBmaintenanceEnables MCP clients like Claude to access a user's Medium account, including Following and For you feeds, full member-only posts, search, reading lists, and managing follows, saves, and claps after a one-time browser login.14MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to securely connect to a personal HEY account through OAuth and perform scoped email, search, contact, calendar, todo, thread, and sending operations.MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to operate Google Flow through a visible browser, supporting login, project tracking, reference upload, generation submission, and media download with local validation.99 npm7MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to exchange an MCP-audience token for a Microsoft Graph token and call Graph as the signed-in user, with tools for identity verification and recent mail access.MIT
TDQS
Scored across 47 tools
Most tools target a distinct resource+action, and descriptions go out of their way to delineate boundaries (e.g. get_dashboard vs get_analytics vs get_post_analytics, and schedule_rush_lineup vs create_automation). A few analytics/post-reading tools overlap in intent but the descriptions disambiguate them. No true duplicates.
Nearly every tool follows a clean verb_noun snake_case pattern (list_slideshows, generate_image, get_video_job, create_automation, publish_automation). The vocabulary is even semantically consistent, using list_/get_/create_/update_/delete_/schedule_/publish_ in predictable ways. No mixed conventions.
47 tools is heavy and pushes well past the comfortable 3-15 range, so the surface is daunting and increases selection cost. However the server genuinely spans many distinct sub-domains (workspaces, brand, social accounts, analytics, library, image/video/slideshow generation, scheduling, automations, rush), so each tool roughly earns its place rather than being redundant.
Coverage is broad and lifecycle-complete for the core domain: full CRUD on workspaces, automations and library media; generate/get/list/delete for videos and images; schedule, reschedule, cancel and publish for posts. Minor gaps exist (e.g. no update/delete for slideshows, brand exposed only via get_brand/update_brand_voice) but agents can work around them.