Skip to main content
Glama
AhmadElsaeedd

ReelFarm MCP Server

by AhmadElsaeedd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to ReelFarm MCP Server

No user-submitted related servers found.

    Related Servers

    • spoooler

      4nw3rprod
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables local-first Instagram reel production entirely over MCP, turning raw footage, URLs, or topics into finished reels with script generation, stock media, voiceover, and captions.
      2
      MIT
    • tokportal-mcp by tokportal

      tokportal-mcpofficial

      tokportal
      A
      license
      C
      quality
      C
      maintenance
      Enables AI agents to manage real TikTok, Instagram, and YouTube accounts via a REST API and MCP server, allowing for account creation, content publishing, warming, and analytics without OAuth or daily post limits.
      91
      MIT

    • postfast-mcp

      peturgeorgievv-factory
      A
      license
      A
      quality
      B
      maintenance
      Schedule and manage social media posts across 10 platforms (Instagram, Facebook, TikTok, X, LinkedIn, YouTube, Threads, Pinterest, Bluesky, Telegram) from any MCP-compatible AI assistant. Supports batch posting, media uploads, analytics, and platform-specific features like Reels, Shorts, and carousels.
      11
      393 npm
      5
      MIT

    • socialgpt-mcp

      scrollmark
      A
      license
      Not graded
      quality
      B
      maintenance
      Brings social media analytics and content intelligence into any MCP-compatible AI agent, enabling analysis of your own videos, competitor research, and creator discovery via a hosted OAuth-authenticated server.
      10
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 26 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose, and even near-overlapping pairs like generate_slideshow vs. create_slideshow or publish_video_via_automation vs. publish_to_tiktok are explicitly differentiated by AI/manual control and automation vs. direct publication. The descriptions eliminate ambiguity.

    Naming Consistency4/5

    The naming is overwhelmingly consistent: verb_noun snake_case (list_automations, get_video, publish_to_tiktok). The only deviation is slideshow_status, which is a noun_noun format, but all other tools follow the pattern, making this a minor inconsistency.

    Tool Count3/5

    With 26 tools, the server is on the heavier end. The broad domain of automation, slideshow generation, video management, and TikTok publishing justifies many tools, but some redundancy (e.g., delete_schedule duplicates update_schedule's batch delete) makes it feel slightly over-scoped.

    Completeness3/5

    Automation and schedule CRUD are well covered, and the creation-to-publishing pipeline works. However, there are no delete or update operations for videos or slideshows, and collections lack any management tools beyond listing. These gaps prevent full lifecycle management for generated content.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources