The git-standup-mcp server lets you generate standup reports from git history, explore repositories, and post to Slack.
git_standup: Generate a standup report of recent git activity across configured repositories. Options include days (how far back to look, default 1), author (filter by partial name match), and repos (override default repo paths).
git_repos: List all git repositories the server has access to (auto-discovered up to 2 levels deep from configured directories).
post_to_slack: Send a standup report or any message to a Slack channel via an Incoming Webhook, with optional channel override.
Automated posting: Schedule daily standup posts on weekdays via cron, with support for dry runs, multi-day coverage (e.g., to handle weekends), and author filtering.
Generates standup reports from git history across multiple repositories, providing tools to query recent commits, filter by author, and list accessible repos for activity tracking.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@git-standup-mcp what did I work on yesterday?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP server that generates standup reports from your git history and posts them to Slack. Ask Claude what you did yesterday, or set up a cron job to post automatically every morning.
# Add to Claude Code
claude mcp add git-standup -- uv run --directory /path/to/git-standup-mcp git-standup-mcpOr add to your MCP config manually:
{
"mcpServers": {
"git-standup": {
"command": "uv",
"args": ["run", "--directory", "/path/to/git-standup-mcp", "git-standup-mcp"],
"env": {
"GIT_STANDUP_REPOS": "/path/to/repo1,/path/to/repo2",
"SLACK_STANDUP_WEBHOOK": "https://hooks.slack.com/services/..."
}
}
}
}Related MCP server: git-finder-mcp
Once connected, ask Claude:
"What did I do yesterday?"
"Give me a standup for the last 3 days"
"Post my standup to Slack"
"What repos do you have access to?"
Set up an Incoming Webhook for your standup channel, then set SLACK_STANDUP_WEBHOOK.
# Post yesterday's standup at 9am on weekdays
0 9 * * 1-5 cd /path/to/git-standup-mcp && \
GIT_STANDUP_REPOS="~/projects,~/work" \
SLACK_STANDUP_WEBHOOK="https://hooks.slack.com/..." \
uv run python -m git_standup_mcp.cron# Dry run — see the report without posting
uv run python -m git_standup_mcp.cron --dry-run
# Monday morning — cover the weekend
uv run python -m git_standup_mcp.cron --days 3
# Filter by author
uv run python -m git_standup_mcp.cron --author "Anisha"git_standupGet a standup report of recent git activity across your repos.
Parameter | Type | Default | Description |
| int | 1 | Number of days to look back |
| string | null | Filter by author name (partial match) |
| string | null | Comma-separated repo paths (overrides env) |
git_reposList all git repos the server can see.
post_to_slackPost a message to Slack via webhook.
Parameter | Type | Default | Description |
| string | required | Message text (supports Slack markdown) |
| string | null | Channel override (uses webhook default if not set) |
Env var | Description |
| Comma-separated directories to scan for repos (default: ~/Documents) |
| Slack Incoming Webhook URL for posting |
Repos are auto-discovered up to 2 levels deep.
List all git repos that git-standup can see.
Inputs: no named parameters. Returns: result
Get a standup report of recent git activity across your repos.
Args: days: Number of days to look back (default: 1 = yesterday) author: Filter by author name (partial match). If not set, shows all. repos: Comma-separated repo paths. If not set, uses GIT_STANDUP_REPOS env or ~/Documents.
Inputs: days, author, repos. Returns: result
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 2 tools
The two tools have clearly distinct purposes: git_repos lists available repositories, while git_standup generates activity reports. There is no overlap in functionality, making tool selection unambiguous for an agent.
Both tools follow a consistent snake_case naming pattern with the 'git_' prefix, maintaining perfect naming consistency throughout the set. This predictability aids agent understanding and usage.
With only two tools, the server feels under-scoped for its apparent domain of git activity reporting. While the tools cover core functionality, the lack of additional operations (e.g., configuration management, filtering options as separate tools) makes the surface thin and potentially limiting.
The server covers the basic workflow of listing repos and generating standup reports, but there are notable gaps. Missing operations include managing git-standup configurations, handling repo exclusions, or providing detailed commit analytics, which could hinder more complex agent tasks.
Writes your daily standup from GitLab or GitHub merge request state: what's ready, blocked or waiting on your review, and why a pipeline is red, read from the failing job log. OAuth sign-in, no API keys; can post the note to Slack, Discord or Google Chat on a schedule.
Code intelligence for LLMs. Analyze, search, and retrieve code from any public git repository.
Opinionated sprint tracker. Read/update tickets, sprints, velocity from Claude/Cursor/Zed.
Generate changelogs, release emails, help-center articles, banners, and social posts from commits.
