Wenyan MCP vs PlanVortex
A side-by-side look at the Wenyan MCP and PlanVortex MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Wenyan MCP for social media work over a hosted endpoint; choose PlanVortex 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 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.
Choose PlanVortex when
- You need dedicated capabilities in the Social Media domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
PLANVORTEX_CLIENT_ID, PLANVORTEX_CLIENT_SECRET, PLANVORTEX_ORGANIZATION_ID, PLANVORTEX_MCP_ALLOW_AI, PLANVORTEX_MCP_READ_ONLY, PLANVORTEX_MCP_AUTH_TOKEN, PLANVORTEX_MCP_UPLOAD_DIRS.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Social Media | Social Media |
| Quality signal | 44/100 · Fair | 43/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | other | Not declared |
| Pricing | Free | Not declared |
| Required env vars | WECHAT_APP_IDWECHAT_APP_SECRET | PLANVORTEX_CLIENT_IDPLANVORTEX_CLIENT_SECRETPLANVORTEX_ORGANIZATION_IDPLANVORTEX_MCP_ALLOW_AIPLANVORTEX_MCP_READ_ONLYPLANVORTEX_MCP_AUTH_TOKENPLANVORTEX_MCP_UPLOAD_DIRS |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1,347 | 0 |
| Directory activity | 6 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Wenyan MCP | View PlanVortex |
Tools & capabilities
Wenyan MCP tools
No tool names declared yet. Check the project README from the listing page.
PlanVortex 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.
Wenyan MCP
{
"mcpServers": {
"caol64-wenyan-mcp": {
"url": "https://api.example.com"
}
}
}
PlanVortex
{
"mcpServers": {
"planvortex": {
"command": "npx",
"args": [
"-y",
"planvortex-mcp"
],
"env": {
"PLANVORTEX_CLIENT_ID": "YOUR_PLANVORTEX_CLIENT_ID_HERE",
"PLANVORTEX_CLIENT_SECRET": "YOUR_PLANVORTEX_CLIENT_SECRET_HERE",
"PLANVORTEX_ORGANIZATION_ID": "YOUR_PLANVORTEX_ORGANIZATION_ID_HERE",
"PLANVORTEX_MCP_ALLOW_AI": "YOUR_PLANVORTEX_MCP_ALLOW_AI_HERE",
"PLANVORTEX_MCP_READ_ONLY": "YOUR_PLANVORTEX_MCP_READ_ONLY_HERE",
"PLANVORTEX_MCP_AUTH_TOKEN": "YOUR_PLANVORTEX_MCP_AUTH_TOKEN_HERE",
"PLANVORTEX_MCP_UPLOAD_DIRS": "YOUR_PLANVORTEX_MCP_UPLOAD_DIRS_HERE"
}
}
}
}
Frequently asked questions
Wenyan MCP is categorized under Social Media and uses a remote HTTP/SSE transport. PlanVortex belongs to Social Media and uses a local stdio subprocess. Pick Wenyan MCP for social media work and PlanVortex 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.
Wenyan MCP is listed as free. Auth: other. PlanVortex 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 caol64-wenyan-mcp and planvortex as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Wenyan MCP has a quality signal of 44/100 (Fair) with 6 views, 0 installs and 1,347 GitHub stars. PlanVortex has 43/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.