Performance Review vs Wenyan MCP
A side-by-side look at the Performance Review and Wenyan MCP 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 Wenyan MCP for social media over a hosted endpoint. 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 Wenyan MCP when
- You need dedicated capabilities in the Social Media domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: other.
- You have the keys it needs:
WECHAT_APP_ID, WECHAT_APP_SECRET.
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) | Remote HTTP/SSE |
| Auth | Not declared | other |
| Pricing | Not declared | Free |
| Required env vars | None listed | WECHAT_APP_IDWECHAT_APP_SECRET |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 1,344 |
| Directory activity | 2 views 0 installs 0 upvotes | 6 views 0 installs 0 upvotes |
| Tools | 1 | Not listed |
| Full listing | View Performance Review | View Wenyan MCP |
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.
Wenyan MCP 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"
]
}
}
}
Wenyan MCP
{
"mcpServers": {
"caol64-wenyan-mcp": {
"url": "https://api.example.com"
}
}
}
Frequently asked questions
Performance Review is categorized under Social Media and uses a local stdio subprocess. Wenyan MCP belongs to Social Media and uses a remote HTTP/SSE transport. Pick Performance Review for social media work and Wenyan MCP 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. Wenyan MCP is listed as free. Auth: other. 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 caol64-wenyan-mcp 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. Wenyan MCP has 44/100 (Fair) with 6 views, 0 installs and 1,344 GitHub stars.