Trends Hub is an MCP server that aggregates global trending content from 20+ high-quality data sources and exposes it through the Model Context Protocol. It is designed to be drop-in compatible with MCP clients, offering a unified endpoint to fetch current trends and related metadata. The server supports configurable return fields via environment variables, allowing you to tailor the response payload to your AI apps or chat clients. Tools available include a variety of get_... endpoints (e.g., get_36kr_trending, get_nytimes_news, get_toutiao_trending, get_weibo_trending, get_zhihu_trending, and more) that fetch latest items from each source and normalize them into MCP-compatible responses.

Prerequisites:

• Node.js 22 or newer installed on your system
• npm (comes with Node.js) or npm/yarn available in your environment

Installation steps:

1. Verify Node.js version: node -v

   should show v22.x.x or newer

2. Install or run via npx (no global install required): npx -y mcp-trends-hub

3. (Optional) If you prefer a local install in a project, you can install as a dev dependency: npm install --save-dev mcp-trends-hub

   then run with npx or a script, e.g. npx mcp-trends-hub

4. Configure via mcpServers block as shown in the mcp_config below, and set any environment variables as needed:

   • TRENDS_HUB_HIDDEN_FIELDS: comma-separated fields to hide
   • TRENDS_HUB_CUSTOM_RSS_URL: comma-separated custom RSS URLs to add

5. Start using the MCP client of your choice (Claude Desktop, Cursor, Windsurf, VS Code MCP extension, etc.) with the standard configuration example provided in the README.

Tips and notes:

• The server is designed to work with MCP clients using the standard npx configuration, which makes deployment quick and stateless for many environments.
• You can customize returned fields using TRENDS_HUB_HIDDEN_FIELDS and add extra RSS sources via TRENDS_HUB_CUSTOM_RSS_URL. Ensure correct formatting (comma-separated values) and unique tool-name prefixes when customizing.
• If you run into network or source outages, the MCP layer will attempt to surface available sources and maintain recent items; consider enabling verbose logs or debugging in your client to diagnose failures.
• When using environments, avoid placing sensitive keys directly in the config unless required; prefer runtime environment management of secrets where supported.