# standupbot [Health: Active]

**Category:** 🔄 Version Control  
**Repository:** https://github.com/rimysore/standupbot-mcp  
**GitHub Stars:** 0  
**npm Downloads (last month):** 96  
**Views:** 2  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/standupbot

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

## Tools
Capabilities this server exposes over MCP:

- **get_standup** — Your personal standup — commits, PRs, reviews, issues in the last N hours
- **get_standup_multi** — Team standup — same thing for a list of GitHub usernames
- **get_repo_pulse** — Recent activity on any public or private repo

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

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

**Requires environment variables:** `GITHUB_TOKEN` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

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

_Full upstream README: https://allmcps.com/mcp/standupbot/readme_