In-depth architectural comparison of the Socialclaw 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
Socialclaw
Social Media · Local stdio
Quality: 47/100 (Fair) | Auth: No auth required
TikTok Trends MCP
Social Media · Remote HTTP/SSE
Quality: 49/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Socialclaw if you need specialized Social Media tools running via a local process. 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 Socialclaw when:
You need dedicated capabilities in the Social Media domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: SOCIALCLAW_API_KEY.
Primary tools included: 17 validation-first MCP tools, Multi-platform account and capability discovery, Media upload and schedule management.
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).
Socialclaw is categorized under Social Media and uses a local stdio subprocess. In contrast, TikTok Trends MCP belongs to Social Media using remote streaming HTTP/SSE transport. Select Socialclaw 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).