git-standup-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GIT_STANDUP_REPOS | No | Comma-separated list of directories to scan for git repos | ~/Documents |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| git_standupB | Get a standup report of recent git activity across your repos. Args: days: Number of days to look back (default: 1 = yesterday) author: Filter by author name (partial match). If not set, shows all. repos: Comma-separated repo paths. If not set, uses GIT_STANDUP_REPOS env or ~/Documents. |
| git_reposB | List all git repos that git-standup can see. |
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 2 tools
The two tools have clearly distinct purposes: git_repos lists available repositories, while git_standup generates activity reports. There is no overlap in functionality, making tool selection unambiguous for an agent.
Both tools follow a consistent snake_case naming pattern with the 'git_' prefix, maintaining perfect naming consistency throughout the set. This predictability aids agent understanding and usage.
With only two tools, the server feels under-scoped for its apparent domain of git activity reporting. While the tools cover core functionality, the lack of additional operations (e.g., configuration management, filtering options as separate tools) makes the surface thin and potentially limiting.
The server covers the basic workflow of listing repos and generating standup reports, but there are notable gaps. Missing operations include managing git-standup configurations, handling repo exclusions, or providing detailed commit analytics, which could hinder more complex agent tasks.