Antwork vs Postfast MCP — MCP Server Comparison | AllMCPs
Antwork vs Postfast MCP
A side-by-side look at the Antwork and Postfast MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Antwork for social media work over a hosted endpoint; choose Postfast MCP for social media as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Antwork when
You need dedicated capabilities in the Social Media domain.
No tool names declared yet. Check the project README from the listing page.
Postfast MCP tools 25
list_accountsList connected social media accounts (each with `connectionStatus` — `CONNECTED`/`DISABLED` — `disabledReason`, `followerCount`/`followerCountUpdatedAt`, and `inboxCapable`)
list_postsList posts with filters (specific IDs, accounts, platform, status, date range); each post carries its key settings in `controls` (Threads topic, Instagram/Facebook format, TikTok draft flag, YouTube privacy)
create_postsCreate and schedule posts (batch, up to 15)
delete_postDelete a post from PostFast by ID (does not remove an already-published post from the platform)
delete_postsDelete up to 100 posts from PostFast in one call; returns `deletedIds` and `notFoundIds` (does not remove already-published posts from the platform)
upload_mediaUpload a local file and get a media key (handles the full flow)
get_upload_urlsGet signed URLs to upload media files
list_pinterest_boardsGet Pinterest boards for an account
list_youtube_playlistsGet YouTube playlists for an account
list_gbp_locationsGet Google Business Profile locations for an account
search_placesFind a place to tag posts (the `id` works for both `facebookPlaceId` and `instagramLocationId`)
generate_connect_linkGenerate a link for clients to connect accounts — optionally scoped to specific platforms, with a `redirectUrl` the user returns to (carrying `status`, `platform`, `accountId` and your own `externalId`, plus `accountIds` after a Facebook or LinkedIn page step)
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Antwork is categorized under Social Media and uses a remote HTTP/SSE transport. Postfast MCP belongs to Social Media and uses a local stdio subprocess. Pick Antwork for social media work and Postfast MCP for social media.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Antwork has no declared pricing — check the project's own site. Postfast MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: other. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add antwork-2 and peturgeorgievv-factory-postfast-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Antwork has a quality signal of 40/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Postfast MCP has 64/100 (Good) with 4 views, 0 installs and 6 GitHub stars.