get_repo_data returns history for a repository out of the server's own data file, and the daily and weekly reports run over the repositories named in configuration rather than ones passed per call — which means the set being reported on is a deployment decision, not a prompt. Delivery is independent in the same way: ai_analysis answers a question about the stored data, and send_feishu_message will post whatever message you hand it, report or not.
A GitHub repository activity reporter with 5 tools: it keeps historical data for the repositories you configure, produces daily and weekly reports from it, runs AI analysis over the same data, and delivers messages to a Feishu chat.
- get_repo_data returns the stored historical data for a named GitHub repository.
- generate_daily_report and generate_weekly_report build the activity report for today and for the current week across the tracked repositories.
- ai_analysis puts a question to a model over the collected repository data and returns its analysis.
- send_feishu_message posts a message to the configured Feishu group.
A GitHub token in GITHUB_TOKEN, the repositories to track in REPORT_REPOS, and a data file at DATA_FILE for the collected history. ai_analysis needs a model endpoint through API_KEY, API_BASE_URL and API_MODEL; send_feishu_message needs an incoming webhook in FEISHU_WEBHOOK.
One command plus a key — npx -y star-report mcp-server, then supply credentials