DataLikers vs TikTok Trends MCP
A side-by-side look at the DataLikers and TikTok Trends MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose DataLikers for social media work as a local process; choose TikTok Trends 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 DataLikers when
- You need dedicated capabilities in the Social Media domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
DATALIKERS_API_KEY, DATALIKERS_URL.
Choose TikTok Trends MCP when
- You need dedicated capabilities in the Social Media domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
TRENDSMCP_API_KEY. - You want tools like
get_time_series, get_growth, get_top_trends.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Social Media | Social Media |
| Quality signal | 40/100 · Fair | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | API key required | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | DATALIKERS_API_KEYDATALIKERS_URL |
Tools & capabilities
DataLikers tools
No tool names declared yet. Check the project README from the listing page.
TikTok Trends MCP tools 3
get_time_seriesWeekly (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.get_growthPoint-to-point percent change. Several windows in one call still count as **one** request for that source + keyword.get_top_trendsLive 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).
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.
DataLikers
{
"mcpServers": {
"datalikers": {
"command": "npx",
"args": [
"-y",
"datalikers-mcp"
],
"env": {
"DATALIKERS_API_KEY": "YOUR_DATALIKERS_API_KEY_HERE",
"DATALIKERS_URL": "YOUR_DATALIKERS_URL_HERE"
}
}
}
}
TikTok Trends MCP
{
"mcpServers": {
"tiktok-trends-mcp": {
"url": "https://api.trendsmcp.ai/mcp"
}
}
}
Frequently asked questions
DataLikers is categorized under Social Media and uses a local stdio subprocess. TikTok Trends MCP belongs to Social Media and uses a remote HTTP/SSE transport. Pick DataLikers for social media work and TikTok Trends 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.
DataLikers has no declared pricing — check the project's own site. Auth: api key required. TikTok Trends MCP 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 datalikers and tiktok-trends-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, DataLikers has a quality signal of 40/100 (Fair) with 0 views, 0 installs and 9 GitHub stars. TikTok Trends MCP has 49/100 (Fair) with 1 views, 0 installs and 1 GitHub stars.
