Reeling MCP
Related Servers
Alternatives to Reeling MCP
No user-submitted related servers found.
Related Servers
- FlicenseAqualityBmaintenanceMCP server for LazyRelay: schedule posts, check analytics, and read mentions from any MCP-compatible AI agent. Local (stdio, API key) or hosted (OAuth, no install).27-
- FlicenseNot gradedqualityDmaintenanceMCP server for automatic Instagram publishing — single image, carousel and Reels — via the official Instagram Graph API.18 npm-
- AlicenseBqualityBmaintenanceMCP server for Instagram Graph API, Threads API & Meta platform — posting, insights, comments, messaging66225 npm30MIT
- AlicenseNot gradedqualityCmaintenanceSocial media API and MCP server for AI agents that enables publishing to X, Instagram, LinkedIn, Reddit, Bluesky, and Threads from a single endpoint.108 npmMIT
- AlicenseNot gradedqualityDmaintenanceOpen-source MCP server that routes tool calls to AdPanel's production gateway for brand asset management, timeline orchestration, and broadcast asset synthesis.01Apache 2.0
- AlicenseAqualityAmaintenanceEnables agents and scripts to drive a social publishing account through remote or local MCP tools: drafting, scheduling, approving and publishing posts, running durable background jobs with file attachments, and reading or editing Brand Memory, assets, and standing agents. Hosts can connect over OAuth with no API key, or run the stdio variant with a key for local disk tools.651MIT
TDQS
Scored across 18 tools
Each tool targets a distinct action or resource within the social media workflow. While several tools involve content creation (adapt_content_ai, draft_community_answer, generate_video, create_storyboard), their descriptions clearly differentiate the target platforms and output types, preventing confusion.
All tools are prefixed with 'reeling_' and use snake_case with a consistent verb_noun structure (e.g., reeling_get_platform_matrix, reeling_publish_post). The only variation is the inclusion of acronyms like JEV, but the pattern remains predictable.
18 tools is slightly above the ideal 3-15 range but is justified by the breadth of functionality (discovery, creation, publishing, analytics, engagement). No obvious redundant tools, though the set could be trimmed if some advanced features are rarely used.
Coverage is strong across the core lifecycle: platform discovery, content creation, publishing, analytics, and engagement. Minor gaps exist, such as no tools for updating/deleting posts or managing projects/channels beyond listing, but these are likely handled via the web interface and do not block core agent workflows.