A
licenseA
qualityC
maintenanceSemantic git queries via MCP. Beyond git log — answer who/what/why about any line, file, or branch with blame, co-change, PR linkage.
6
8 npm
2
MIT
standup-mr
by Jubstaaa
Related Servers
Alternatives to standup-mr
- AlicenseAqualityCmaintenancePython MCP server for GitHub operations, providing native tool integration with Claude Code and other MCP clients. It enables managing issues, pull requests, CI status, milestones, and batch operations via natural language.15MIT
Related Servers
- AlicenseAqualityDmaintenanceGenerates daily standup drafts from your actual GitHub, Jira, Linear, and Slack activity, grouping work items and detecting blockers.524 npmMIT
- AlicenseAqualityCmaintenanceGenerates daily standup notes from your git commits across multiple repositories using AI.457 npm5MIT
- AlicenseNot gradedqualityBmaintenanceEnables building a daily standup from real GitHub activity and spoken notes, exposing tools to fetch a voice-ready summary, capture tasks, bugs and blockers, list and complete items, and file deduplicated GitHub issues. Output is voice-first, returning a short spoken version alongside markdown for the screen.MIT
- FlicenseNot gradedqualityDmaintenanceSummarizes Slack activity and GitLab merge requests with OpenAI to help generate daily standups, weekly reports, or quarterly check-ins.-
- AlicenseNot gradedqualityAmaintenanceRanks your open pull requests by urgency with human-readable reasons, surfacing changes requested, unresolved review threads, real failing checks, merge conflicts, and reviewer silence. Exposes tools for an attention report, a simple list of open PRs, and a per-PR deep dive covering reviews, checks, and threads.665 npmMIT
- AlicenseAqualityDmaintenanceAutomates creating Pull Requests (GitHub) and Merge Requests (GitLab) using git CLI, repository templates, and LLM-assisted content generation from your diff and commit logs.440 npmMIT
TDQS
A4.5/5.0
Scored across 3 tools
Disambiguation5/5
The three tools form a clear pipeline: fetch data, fetch writing rules, then post the note. Each has a distinct purpose and no two could reasonably be confused (read vs write, data vs rules vs delivery).
Naming Consistency5/5
All three follow a consistent verb_noun pattern (get_standup_data, post_standup_note, get_note_instructions) in snake_case, with no deviations.
Tool Count5/5
Three tools map exactly onto the workflow's essential steps—fetch snapshot, fetch playbook, post note—with nothing redundant or missing.
Completeness4/5
The surface covers the full standup workflow end to end. Minor gaps are inherent to the stated scope (read-only snapshot, no MR search/filter), which is documented rather than an oversight.
Maintenance
ActivityMaintained
ResponsivenessNo issues