Performance Review vs InsightSocial
A side-by-side look at the Performance Review and InsightSocial MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Performance Review for social media work as a local process; choose InsightSocial 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 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.
Choose InsightSocial when
- You need dedicated capabilities in the Social Media domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
INSIGHTSOCIAL_API_KEY, INSIGHTSOCIAL_BASE_URL, INSIGHTSOCIAL_HOME.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Social Media | Social Media |
| Quality signal | 57/100 · Good | 44/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 | None listed | INSIGHTSOCIAL_API_KEYINSIGHTSOCIAL_BASE_URLINSIGHTSOCIAL_HOME |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 1 | Not listed |
| Full listing | View Performance Review | View InsightSocial |
Tools & capabilities
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.
InsightSocial 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.
Performance Review
{
"mcpServers": {
"performance-review": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-performance-review"
]
}
}
}
InsightSocial
{
"mcpServers": {
"insightsocial": {
"command": "npx",
"args": [
"-y",
"insightsocial"
],
"env": {
"INSIGHTSOCIAL_API_KEY": "YOUR_INSIGHTSOCIAL_API_KEY_HERE",
"INSIGHTSOCIAL_BASE_URL": "YOUR_INSIGHTSOCIAL_BASE_URL_HERE",
"INSIGHTSOCIAL_HOME": "YOUR_INSIGHTSOCIAL_HOME_HERE"
}
}
}
}
Frequently asked questions
Performance Review is categorized under Social Media and uses a local stdio subprocess. InsightSocial belongs to Social Media and uses a local stdio subprocess. Pick Performance Review for social media work and InsightSocial 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.
Performance Review has no declared pricing — check the project's own site. InsightSocial 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 performance-review and insightsocial as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Performance Review has a quality signal of 57/100 (Good) with 2 views, 0 installs and 0 GitHub stars. InsightSocial has 44/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.