Socialclaw vs Markaestro
A side-by-side look at the Socialclaw 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 Socialclaw for social media work as a local process; 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 Socialclaw when
- You need dedicated capabilities in the Social Media domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
SOCIALCLAW_API_KEY.
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 | 48/100 · Fair | 43/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | SOCIALCLAW_API_KEY | MARKAESTRO_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 97 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Socialclaw | View Markaestro |
Tools & capabilities
Socialclaw 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.
Socialclaw
{
"mcpServers": {
"socialclaw": {
"command": "npx",
"args": [
"-y",
"socialclaw"
],
"env": {
"SOCIALCLAW_API_KEY": "YOUR_SOCIALCLAW_API_KEY_HERE"
}
}
}
}
Markaestro
{
"mcpServers": {
"markaestro": {
"command": "npx",
"args": [
"-y",
"@markaestro/mcp"
],
"env": {
"MARKAESTRO_API_KEY": "YOUR_MARKAESTRO_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Socialclaw is categorized under Social Media and uses a local stdio subprocess. Markaestro belongs to Social Media and uses a local stdio subprocess. Pick Socialclaw 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.
Socialclaw has no declared pricing — check the project's own site. 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 socialclaw and markaestro as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Socialclaw has a quality signal of 48/100 (Fair) with 2 views, 0 installs and 97 GitHub stars. Markaestro has 43/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.