TikTok Trends MCP vs X Twitter Scraper
A side-by-side look at the TikTok Trends MCP and X Twitter Scraper MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose TikTok Trends MCP for social media work over a hosted endpoint; choose X Twitter Scraper 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 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.
Choose X Twitter Scraper 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:
XQUIK_API_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Social Media | Social Media |
| Quality signal | 49/100 · Fair | 63/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Paid service |
| Required env vars | TRENDSMCP_API_KEY | XQUIK_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 218 |
| Directory activity | 1 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | 3 | Not listed |
| Full listing | View TikTok Trends MCP | View X Twitter Scraper |
Tools & capabilities
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).
X Twitter Scraper 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.
TikTok Trends MCP
{
"mcpServers": {
"tiktok-trends-mcp": {
"url": "https://api.trendsmcp.ai/mcp"
}
}
}
X Twitter Scraper
{
"mcpServers": {
"xquik-dev-x-twitter-scraper": {
"command": "bunx",
"args": [
"shadcn@4.18.0"
],
"env": {
"XQUIK_API_KEY": "YOUR_XQUIK_API_KEY_HERE"
}
}
}
}
Frequently asked questions
TikTok Trends MCP is categorized under Social Media and uses a remote HTTP/SSE transport. X Twitter Scraper belongs to Social Media and uses a local stdio subprocess. Pick TikTok Trends MCP for social media work and X Twitter Scraper 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.
TikTok Trends MCP has no declared pricing — check the project's own site. X Twitter Scraper is listed as a paid service. Auth: api key required. 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 tiktok-trends-mcp and xquik-dev-x-twitter-scraper as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, TikTok Trends MCP has a quality signal of 49/100 (Fair) with 1 views, 0 installs and 1 GitHub stars. X Twitter Scraper has 63/100 (Good) with 4 views, 0 installs and 218 GitHub stars.