Trend Finder

Stay on top of trending topics on social media and the web with AI

Installation

Installing for Claude Desktop

Manual Configuration Required

This MCP server requires manual configuration. Run the command below to open your configuration file:

npx mcpbar@latest edit -c claude

This will open your configuration file where you can add the Trend Finder MCP server manually.

Trend Finder πŸ”¦

Stay on top of trending topics on social media β€” all in one place.

Trend Finder collects and analyzes posts from key influencers, then sends a Slack or Discord notification when it detects new trends or product launches. This has been a complete game-changer for the Firecrawl marketing team by:

  • Saving time normally spent manually searching social channels
  • Keeping you informed of relevant, real-time conversations
  • Enabling rapid response to new opportunities or emerging industry shifts

Spend less time hunting for trends and more time creating impactful campaigns.

Watch the Demo & Tutorial video

Thumbnail

Learn how to set up Trend Finder and start monitoring trends in this video!

How it Works

  1. Data Collection πŸ“₯

    • Monitors selected influencers' posts on Twitter/X using the X API (Warning: the X API free plan is rate limited to only monitor 1 X account every 15 min)
    • Monitors websites for new releases and news with Firecrawl's /extract
    • Runs on a scheduled basis using cron jobs
  2. AI Analysis 🧠

    • Processes collected content through Together AI
    • Identifies emerging trends, releases, and news.
    • Analyzes sentiment and relevance
  3. Notification System πŸ“’

    • When significant trends are detected, sends Slack or Discord notifications based on cron job setup
    • Provides context about the trend and its sources
    • Enables quick response to emerging opportunities

Features

  • πŸ€– AI-powered trend analysis using Together AI
  • πŸ“± Social media monitoring (Twitter/X integration)
  • πŸ” Website monitoring with Firecrawl
  • πŸ’¬ Instant Slack or Discord notifications
  • ⏱️ Scheduled monitoring using cron jobs

Prerequisites

  • Node.js (v14 or higher)
  • npm or yarn
  • Docker
  • Docker Compose
  • Slack workspace with webhook permissions
  • API keys for required services

Environment Variables

Copy .env.example to .env and configure the following variables:

# Optional: API key from Together AI for trend analysis (https://www.together.ai/)
TOGETHER_API_KEY=your_together_api_key_here

# Optional: API key from DeepSeek for trend analysis (https://deepseek.com/)
DEEPSEEK_API_KEY=

# Optional: API key from OpenAI for trend analysis (https://openai.com/)
OPENAI_API_KEY=

# Required if monitoring web pages (https://www.firecrawl.dev/)
FIRECRAWL_API_KEY=your_firecrawl_api_key_here

# Required if monitoring Twitter/X trends (https://developer.x.com/)
X_API_BEARER_TOKEN=your_twitter_api_bearer_token_here

# Notification driver. Supported drivers: "slack", "discord"
NOTIFICATION_DRIVER=discord

# Required (if NOTIFICATION_DRIVER is "slack"): Incoming Webhook URL from Slack for notifications
SLACK_WEBHOOK_URL=https://hooks.slack.com/services/YOUR/WEBHOOK/URL

# Required (if NOTIFICATION_DRIVER is "discord"): Incoming Webhook URL from Discord for notifications
DISCORD_WEBHOOK_URL=https://discord.com/api/webhooks/WEBHOOK/URL

Getting Started

  1. Clone the repository:

    git clone [repository-url]
    cd trend-finder
    
  2. Install dependencies:

    npm install
    
  3. Configure environment variables:

    cp .env.example .env
    # Edit .env with your configuration
    
  4. Run the application:

    # Development mode with hot reloading
    npm run start
    
    # Build for production
    npm run build
    

Using Docker

  1. Build the Docker image:

    docker build -t trend-finder .
    
  2. Run the Docker container:

    docker run -d -p 3000:3000 --env-file .env trend-finder
    

Using Docker Compose

  1. Start the application with Docker Compose:

    docker-compose up --build -d
    
  2. Stop the application with Docker Compose:

    docker-compose down
    

Project Structure

trend-finder/
β”œβ”€β”€ src/
β”‚   β”œβ”€β”€ controllers/    # Request handlers
β”‚   β”œβ”€β”€ services/       # Business logic
β”‚   └── index.ts        # Application entry point
β”œβ”€β”€ .env.example        # Environment variables template
β”œβ”€β”€ package.json        # Dependencies and scripts
└── tsconfig.json       # TypeScript configuration

Contributing

  1. Fork the repository
  2. Create your feature branch (git checkout -b feature/amazing-feature)
  3. Commit your changes (git commit -m 'Add some amazing feature')
  4. Push to the branch (git push origin feature/amazing-feature)
  5. Open a Pull Request
Share:
Details:
  • Stars


    1
  • Forks


    0
  • Last commit


    5 months ago
  • Repository age


    4 months
  • License


    MIT
View Repository

Auto-fetched from GitHub .

MCP servers similar to Trend Finder:

Β 

Β 
Β 
  • Stars


  • Forks


  • Last commit


Β 

Β 
Β 
  • Stars


  • Forks


  • Last commit


Β 

Β 
Β 
  • Stars


  • Forks


  • Last commit


Trend Finder: MCP Server – MCP.Bar