X Twitter MCP server
{
"mcpServers": {
"trendsmcp-x-twitter": {
"type": "http",
"url": "https://x-twitter.api.trendsmcp.ai/mcp"
}
}
}{
"mcpServers": {
"trendsmcp-x-twitter": {
"type": "http",
"url": "https://x-twitter.api.trendsmcp.ai/mcp"
}
}
}{
"mcpServers": {
"trendsmcp-x-twitter": {
"type": "http",
"url": "https://x-twitter.api.trendsmcp.ai/mcp"
}
}
}{
"servers": {
"trendsmcp-x-twitter": {
"type": "http",
"url": "https://x-twitter.api.trendsmcp.ai/mcp"
}
}
}{
"mcpServers": {
"trendsmcp-x-twitter": {
"type": "http",
"url": "https://x-twitter.api.trendsmcp.ai/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 1.0.6
What it does
Trends MCP provides access to trending keywords and time-series trend data across 30+ platforms including Google, TikTok, YouTube, Amazon, and Reddit. It is for developers building AI agents that need current trend information normalized across multiple sources.
- Retrieve what keywords are currently trending on a specific platform like Google or TikTok without writing platform-specific scrapers.
- Compare growth rates for a keyword across multiple sources over different time windows (7 days to 5 years) in a single request.
- Track historical search or interest volume for a keyword on a specific platform to identify patterns and changes over time.
Tools this server exposes
| Tool | Does |
|---|---|
| get_time_series | Retrieve historical trend data for a keyword on a specified source, normalized to a 0-100 scale. |
| get_growth | Calculate percent change for a keyword across multiple time windows (7 days to 5 years) on specified sources. |
| get_top_trends | Fetch the currently trending keywords ranking on a specified platform. |
This entry comes from the registry but points to no public repository, so there is nothing to check: no commit history, no source, no tool list. It is listed for completeness and left out of search engines.
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.