Prodbeam MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| 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 | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/prodbeam/prodbeam-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server