gitstandup
Collects commits from local git repositories to generate daily standup notes.
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., "@gitstandup Generate my standup notes"
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.
GitStandup MCP Server
Generate daily standup notes from your git commits using AI
A Model Context Protocol (MCP) server that automatically collects your git commits from multiple repositories and helps AI assistants generate natural, comprehensive standup summaries.
โจ Features
๐ฆ Multi-repo support - Track commits across all your projects
๐ค User-specific - Only shows your commits (filtered by git user.email)
โฐ Time-based - Configurable lookback period (default: last 24 hours)
๐ฏ Smart diff analysis - Includes code changes with intelligent truncation
๐พ Persistent config - Remembers your repos in
~/.gitstandup/config.json๐งน Clean output - Skips generated files (lock files, minified code)
Related MCP server: Slack Gitlab Digest Model Context Protocol MCP Server
๐ Quick Start
Installation
# Using npx (no installation needed)
npx -y gitstandup-mcp
# Or install globally
npm install -g gitstandup-mcpSetup with Claude Desktop
Add to your Claude Desktop config at ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"gitstandup": {
"command": "npx",
"args": ["-y", "gitstandup-mcp"]
}
}
}Setup with VS Code (GitHub Copilot)
Add to your VS Code MCP settings:
{
"gitstandup": {
"type": "stdio",
"command": "npx",
"args": ["-y", "gitstandup-mcp"]
}
}๐ Usage
Once configured, you can use natural language with your AI assistant:
"Generate my standup notes"
"What did I work on yesterday?"
"Show my commits from the last 2 days"First Time Setup
Add your repositories:
"Add /path/to/my/project to GitStandup"Generate standup notes:
"Generate my standup notes"The AI will create a summary like:
Yesterday I:
Implemented OAuth authentication flow in the api-server
Fixed critical bug in payment processing
Added integration tests for user registration
๐ ๏ธ Available Tools
The server exposes four MCP tools that AI assistants can use:
generate_standup
Generate standup notes from configured repositories.
Parameters:
hours(optional): Number of hours to look back (default: 24)repos(optional): Array of specific repo paths to use
Example:
{
"hours": 48, // Last 2 days
"repos": ["/path/to/repo1", "/path/to/repo2"] // Optional
}add_repos
Add repository paths to the configuration.
Parameters:
paths: Array of absolute paths to git repositories
Example:
{
"paths": ["/Users/you/projects/my-app", "/Users/you/projects/api"]
}list_repos
List currently configured repositories.
Returns: Array of configured repository paths
remove_repos
Remove repository paths from the configuration.
Parameters:
paths: Array of repository paths to remove
๐ง Development
# Clone the repository
git clone https://github.com/muba00/gitstandup.git
cd gitstandup
# Install dependencies
npm install
# Build
npm run build
# Test locally
node build/index.jsProject Structure
gitstandup/
โโโ src/
โ โโโ index.ts # MCP server setup and tool definitions
โ โโโ git.ts # Git operations and commit collection
โ โโโ config.ts # Configuration management
โโโ build/ # Compiled JavaScript (generated)
โโโ package.json๐ Configuration
Repository paths are stored in ~/.gitstandup/config.json:
{
"repos": ["/Users/you/projects/project1", "/Users/you/projects/project2"]
}You can edit this file manually or use the add_repos and remove_repos tools.
๐ฆ Publishing to MCP Registry
This server is discoverable via the GitHub MCP Registry and OSS MCP Community Registry.
For Maintainers
To publish a new version:
Update version in both files:
# Update version in package.json and server.json npm version patch # or minor/majorBuild and publish to npm:
npm run build npm publishInstall mcp-publisher (first time only):
brew install mcp-publisher # OR curl -L "https://github.com/modelcontextprotocol/registry/releases/latest/download/mcp-publisher_$(uname -s | tr '[:upper:]' '[:lower:]')_$(uname -m | sed 's/x86_64/amd64/;s/aarch64/arm64/').tar.gz" | tar xz mcp-publisher && sudo mv mcp-publisher /usr/local/bin/Authenticate (first time only):
mcp-publisher login githubUpdate server.json version to match package.json and publish:
mcp-publisher publish
The server will automatically appear in both the GitHub MCP Registry and the community registry, making it discoverable in VS Code, Claude Desktop, and other MCP-compatible clients.
๐ค Contributing
Contributions are welcome! Feel free to:
๐ Report bugs
๐ก Suggest new features
๐ง Submit pull requests
See CONTRIBUTING.md for details.
๐ License
MIT License - see LICENSE for details
๐ Acknowledgments
Built with:
Note: This tool only reads git commit history and does not modify your repositories.
Available Tools
4 toolsadd_reposAdd RepositoriesB
Add repository paths to the configuration
Inputs: paths (required). Returns: added, repos
generate_standupGenerate Standup NotesA
Generate standup notes from git commits in configured repositories
Inputs: hours, repos. Returns: repos, summary
list_reposList RepositoriesA
List currently configured repositories
Inputs: no named parameters. Returns: count, repos
remove_reposRemove RepositoriesB
Remove repository paths from the configuration
Inputs: paths (required). Returns: repos, removed
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogโฆ
TDQS
Scored across 4 tools
Each tool targets a clear, distinct operation: adding, listing, generating from, and removing configured repositories. There is no overlap or ambiguity between them.
All tool names follow the consistent verb_noun pattern in snake_case: add_repos, list_repos, generate_standup, remove_repos. This is perfectly predictable.
With only 4 tools, the set is tightly scoped to its purpose of managing repository configuration and generating standup notes. Each tool earns its place with no redundancy.
The tool surface covers the full lifecycle of configuration: add, list, remove, and the core generation action. No obvious missing operations for the stated purpose.
Maintenance
Related MCP Connectors
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.
Your team's AI chat agent for standups, automations, and daily work.
Generate changelogs, release emails, help-center articles, banners, and social posts from commits.
Ask what your team decided in meetings, get your standup, and update Jira/Linear-synced tasks.
Related MCP Servers
- AlicenseBqualityDmaintenanceGenerates standup reports from git history by analyzing recent commits across configured repositories. Enables users to query their development activity, such as what they worked on yesterday or over multiple days, through natural language interactions with Claude.2MIT
- FlicenseNot gradedqualityDmaintenanceSummarizes Slack activity and GitLab merge requests with OpenAI to help generate daily standups, weekly reports, or quarterly check-ins.-
- AlicenseAqualityDmaintenanceGenerates daily standup drafts from your actual GitHub, Jira, Linear, and Slack activity, grouping work items and detecting blockers.545 npmMIT
- -licenseNot gradedqualityNot gradedmaintenanceEnables generating AI-powered standups from git activity, with risk flags and markdown digests, via MCP tools.-