Skip to main content
Glama
owlstacks

OwlStack MCP

Official
by owlstacks
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to OwlStack MCP

No user-submitted related servers found.

    Related Servers

    • social0-mcp

      Abhishek-B-R
      A
      license
      A
      quality
      B
      maintenance
      MCP server to manage social media accounts from AI assistants, enabling post creation, scheduling, publishing, and media uploads across multiple platforms.
      13
      41 npm
      1
      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

    • so-easy-mcp

      Pantalones411
      A
      license
      Not graded
      quality
      C
      maintenance
      A full social media management MCP server enabling post, read, schedule, and analyze across Facebook, Instagram, LinkedIn, X/Twitter, Pinterest, and YouTube from any MCP-compatible AI client.
      MIT

    • seenpaid

      justinasrolando-cpu
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to schedule and manage social media posts across 25 platforms via a simple 3-tool MCP interface, including listing connected accounts and recent posts.
      AGPL 3.0
    • Solnk MCP by solnk-dev

      Solnk MCPofficial

      solnk-dev
      A
      license
      A
      quality
      D
      maintenance
      Enables publishing and scheduling content across 9 social platforms (X, Instagram, TikTok, YouTube, Facebook, LinkedIn, Pinterest, Threads, Bluesky) through a single MCP tool interface, acting as a stateless proxy to the Solnk API.
      11
      1
      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

    A4/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action. Post operations are split clearly (get, list, schedule, edit, cancel, delete, delivery), account tools are separate, and AI tools have distinct purposes (caption generation, platform rewriting, URL repurposing). The minimal overlap between get_post and list_post_deliveries is acceptable since the latter provides per-account detail.

    Naming Consistency5/5

    All tools follow a consistent verb_noun snake_case pattern (e.g., list_posts, schedule_post, get_account_health). Even multi-word actions like repurpose_url and rewrite_for_platforms maintain the structure. No mixing of casing or verb styles.

    Tool Count5/5

    14 tools is well within the ideal range and each tool earns its place. The count covers post CRUD, delivery, accounts, workspaces, and AI features without feeling bloated or sparse for the domain.

    Completeness4/5

    The core content scheduling lifecycle is fully covered: create, read, update, cancel, delete, and track delivery. Account management is read-only plus health checks, which is sufficient for the stated purpose. Minor gaps like no single-workspace getter or account update tool exist, but they are not critical for typical workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources