zernio-mcp
Related Servers
Alternatives to zernio-mcp
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityBmaintenanceEnables Claude or any MCP client to schedule and publish social media posts across 15 platforms, write brand-voice captions, create branded graphics, and manage media and workspaces through a hosted remote server.1MIT- AlicenseNot gradedqualityCmaintenanceA 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
- AlicenseNot gradedqualityDmaintenanceA 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.26 npm3MIT
- AlicenseCqualityBmaintenanceEnables posting, scheduling, and analyzing social media content across 16+ platforms through MCP clients like Claude Desktop, Claude Code, and Cursor.55146 npmMIT
- FlicenseAqualityDmaintenanceAn 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-
- AlicenseAqualityCmaintenanceA read-only MCP server that lets Claude query your own Threads, itch.io, YouTube, and X accounts through official APIs, returning recent posts, per-post stats, replies and mentions, and account totals. It also supports saving daily snapshots so week-to-week comparisons can be made, and it never posts, replies, likes, or deletes anything.51MIT
TDQS
Scored across 274 tools
Many tools have near-identical purposes: get_account_health vs get_single_account_health, validate_post_content vs validate_post vs validate_post_length, and three separate media upload tools (upload_media, upload_media_direct, upload_media_from_file). Profile handling is especially confusing (get_profile, list_profiles, get_zernio_profile, create_zernio_profile) and the connect-time list_*_for_connect tools shadow the regular get_* variants for the same platforms.
Most tools follow a zernio_verb_noun snake_case pattern, which is broadly readable. However, it's mixed with platform-first ordering (zernio_reddit_submit_post, zernio_twitter_retweet) versus verb-first (zernio_connect_bluesky, zernio_get_reddit_flairs), and some resources are inconsistently prefixed (create_zernio_profile vs list_profiles).
274 tools is an extreme mismatch for any coherent tool set and far beyond what an agent can reliably select from. Whole sub-domains (WhatsApp, GMB, ads, analytics) each contribute dozens of tools, causing massive surface-area overload.
Coverage of the sprawling domain is genuinely deep—CRM, messaging, WhatsApp Business, ads, analytics, GMB, and moderation all have create/read/update/delete coverage. Minor gaps exist (e.g., no delete_campaign, only campaign status updates) but most workflows are covered end to end.