Skip to main content
Glama
Eyalm321
by Eyalm321

Related Servers

Alternatives to zernio-mcp

No user-submitted related servers found.

    Related Servers

    • 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
    • A
      license
      Not graded
      quality
      D
      maintenance
      A comprehensive MCP server with 206+ tools across 16 integrations that gives Claude access to real accounts (LinkedIn, Twitter, Slack, Gmail, WhatsApp, etc.) by extracting auth tokens straight from your browser, no API keys or OAuth needed.
      8 npm
      3
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      An MCP server that integrates the Sprout Social Public API with Claude and other MCP clients. It allows users to manage social profiles, track analytics for posts and profiles, and schedule social media content.
      11
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      A production-ready Remote MCP Server that gives Claude direct, tool-based access to your Instagram Business account through the Meta Graph API — profile data, posts, comments, publishing, insights, analytics, hashtags, messaging, and real-time webhooks.
      7 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that exposes the full Social Champ tool catalog for scheduling and managing posts, channels, workspaces, labels, queues, and more through AI clients like Claude Desktop and Cursor.
      2
      MIT
    • F
      license
      A
      quality
      B
      maintenance
      Local MCP server for operating Instagram, Meta Ads, and Facebook Page from Claude Code via Meta's Graph API. Provides 20 tools for publishing, campaign management, and insights.
      20
      -

    TDQS

    C2.8/5.0

    Scored across 274 tools

    Disambiguation2/5

    Several tool clusters are nearly indistinguishable, such as get_account_health vs get_single_account_health, validate_post vs validate_post_content vs validate_post_length, and multiple upload_media variants. Platform-specific connect/select tools also blur boundaries (e.g., list_linkedin_organizations vs list_linkedin_organizations_for_connect). Descriptions help in some cases, but the overlap is frequent enough to cause misselection.

    Naming Consistency3/5

    The dominant verb_noun pattern is clear and mostly consistent (list_accounts, create_campaign, delete_webhook). However, there are notable exceptions: platform-first names like twitter_retweet and reddit_submit_post, inconsistent profile naming (list_profiles vs create_zernio_profile), and duplicated qualifiers like get_account_health vs get_single_account_health. Overall it is readable but mixes conventions.

    Tool Count1/5

    274 tools is an extreme count for any MCP server and far exceeds the 50+ threshold. This will overwhelm agent context windows and make reliable tool selection difficult. The server should be split into focused sub-servers by domain such as posts, messaging, ads, WhatsApp, and analytics.

    Completeness4/5

    The surface is remarkably comprehensive for a social media management platform, with CRUD-style coverage across accounts, posts, comments, DMs, analytics, ads, CRM, broadcasts, automations, sequences, webhooks, WhatsApp, and queue management. Minor gaps exist, such as no update_comment or update_review_reply, but agents can generally work around them with existing tools.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues