Gitstandup

io.github.muba00Published by GitHub account muba00v1.0.6Updated Oct 24, 2026

Generate daily standup notes from git commits across multiple repositories with AI summaries.

Overview

AI-generated overview

A local MCP server that collects your git commits across configured repositories and lets an AI assistant turn them into daily standup notes.

What you can do
Generate standup notes from commits in configured repositories, with an optional lookback in hours and an optional list of repo paths to use for one run. Add repository paths to the saved configuration. List the repositories currently configured. Remove repository paths from the configuration. Commit collection is filtered to your git user email, skips generated files such as lock files and minified code, and can include truncated code diffs for the assistant to summarize.
When to use it
Useful when you work across several local git repositories and want an assistant to draft standup updates or answer questions like what you worked on yesterday, without checking each repository by hand.
Requirements
Runs locally over stdio, typically launched with npx from the npm package gitstandup-mcp, so Node.js and npm are needed. Git must be available and the configured paths must be local git repositories. Repository paths are stored in a config file under your home directory. No accounts, API keys or environment variables are declared.
Before you install
The server reads commit history and code diffs from the repositories you add, and that content is passed to the AI assistant, so avoid adding repositories with sensitive code. The add and remove tools change a configuration file in your home directory. Commit filtering relies on your git user email being set correctly.

Installation

In SourceWeft

  1. Open Gitstandup in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

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)

🚀 Quick Start

Installation

bash
# Using npx (no installation needed)npx -y gitstandup-mcp
# Or install globallynpm install -g gitstandup-mcp

Setup with Claude Desktop

Add to your Claude Desktop config at ~/Library/Application Support/Claude/claude_desktop_config.json:

json
{  "mcpServers": {    "gitstandup": {      "command": "npx",      "args": ["-y", "gitstandup-mcp"]    }  }}

Setup with VS Code (GitHub Copilot)

Add to your VS Code MCP settings:

json
{  "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

  1. Add your repositories:

    "Add /path/to/my/project to GitStandup"
  2. Generate standup notes:

    "Generate my standup notes"
  3. 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:

typescript
{  "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:

typescript
{  "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

bash
# Clone the repositorygit clone https://github.com/muba00/gitstandup.gitcd gitstandup
# Install dependenciesnpm install
# Buildnpm run build
# Test locallynode build/index.js

Project 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:

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:

  1. Update version in both files:

    bash
    # Update version in package.json and server.jsonnpm version patch  # or minor/major
  2. Build and publish to npm:

    bash
    npm run buildnpm publish
  3. Install mcp-publisher (first time only):

    bash
    brew install mcp-publisher# ORcurl -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/
  4. Authenticate (first time only):

    bash
    mcp-publisher login github
  5. Update server.json version to match package.json and publish:

    bash
    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.

Source: README.md at commit 9221543

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.6LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts