Skip to main content
Glama
Sign In
standup-mcp

standup-mcp

by sathvic-kollu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to standup-mcp

No user-submitted related servers found.

    Related Servers

    • Standup Voice

      Actualjudgepresident
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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

    • standup-mr

      Jubstaaa
      A
      license
      A
      quality
      A
      maintenance
      Generates a daily standup note from GitLab merge request or GitHub pull request state: what is ready to merge, what is blocked, what is stale, and what is waiting on your review. When CI is red it opens the failed job's log and reports the error lines, so the note says why the pipeline failed rather than just that it did.
      3
      135 npm
      1
      MIT

    • Prodbeam MCP Server

      prodbeam
      A
      license
      A
      quality
      C
      maintenance
      Generates engineering intelligence reports (standups, weekly summaries, sprint retrospectives) from GitHub and Jira data, accessible via MCP clients or CLI.
      10
      4 npm
      MIT
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    A4.3/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a distinct purpose: standup_draft for daily summaries, blocker_scan for identifying blockers, weekly_summary for longer-term rollups, activity_digest for raw chronological data, and list_sources for inspecting configured sources. There is no overlap that would cause an agent to select the wrong tool.

    Naming Consistency3/5

    Names are all lowercase snake_case with no style mixing, but the word order is inconsistent: list_sources follows verb_noun (imperative), while standup_draft, blocker_scan, weekly_summary, and activity_digest are object_verb or noun-based compounds. This mixed pattern is readable but not predictable.

    Tool Count5/5

    With 5 tools, the server is well-scoped for its purpose of generating standup and activity reports. Each tool provides a meaningful function without redundancy or unnecessary bloat, sitting comfortably in the ideal range.

    Completeness5/5

    The domain covers daily standup generation, blocker detection, weekly summaries, raw activity retrieval, and source status. There are no obvious gaps for the stated purpose; the tools form a cohesive set for both quick standups and deeper review.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources