Standupbot

io.github.rimysorePublished by GitHub account rimysorev1.0.1Updated Oct 24, 2026

Turns your GitHub activity into a daily standup — commits, PRs, reviews & issues.

Overview

AI-generated overview

A local MCP server that reads your GitHub activity and turns the last hours of commits, pull requests, reviews and issues into a standup report.

What you can do
Summarize your own recent GitHub activity into a personal standup for a chosen time window, ready to paste into chat tools such as Slack. Build a team standup covering the same activity for a list of GitHub usernames. Review recent activity on any public or private repository. Output is grouped into commits, PRs opened, PRs reviewed and issues, with links.
When to use it
Useful when you write daily standups or status updates and want an assistant to gather your GitHub work instead of recalling it yourself, or when a lead needs a quick team or repository activity summary.
Requirements
Runs locally over stdio, typically launched with npx from the npm package standupbot-mcp, so Node.js is needed. Requires a GitHub personal access token supplied as the GITHUB_TOKEN environment variable, with repo and read:user scopes. Needs network access to the GitHub API.
Before you install
The token grants access to private repositories and profile data, so store it only in your local config and scope it narrowly. The server reads GitHub data and sends it to the assistant; no writes to GitHub are described. Team standups query other users' public activity.

Installation

In SourceWeft

  1. Open Standupbot 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

StandupBot MCP

"What did I even do yesterday?" — solved.

StandupBot is a free Model Context Protocol server that connects Claude to your GitHub activity. Ask Claude for your standup and it pulls the last 24h of commits, PRs, reviews, and issues — formatted and ready to paste into Slack.


Tools

ToolWhat it does
get_standupYour personal standup — commits, PRs, reviews, issues in the last N hours
get_standup_multiTeam standup — same thing for a list of GitHub usernames
get_repo_pulseRecent activity on any public or private repo

Quick Start

1. Get a GitHub token

Go to GitHub → Settings → Developer settings → Personal access tokens → Tokens (classic).

Create a token with these scopes:

  • repo (to see private repos)
  • read:user

2. Add to Claude Code

Add this to your Claude Code config (~/.claude/claude_desktop_config.json for Claude Desktop, or .claude/settings.json for Claude Code CLI):

json
{  "mcpServers": {    "standupbot": {      "command": "npx",      "args": ["-y", "standupbot-mcp"],      "env": {        "GITHUB_TOKEN": "ghp_your_token_here"      }    }  }}

3. Ask Claude

Give me my standup for the last 24 hours. My GitHub username is alice.
Generate a team standup for usernames: alice, bob, carol
What's been happening in the facebook/react repo today?

Example Output

## Daily Standup — @alice_Last 24h of GitHub activity_
### Commits- **alice/my-app** (a3f9c12) — fix: resolve race condition in auth middleware  https://github.com/alice/my-app/commit/a3f9c12
### PRs Opened- **alice/my-app** (#42) — feat: add OAuth2 support  https://github.com/alice/my-app/pull/42
### PRs Reviewed- **team-org/backend** (#99) — refactor: extract payment service  https://github.com/team-org/backend/pull/99

Environment Variables

You can set GITHUB_TOKEN as an env var in your MCP config and omit it from tool calls:

json
"env": { "GITHUB_TOKEN": "ghp_..." }

The tool will fall back to the env var automatically if no token is passed.


Privacy

  • Your token is stored only in your local config file.
  • StandupBot makes direct HTTPS calls to api.github.com — no proxy, no telemetry, no servers.
  • 100% open source. MIT license.

License

MIT

Source: README.md at commit 5f93e9f

Tools

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

Version history

1
  1. v1.0.1LatestSep 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