Removing a post from the platforms names the networks it covers and states which ones it cannot reach; comments can be hidden on some networks and liked on only one; message editing is Telegram-only, reactions are Meta-only, chat archiving is Bluesky-only. Two timing rules are worth planning around rather than discovering: a scheduled post can only be updated while it is still comfortably ahead of its publish time, and a Meta private reply is one per comment, ever. The stats are equally plain about their resolution — profile snapshots are roughly daily, and the fields inside them are platform-native rather than normalised.
A multi-network social publishing and inbox client: profiles and profile groups, posts with scheduling and queues, comment moderation, Google Business reviews, direct messages, and per-post and per-profile stats. An interactive setup command registers it for you if you would rather not edit config by hand.
- Publishing with the network differences handled on the call: post_publish takes content, media, a schedule, a draft flag, threads for X and Threads, and a platforms parameter for per-network customisation.
- A post lifecycle rather than a fire-and-forget send — post_status, post_publish_draft, post_update, and two different deletes: post_delete removes it from the database, post_delete_on_platform removes it from the networks and leaves the record.
- summary_get answers "what is the status?" in one call — posts published and failed, engagement, comments and reviews awaiting reply, DM chats waiting, all for a window — instead of three separate listings.
- Queues that do the scheduling for you: queues_create defines recurring weekly timeslots with a timezone, queues_update rearranges everything already queued when the timeslots or timezone change, and queues_next_slot reports the next opening.
- Profiles organised into groups per brand or client, with profile_groups_initialize_connection returning the URL that starts the connect flow, and profiles_placements listing what a profile can actually post to — Facebook business pages, LinkedIn organizations, Pinterest boards, Telegram channels.
- Comment moderation on published posts: list, get, create, delete, hide, unhide, like and unlike, each naming the networks it works on.
- Google Business reviews as their own surface, because a review lives on a location rather than a post — profile_comments_list, profile_comments_get, profile_comments_create for replies only, and profile_comments_delete, which removes your reply and not the review.
- Direct messages: dm_chats_list, dm_chat_create, dm_messages_list, dm_message_send taking either a body or a single media attachment, dm_message_get, dm_message_edit, dm_message_react and dm_message_unreact, plus dm_chat_archive and dm_chat_unarchive.
- dm_comment_private_reply sends a DM to the author of a comment in reply to that comment, creating or reusing a chat automatically.
- Measurement: post_stats returns every snapshot in a timespan so a trend is visible rather than a single figure, and profiles_stats returns the follower and engagement timeseries as daily snapshots.
- upload_create returns a temporary upload URL with a key and an expiry, for sandboxed environments that cannot host a file themselves.
A Postproxy account and its API key in POSTPROXY_API_KEY, with POSTPROXY_BASE_URL pointing at the API. A social profile connected into a profile group before anything can be posted — the connect tool returns the URL the user opens to finish it, with Bluesky taking an identifier and an app password and Telegram taking a bot token. A placement id where the network has one: profile stats require it for Facebook, LinkedIn and Telegram, and Telegram and Pinterest posts fail without one.
One command plus a key — npm install -g postproxy-mcp, then supply credentials