Wenyan MCP vs TikTok Trends MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Wenyan MCP vs TikTok Trends MCP
In-depth architectural comparison of the Wenyan MCP and TikTok Trends MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Wenyan MCP
Social Media · Remote HTTP/SSE
Quality: 47/100 (Fair) | Auth: other
TikTok Trends MCP
Social Media · Remote HTTP/SSE
Quality: 51/100 (Good) | Auth: No auth required
Verdict Summary: Choose Wenyan MCP if you need specialized Social Media tools running via a hosted cloud SSE transport. Choose TikTok Trends MCP if your workspace requires Social Media integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Wenyan MCP when:
You need dedicated capabilities in the Social Media domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: other (Free / Open Source).
You have access to required keys: WECHAT_APP_ID, WECHAT_APP_SECRET.
Primary tools included: Markdown-to-WeChat rich-text rendering, Built-in and custom formatting themes, Local and remote image uploads.
Weekly (or daily) history for **one** `source` + `keyword`. Same name on MCP and REST (`mode: "get_time_series"`). REST also accepts `get_trends` as an alias.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Wenyan MCP is categorized under Social Media and uses a remote streaming HTTP/SSE transport. In contrast, TikTok Trends MCP belongs to Social Media using remote streaming HTTP/SSE transport. Select Wenyan MCP when you need capabilities focused on social media and TikTok Trends MCP when you require tools for social media.
Point-to-point percent change. Several windows in one call still count as **one** request for that source + keyword.
get_top_trends
Live ranked list. **No keyword.** On MCP, `type` is required and must match the feed name **exactly** (including capitals). On REST, omit `type` only if you intend to pull every feed (billed per feed).