T
trendsmcp-ai/TrendWatch
📈 Free trend-monitoring & breakout alerts that run in your own GitHub repo
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
- Star count
- 6 ★ · trendsmcp-ai/TrendWatch · read from the GitHub search API · (checked 2026-11-13 20:00:50)
- Source
- read directly from its GitHub page · type: open-source project
- Harvest history
- first seen 2026-11-12 · last seen 2026-11-14 · seen 3× · listed by 1 sources
- Score
- score 103 · 6 ★ · 1 sources · repo
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: 开源项目. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
trendsmcp-ai/TrendWatch;first catalogued 2026-11-12;last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.# 📈 TrendWatch
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
### Get pinged the moment a topic starts blowing up - Google, TikTok, YouTube, Reddit, Amazon & more.
Free. Runs in your own GitHub repo. No server, no scraping, no API keys to juggle.
Fork it → add one free key → pick your keywords → GitHub Actions watches the trends and DMs you when something breaks out.
Alerts to:
Data by · works with any MCP client (Claude, Cursor…)
### 📊 Live trends - updated 2026-11-11 19:58 UTC
_All quiet - no watchlist breakouts in the latest run._
Auto-updated by TrendWatch · powered by Trends MCP
## Why TrendWatch?
You want to know when "your brand", a competitor, or a whole category starts trending - before everyone else does. The usual options are bad:
🧱 Building a scraper → breaks every time Google changes its HTML, needs a server, gets you rate-limited/blocked.
💸 Enterprise trend tools → $100s/month, overkill, locked behind sales calls.
👀 Checking Google Trends by hand → you forget, you miss the spike, you're late.
TrendWatch is the lazy, reliable middle path: a tiny open-source job that runs on GitHub's free Actions runners, calls the Trends MCP API for clean normalized data, and pings you in Slack / Discord / Telegram / email the instant something moves.
your keywords Trends MCP API you, notified
┌────────────────────┐ ┌──────────────────────┐ ┌──────────────────┐
│ "your brand" │ │ Google · TikTok · │ │ 📈 Slack │
│ "competitor" │──▶│ YouTube · Reddit · │──▶│ 💬 Discord │
│ "labubu" │ │ Amazon · Wikipedia… │ │ ✈️ Telegram │
└────────────────────┘ └──────────────────────┘ │ ✉️ Email / Webhook│
config.yml (1 clean API call) └──────────────────┘
GitHub Actions runs this on a schedule - for free.
## ⚡ 60-second setup
1. Click "Use this template" → create your own copy of this repo.
2. Grab a free API key (100 requests/month, no credit card).
3. In your repo: Settings → Secrets and variables → Actions → New repository secret
Name: TRENDS_API_KEY · Value: (your key)
4. Edit config.yml - add the keywords you care about.
5. Go to the Actions tab, enable workflows, and hit Run workflow to test it.
That's it. It now runs on a schedule and alerts you. 🎉
> Want desktop/phone alerts? Add any of SLACK_WEBHOOK_URL, DISCORD_WEBHOOK_URL, TELEGRAM_BOT_TOKEN + TELEGRAM_CHAT_ID, or SMTP secrets. With none set, it still logs to the Actions console and updates your README dashboard.
## 🎯 What it detects
Watchlist breakouts - your keywords, measured for momentum.
> 🚀 labubu is breaking out on google search: +212% over 7D (1M +140%, 3M +320%)
Breakouts land in your alert channels, get written to reports/ as dated Markdown, and refresh the live dashboard at the top of this README.
## 🔔 Notification channels
| Channel | Secrets to add | How to get it |
| Slack | SLACK_WEBHOOK_URL | Slack incoming webhooks |
| Discord | DISCORD_WEBHOOK_URL | Channel → Edit → Integrations → Webhooks |
| Telegram | TELEGRAM_BOT_TOKEN, TELEGRAM_CHAT_ID | @BotFather → new bot |
| Email | SMTP_HOST, SMTP_PORT, SMTP_USER, SMTP_PASS, SMTP_TO | Any SMTP (Gmail app password, Fastmail…) |
| Anything else | GENERIC_WEBHOOK_URL | Zapier / Make / n8n / your own endpoint |
Set one, several, or none - each activates only when its secret is present.
Free. Runs in your own GitHub repo. No server, no scraping, no API keys to juggle.
Fork it → add one free key → pick your keywords → GitHub Actions watches the trends and DMs you when something breaks out.
Alerts to:
Data by · works with any MCP client (Claude, Cursor…)
### 📊 Live trends - updated 2026-11-11 19:58 UTC
_All quiet - no watchlist breakouts in the latest run._
Auto-updated by TrendWatch · powered by Trends MCP
## Why TrendWatch?
You want to know when "your brand", a competitor, or a whole category starts trending - before everyone else does. The usual options are bad:
🧱 Building a scraper → breaks every time Google changes its HTML, needs a server, gets you rate-limited/blocked.
💸 Enterprise trend tools → $100s/month, overkill, locked behind sales calls.
👀 Checking Google Trends by hand → you forget, you miss the spike, you're late.
TrendWatch is the lazy, reliable middle path: a tiny open-source job that runs on GitHub's free Actions runners, calls the Trends MCP API for clean normalized data, and pings you in Slack / Discord / Telegram / email the instant something moves.
your keywords Trends MCP API you, notified
┌────────────────────┐ ┌──────────────────────┐ ┌──────────────────┐
│ "your brand" │ │ Google · TikTok · │ │ 📈 Slack │
│ "competitor" │──▶│ YouTube · Reddit · │──▶│ 💬 Discord │
│ "labubu" │ │ Amazon · Wikipedia… │ │ ✈️ Telegram │
└────────────────────┘ └──────────────────────┘ │ ✉️ Email / Webhook│
config.yml (1 clean API call) └──────────────────┘
GitHub Actions runs this on a schedule - for free.
## ⚡ 60-second setup
1. Click "Use this template" → create your own copy of this repo.
2. Grab a free API key (100 requests/month, no credit card).
3. In your repo: Settings → Secrets and variables → Actions → New repository secret
Name: TRENDS_API_KEY · Value: (your key)
4. Edit config.yml - add the keywords you care about.
5. Go to the Actions tab, enable workflows, and hit Run workflow to test it.
That's it. It now runs on a schedule and alerts you. 🎉
> Want desktop/phone alerts? Add any of SLACK_WEBHOOK_URL, DISCORD_WEBHOOK_URL, TELEGRAM_BOT_TOKEN + TELEGRAM_CHAT_ID, or SMTP secrets. With none set, it still logs to the Actions console and updates your README dashboard.
## 🎯 What it detects
Watchlist breakouts - your keywords, measured for momentum.
> 🚀 labubu is breaking out on google search: +212% over 7D (1M +140%, 3M +320%)
Breakouts land in your alert channels, get written to reports/ as dated Markdown, and refresh the live dashboard at the top of this README.
## 🔔 Notification channels
| Channel | Secrets to add | How to get it |
| Slack | SLACK_WEBHOOK_URL | Slack incoming webhooks |
| Discord | DISCORD_WEBHOOK_URL | Channel → Edit → Integrations → Webhooks |
| Telegram | TELEGRAM_BOT_TOKEN, TELEGRAM_CHAT_ID | @BotFather → new bot |
| Email | SMTP_HOST, SMTP_PORT, SMTP_USER, SMTP_PASS, SMTP_TO | Any SMTP (Gmail app password, Fastmail…) |
| Anything else | GENERIC_WEBHOOK_URL | Zapier / Make / n8n / your own endpoint |
Set one, several, or none - each activates only when its secret is present.
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/trendsmcp-ai-trendwatch/)
- Source
- github · https://github.com/trendsmcp-ai/TrendWatch
- Browse by field
- Open source
- Traction
- 6 ★
- added
- today
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.