Log inSubmit server
Standupbot logo

Standupbot

Builds personal, team, and repository activity summaries from GitHub data over MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Standupbot

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "standupbot": {
      "command": "npx",
      "args": [
        "-y",
        "standupbot-mcp"
      ],
      "env": {
        "GITHUB_TOKEN": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

The install command started, but didn't respond the way we expected when we tried to talk to it.

npx -y standupbot-mcp

initialize succeeded but no response to tools/list.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 15d ago.

Overview

The standupbot MCP server retrieves GitHub commits, pull requests, reviews, and issues for standup reporting. It runs locally as an MCP process and makes direct HTTPS requests to api.github.com, using a GitHub personal access token for authorization. Use it when you need a personal activity summary, a team report for multiple usernames, or recent activity from a public or private repository. Results are organized for use in conversational responses and can be copied into tools such as Slack.

Use cases

  • Generate a personal daily standup from recent GitHub activity
  • Compile a team standup for multiple GitHub usernames
  • Review recent activity in a public or private repository
  • Prepare GitHub updates for copying into Slack

Key features

  • Personal standup reports
  • Multi-user team standups
  • Repository activity summaries
  • Commit, pull request, review, and issue tracking
  • Private repository access with a GitHub token
  • Local MCP execution with direct GitHub API calls

Tools3

What Standupbot lets your agent do. Expand a tool for its parameters.

Self-reported~54 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

11/11 checks healthy over the last 61d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 9d ago via OSV.dev · standupbot-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads96Package downloads in the last 30 days.
Last commit4mo agoMost recent push to the default branch.
Install checkInconclusiveStarted but did not complete the MCP handshake in our test.
Tools exposed3Callable tools this server registers over MCP.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Standupbot works

What the standupbot MCP server does

The standupbot MCP server connects an MCP-compatible client to GitHub activity data. It can collect commits, pull requests, pull request reviews, and issues from a selected time window, then return the results as a standup-style report. The personal report accepts a GitHub username and a number of hours, so you can ask for activity from the last 24 hours or another interval.

A second mode builds a team report from a list of GitHub usernames. This is useful when each person’s activity needs to be combined into one recurring status update. The repository activity tool instead summarizes recent events for a specified repository, including repositories that are public or private when the supplied token has access.

How it works

The server exposes three MCP tools:

  • get_standup retrieves one user’s commits, pull requests, reviews, and issues from the requested number of recent hours.
  • get_standup_multi performs the same type of collection for multiple GitHub usernames.
  • get_repo_pulse reports recent activity for a selected public or private repository.

The standupbot MCP server is designed to run through a local command such as npx -y standupbot-mcp. The returned information includes activity details such as repository names, commit identifiers, pull request numbers, titles, and links where applicable.

Setup and configuration

Create a GitHub classic personal access token from GitHub’s developer settings. The documented scopes are repo for access to private repositories and read:user for reading user information. Configure the server in an MCP client by running the package with npx and supplying the token through the GITHUB_TOKEN environment variable.

The token can also be passed in tool calls. If a call does not provide one, the server falls back to GITHUB_TOKEN from the MCP configuration. Keep the token in the local configuration rather than embedding it in prompts.

Tools and capabilities

Use get_standup for an individual report, such as a user’s activity during the previous 24 hours. Use get_standup_multi when the report should cover several GitHub accounts, for example a team with separate usernames. Use get_repo_pulse when the question concerns what has recently happened in one repository rather than what one person did.

A typical request supplies the GitHub username and time range for a personal report, a list of usernames for a team report, or a repository identifier for a repository pulse. The resulting summaries can be used as daily standup material or copied into a communication channel.

Limitations and notes

Access to private repository activity depends on the token’s permissions, while public repository activity can be queried without private repository access. The documented setup uses a classic token with repo and read:user scopes.

The project is distributed under the MIT license. Token storage is described as local to the client configuration, and requests are sent directly from the local server to GitHub.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Standupbot

standupbot is an MCP server that connects Claude-compatible MCP clients to GitHub and provides tools for personal standups, team standups, and repository activity reports. Its main tools are `get_standup`, `get_standup_multi`, and `get_repo_pulse`, covering commits, pull requests, reviews, and issues.

Install it through an MCP client configuration that runs `npx -y standupbot-mcp`. Add the command and arguments under an MCP server named `standupbot`, then provide a GitHub token through the `GITHUB_TOKEN` environment variable.

The documented token scopes are `repo` and `read:user`. `repo` allows access to private repositories, while `read:user` provides user information. The token may be configured as `GITHUB_TOKEN` or passed directly in tool calls.

The documented clients are Claude Desktop and Claude Code CLI, both configured to run the server locally with `npx`.

Related MCP servers

All in Version Control All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewStandupbot AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/standupbot?style=directory)](https://allmcps.com/mcp/standupbot)
HTML Embed
<a href="https://allmcps.com/mcp/standupbot"><img src="https://allmcps.com/api/badge/standupbot?style=directory" alt="Standupbot on AllMCPs" /></a>