Markaestro vs Performance Review
A side-by-side look at the Markaestro and Performance Review MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Markaestro for social media work as a local process; choose Performance Review 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.
Choose Performance Review when
- You need dedicated capabilities in the Social Media domain.
- You prefer a local stdio subprocess transport.
- You want tools like
performance_review_generate.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Social Media | Social Media |
| Quality signal | 43/100 · Fair | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | MARKAESTRO_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | 1 |
| Full listing | View Markaestro | View Performance Review |
Tools & capabilities
Markaestro tools
No tool names declared yet. Check the project README from the listing page.
Performance Review tools 1
performance_review_generateGenerate a satirical corporate performance review for an employee; takes employee_name, role, rating (rockstar/solid/developing/not_a_culture_fit), actual_performance, and what_manager_wants_to_say — returns review text that communicates nothing clearly.
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.
Markaestro
{
"mcpServers": {
"markaestro": {
"command": "npx",
"args": [
"-y",
"@markaestro/mcp"
],
"env": {
"MARKAESTRO_API_KEY": "YOUR_MARKAESTRO_API_KEY_HERE"
}
}
}
}
Performance Review
{
"mcpServers": {
"performance-review": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-performance-review"
]
}
}
}
Frequently asked questions
Markaestro is categorized under Social Media and uses a local stdio subprocess. Performance Review belongs to Social Media and uses a local stdio subprocess. Pick Markaestro for social media work and Performance Review 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.
Markaestro has no declared pricing — check the project's own site. Performance Review 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 markaestro and performance-review as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Markaestro has a quality signal of 43/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Performance Review has 57/100 (Good) with 2 views, 0 installs and 0 GitHub stars.