standupbot-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | Yes | GitHub personal access token with repo and read:user scopes |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_standupB | Fetch your GitHub activity for the last N hours and format it as a standup report — commits, PRs opened/merged, reviews, and issues. |
| get_standup_multiB | Fetch GitHub activity for multiple users (e.g. your whole team) and return a combined standup report. |
| get_repo_pulseA | Get recent activity (commits, PRs, issues) on a specific repository for the last N hours. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool targets a distinct scope: single repo, single user, or multiple users. No overlap or ambiguity.
All tools follow a consistent 'get_' prefix followed by descriptive noun_phrase pattern.
Three tools cover the essential use cases for a standup bot without being excessive or insufficient.
The set covers repo-level pulse, individual standup, and team standup. A minor gap might be the lack of configurability beyond time range, but core functionality is complete.