Posthive vs Markaestro
A side-by-side look at the Posthive and Markaestro MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Posthive for social media work over a hosted endpoint; choose Markaestro 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 Posthive when
- You need dedicated capabilities in the Social Media domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
- You have the keys it needs:
ENCRYPTION_KEY, JWT_ACCESS_TOKEN_SECRET, JWT_REFRESH_TOKEN_SECRET, DATABASE_URL, REDIS_URL.
Choose Markaestro when
- You need dedicated capabilities in the Social Media domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
MARKAESTRO_API_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Social Media | Social Media |
| Quality signal | 53/100 · Good | 39/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | OAuth 2.0 | Not declared |
| Pricing | Free | Not declared |
| Required env vars | ENCRYPTION_KEYJWT_ACCESS_TOKEN_SECRETJWT_REFRESH_TOKEN_SECRET |
Tools & capabilities
Posthive tools
No tool names declared yet. Check the project README from the listing page.
Markaestro 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.
Posthive
{
"mcpServers": {
"astablackclove-posthive": {
"url": "https://your-api/mcp"
}
}
}
Markaestro
{
"mcpServers": {
"markaestro": {
"command": "npx",
"args": [
"-y",
"@markaestro/mcp"
],
"env": {
"MARKAESTRO_API_KEY": "YOUR_MARKAESTRO_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Posthive is categorized under Social Media and uses a remote HTTP/SSE transport. Markaestro belongs to Social Media and uses a local stdio subprocess. Pick Posthive for social media work and Markaestro 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.
Posthive is listed as free. Auth: oauth 2.0. Markaestro 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 astablackclove-posthive and markaestro as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Posthive has a quality signal of 53/100 (Good) with 1 views, 0 installs and 16 GitHub stars. Markaestro has 39/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.