Skip to main content
Glama
pfarag

mixpost-mcp-server

by pfarag
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mixpost-mcp-server

No user-submitted related servers found.

    Related Servers

    • @posteahora/mcp by posteahora

      @posteahora/mcpofficial

      posteahora
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to create, schedule, and publish social media posts across Instagram, X/Twitter, LinkedIn, Threads, Facebook, and other platforms via the PosteAhora API.
      15
      13 npm
      MIT

    • RecurPost MCP Server

      dinwal
      A
      license
      A
      quality
      A
      maintenance
      Provides AI assistants with access to the RecurPost API to manage social media accounts, schedule posts, and organize content libraries. It enables users to automate recurring posts, track engagement metrics, and generate social media content through natural language.
      10
      409 npm
      1
      MIT

    • Sociona MCP Server

      fav-devs
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to publish, schedule, and manage social media posts across X (Twitter), Instagram, and Threads through the Sociona API. Supports immediate posting, scheduling, analytics, and account management with natural language commands.
      6
      15 npm
      MIT

    • Sprout Social MCP Server

      oliverames
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides full Sprout Social API coverage for AI-powered social media management, enabling analytics, inbox messages, listening, publishing, media uploads, and support cases through natural language.
      8 npm
      MIT
    • OwlStack MCP by owlstacks

      OwlStack MCPofficial

      owlstacks
      A
      license
      A
      quality
      C
      maintenance
      Manages social media posts, accounts, and AI usage from MCP-aware clients. Supports scheduling, editing, canceling, AI caption generation, and repurposing URLs into platform-optimized content.
      14
      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

    B3.3/5.0

    Scored across 20 tools

    Disambiguation4/5

    Most tools target distinct resource-action pairs (posts, tags, media, accounts). The only potential confusion is between mixpost_schedule_post and mixpost_add_post_to_queue, but their descriptions clarify the difference (specific time vs. queue placement). Overall, tool boundaries are clear.

    Naming Consistency5/5

    All tools follow a consistent mixpost_<verb>_<noun> pattern using snake_case and a common prefix. Verbs like list, get, create, update, delete are used uniformly across resources, making the API predictable and easy to navigate.

    Tool Count4/5

    With 20 tools, the server is slightly heavy but appropriate given the breadth of the domain (posts, media, tags, accounts). The tool count reflects the need for CRUD operations on multiple resources without becoming excessive or unwieldy.

    Completeness4/5

    The tool surface provides thorough coverage for posts (create, update, approve, schedule, queue, delete, bulk delete) and full CRUD for tags. Minor gaps exist, such as missing account management (creation/deletion) and media upload, but these are likely handled outside the MCP server scope.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources