A side-by-side look at the Postey and PostOnce MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Postey for social media work; choose PostOnce for social media over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
P
Choose Postey when
You need dedicated capabilities in the Social Media domain.
No tool names declared yet. Check the project README from the listing page.
PostOnce tools
No tool names declared yet. Check the project README from the listing page.
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.
Postey
No confirmed install command for Postey yet — follow the setup steps linked from its listing page rather than a guessed package name.
Postey is categorized under Social Media and uses an install path we have not confirmed yet. PostOnce belongs to Social Media and uses a remote HTTP/SSE transport. Pick Postey for social media work and PostOnce 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. Postey has no confirmed install command yet — follow its own setup instructions.
Postey has no declared pricing — check the project's own site. PostOnce has no declared pricing — check the project's own site. 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 postey and postonce as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Postey has a quality signal of 37/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. PostOnce has 42/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.