A side-by-side look at the Dopost and Breakreach MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Dopost for social media work over a hosted endpoint; choose Breakreach 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 Dopost when
You need dedicated capabilities in the Social Media domain.
No tool names declared yet. Check the project README from the listing page.
Breakreach 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.
Dopost is categorized under Social Media and uses a remote HTTP/SSE transport. Breakreach belongs to Social Media and uses a local stdio subprocess. Pick Dopost for social media work and Breakreach 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.
Dopost has no declared pricing — check the project's own site. Breakreach 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 dopost and breakreach as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Dopost has a quality signal of 40/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Breakreach has 43/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.