standup-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_EMAIL | No | Jira account email. | |
| SLACK_TOKEN | No | Slack user token (xoxp) or bot token (xoxb). With bot token, also set SLACK_CHANNELS. | |
| GITHUB_TOKEN | No | Read-only PAT for GitHub. Reads your commits, PRs, and reviews. | |
| STANDUP_NAME | No | Display name for standup owner (optional, defaults to GitHub handle). | |
| JIRA_BASE_URL | No | Jira Cloud base URL (e.g., https://your-company.atlassian.net). | |
| JIRA_API_TOKEN | No | Jira API token. | |
| LINEAR_API_KEY | No | Linear personal API key. | |
| SLACK_CHANNELS | No | Comma-separated Slack channel IDs, required if using bot token. |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| standup_draftA | Generate your daily standup, what should I say at standup today, from your real activity across the configured tools (GitHub, Jira, Linear, Slack). Returns Yesterday / Today / Blockers grouped by work item, not by tool, in concrete deltas. Defaults to the last working day (Monday reaches back across the weekend). Only reports observed activity; never invents work. |
| blocker_scanA | Surface what is blocking you across GitHub, Jira, Linear, and Slack, ranked by severity. Detects blockers from signals, not self-report: explicit 'blocked / waiting on / stuck' language, PRs awaiting review, in-progress tickets that have not moved, and requests for help. |
| weekly_summaryA | Roll up a week (or any N days) of your real activity into accomplishments, grouped by work item as Shipped vs In progress, with reviews and totals. For 1:1s, weekly status, and self-reviews. Only reports observed work. |
| activity_digestA | A chronological digest of everything you did in a window across the configured tools, newest first, grouped by day. Use it to reconstruct what actually happened, separate from the opinionated standup framing. |
| list_sourcesA | Show which activity sources (GitHub, Jira, Linear, Slack) are configured, or that the server is running on demo data. Does not hit the network; run the server with --check to verify live connections. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
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/sathvic-kollu/standup-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server