Enterprise social suites solve real problems — client separation, permissions, audit — and charge for a great deal you may not use. PostMCP AI keeps those three, drops the listening and inbox surface, and adds an AI agent plus a full API.
A workspace is a wall, not a tag. Each one holds its own connected accounts, brand kits, calendar, members, API keys and activity log. A freelancer invited into one client’s workspace has no route to another — not a hidden tab, not an API call. Business plans allow ten workspaces on one bill.
Owner, Admin, Scheduler and Visitor, with ranks. Nobody can act on a member at or above their own rank, and only the Owner outranks everyone. That is the difference between a permission list and an actual permission model.
Sign in, connect an account through its official OAuth screen, queue a post. No procurement, no implementation call, no seat negotiation before you can find out whether the tool suits you.
Credits are spent when a post reaches a profile — 1 per delivery, 5 for X, plus a 50-credit surcharge on posts with a link. Adding a read-only stakeholder to a workspace does not change what you pay to publish.
No unified inbox, no social listening stream, no engagement queue, no downstream analytics dashboard. PostMCP publishes and schedules. If a unified inbox is the feature holding your team together, a full suite is the honest answer and you should stay on one.
This page states what PostMCP AI does. Other products change their plans and feature sets often — read their current documentation and decide on your own comparison.