Adside vs Markaestro
A side-by-side look at the Adside 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 Adside for social media work; 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 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 | A Adside | |
|---|---|---|
| Category | Social Media | Social Media |
| Quality signal | 37/100 · Fair | 43/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | MARKAESTRO_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Adside | View Markaestro |
Tools & capabilities
Adside 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.
Adside
No confirmed install command for Adside yet — follow the setup steps linked from its listing page rather than a guessed package name.
Markaestro
{
"mcpServers": {
"markaestro": {
"command": "npx",
"args": [
"-y",
"@markaestro/mcp"
],
"env": {
"MARKAESTRO_API_KEY": "YOUR_MARKAESTRO_API_KEY_HERE"
}
}
}
}