postbuzz-mcp
Related Servers
Alternatives to postbuzz-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables generating, scheduling, and publishing social media posts via Claude or an agent through the MCP protocol.15 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to post, schedule, thread, delete, and analyze social media posts across platforms like X, Bluesky, LinkedIn, and Instagram through a single MCP interface.2,215 npmMIT
- AlicenseNot gradedqualityAmaintenanceSchedule and analyze social media posts from Claude, ChatGPT, or Cursor. Remote OAuth server, 17 tools across 9 platforms, free on every plan. Server URL: https://socialrobot.io/api/mcpMIT
- AlicenseAqualityBmaintenanceSchedule 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.111,381 npm6MIT

@crmsolid/mcp-serverofficial
AlicenseNot gradedqualityBmaintenanceEnables AI assistants to manage social DM inboxes and posting calendars across 12 platforms, allowing users to triage messages, draft replies, schedule posts, and pull stats from MCP clients.37 npm5MIT
socialchamp-mcpofficial
AlicenseNot gradedqualityCmaintenanceMCP 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.2MIT
TDQS
Scored across 51 tools
Most tools follow a clear resource+action boundary (posts, comments, media, accounts, teams), and list/get pairs are standard CRUD distinctions. A few ambiguities remain—update_post can also move a schedule, making reschedule_post somewhat redundant, and there are several overlapping analytics retrieval tools—but descriptions generally keep them apart.
All 51 tools use a consistent snake_case verb_noun pattern, e.g. list_posts, create_post, delete_comment, refresh_account. Compound resources are also uniformly prefixed (post_csv_import), so the naming convention is highly predictable.
51 tools is far beyond the 25+ threshold and creates a heavy selection burden for an agent, even though the tools are grouped by domain. The breadth may be justified for a full social media platform, but as an MCP surface it is over-scoped and several convenience tools (delete_media_many, analytics variants, per-account tools) could be consolidated.
The server provides solid lifecycle coverage for posts, scheduled comments, media, accounts, teams, analytics, and CSV imports, including retries and bulk operations. Minor gaps exist—inbox actions are limited to reply/edit, published posts cannot be deleted/unpublished, and organization settings are read-only—but core workflows have no dead ends.