Prodbeam MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
| prompts | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| setup_teamB | One-time team setup. Provide team name and member emails — prodbeam auto-discovers GitHub usernames, Jira accounts, active repos, projects, and sprints. |
| add_member | Add a new member to the team. Provide their email — prodbeam auto-discovers their GitHub and Jira identities. |
| remove_member | Remove a member from the team by email address. |
| refresh_config | Re-scan repos and sprints for existing team members. Updates team config with newly discovered repos and current sprint info. |
| standup | Generate a personal daily standup report. Fetches your GitHub commits, PRs, reviews, and Jira issues from the last 24 hours. Use when the user asks: "standup", "what did I work on", "my activity", "daily update". Requires team setup. |
| team_standup | Generate a full team standup report. Shows per-member activity from the last 24 hours with aggregate stats. Use when the user asks: "team standup", "what did the team do", "team activity", "everyone's update". |
| weekly_summary | Generate a weekly engineering summary with metrics, repo breakdown, and Jira stats. Covers the last 7 days by default. Use when the user asks: "weekly summary", "weekly report", "this week's metrics", "engineering summary", "productivity report". |
| sprint_retroA | Generate a sprint retrospective report with merge time analysis, completion rates, and Jira metrics. Auto-detects the active sprint from Jira. Use when the user asks: "sprint retro", "retrospective", "sprint review meeting", "how did the sprint go". |
| sprint_reviewA | Review current sprint progress with deliverables, risks, and developer status. Mid-sprint health check. Use when the user asks: "sprint review", "sprint status", "sprint health", "how is the sprint going", "sprint progress". |
| get_capabilitiesA | Returns available tools, current team config status, and credential status. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| standup | Generate your personal daily standup report |
| team-standup | Generate the full team's daily standup report |
| weekly-summary | Generate a weekly engineering summary with metrics |
| sprint-retro | Generate a sprint retrospective with what went well, improvements, and action items |
| sprint-review | Review current sprint progress, deliverables, and risks |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
setup_team and get_capabilities are clearly distinct, and sprint_retro vs sprint_review are separated by timing and purpose (end-of-sprint retrospective vs mid-sprint health check). However, the similar sprint-prefixed names could cause an agent to hesitate or misselect without reading the descriptions carefully.
setup_team and get_capabilities follow a verb_noun pattern, while sprint_retro and sprint_review use a noun-like prefix + shortened noun pattern. The sprint_ prefix gives some cohesion, but the overall naming convention is mixed.
Four tools is well-scoped for a focused MCP server that handles team setup, two sprint report types, and capability/status discovery. Each tool addresses a distinct workflow step with no unnecessary duplication.
The tool set covers the core workflow: configure a team, verify capabilities/config, and generate both retrospective and mid-sprint review reports. Minor gaps exist, such as the ability to update team configuration or retrieve historical sprint reports, but these are not critical to the server's stated purpose.