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.8 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.143 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.11455 npm7MIT
- AlicenseAqualityCmaintenanceEnables Claude to list platform login status and rules, preview posts, and publish text, images, or video to X, LinkedIn, YouTube, Facebook Pages, Instagram, and TikTok from one MCP interface. Each post is validated against per-platform rules before publishing, which requires explicit confirmation.3MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to write social posts in a brand's voice for up to four platforms, schedule or cancel them, list brands and channels, and read results, all with human approval before anything is published. Connects via OAuth or API key so posts can be planned and managed from Claude, ChatGPT, Cursor, and other MCP clients.MIT
TDQS
Scored across 55 tools
The set has many clearly named tools, but several pairs overlap meaningfully: create_post vs schedule_post, update_post vs reschedule_post, list_comments vs list_inbox, and the various analytics getters. Descriptions mostly resolve the ambiguity, but with 55 tools an agent can still misselect without reading carefully.
Tool names consistently follow a snake_case verb_noun pattern, such as list_posts, create_comment, delete_media, and update_team. Minor variations like get_post_csv_import and reply_to_inbox_item still fit the same convention.
At 55 tools, the surface is very heavy for one server, even for a broad social-media management domain. Many workflows are split across numerous narrow tools, making discovery and selection more burdensome than necessary.
Coverage is broad: accounts, posts, comments, media, analytics, teams, CSV imports, inbox, and clipping all have core lifecycle operations. There are some minor gaps, such as cancellation/deletion for clipping and CSV import jobs, but most primary workflows are covered.