Standup

Open Source — GitScrum MCP Server is open source under the MIT license. Available on npm and GitHub. Model Context Protocol server for GitScrum — Claude, GitHub Copilot, Cursor, and any MCP-compatible client full operational access to your project management stack.

The standup tool provides 7 actions for managing asynchronous daily standup reports across your team. Submit what you did yesterday, what you're working on today, and any blockers — all through natural language conversation with your AI assistant. No standup meetings required.

Standups in GitScrum follow the standard yesterday / today / blockers format used by agile teams worldwide. The MCP Server lets your AI assistant submit standups, review team reports, and surface blockers without leaving your IDE or AI client. Every standup is linked to a specific project, making cross-project visibility straightforward.

Actions Overview

Listing Standups

The list action returns standup reports for a specific project, ordered by date. Each entry includes the author, date, yesterday/today/blockers content, and the standup UUID for follow-up operations.

Parameters

You:  "Show standups for the Backend project"
AI:   Calls standup action=list → returns standup reports with author and content

You:  "Show standups from last Monday for the Mobile App project"
AI:   Calls standup action=list with date="2026-02-02" → returns filtered results

You:  "What did Sarah report on the Backend project?"
AI:   Calls standup action=list with user="sarah" → returns Sarah's standup entries

Getting Standup Details

The get action retrieves the full details of a specific standup report by its UUID. This includes yesterday, today, blockers, author information, and timestamps.

Parameters

You:  "Show me the details of that standup report"
AI:   Calls standup action=get with uuid → returns full standup content

Creating Standups

The create action submits a new standup report for a project. The yesterday and today fields are required — they represent what you accomplished and what you're planning. The blockers field is optional but strongly recommended when impediments exist.

Required Parameters

Optional Parameters

You:  "Submit my daily standup: yesterday I finished the auth module,
       today I'm starting the payment integration, blocked by missing API keys"
AI:   Calls standup action=create with yesterday, today, blockers
      → "Standup submitted for Backend project"

You:  "My standup: completed PR reviews yesterday, today working on database migration"
AI:   Calls standup action=create → "Standup submitted"

You:  "Log standup — yesterday: fixed 3 bugs in checkout flow.
       Today: starting performance optimization. No blockers."
AI:   Calls standup action=create → "Standup submitted"

Updating Standups

The update action modifies an existing standup report. You can update any combination of the three fields — yesterday, today, or blockers — without affecting the others.

Parameters

You:  "Update my standup — I also fixed the caching issue yesterday"
AI:   Calls standup action=update with updated yesterday field
      → "Standup updated"

You:  "Add a blocker to my standup: waiting on design approval"
AI:   Calls standup action=update with blockers → "Standup updated"

Personal Standup History

The my action returns your own standup history across all projects within a workspace. This is useful for reviewing your own reports, preparing for 1:1 meetings, or generating weekly summaries.

Parameters

You:  "Show my recent standups"
AI:   Calls standup action=my → returns your standup history

You:  "What did I report last week?"
AI:   Calls standup action=my → AI filters to last week's entries

Today's Standups

The today action returns all standup reports submitted today for a specific project. This gives you a real-time view of what the team is working on and any blockers that need attention.

Parameters

You:  "Show team standups for today"
AI:   Calls standup action=today → returns today's standup reports

You:  "Has everyone submitted their standup today?"
AI:   Calls standup action=today → AI compares submissions against team roster

You:  "What blockers does the team have today?"
AI:   Calls standup action=today → AI extracts and summarizes blockers

Team Standup Summary

The team action returns an aggregated standup summary for the entire team within a project. This provides managers and team leads with a consolidated view of progress, planned work, and active blockers across all team members.

Parameters

You:  "Give me a team standup summary"
AI:   Calls standup action=team → returns aggregated team summary

You:  "What's the team working on today?"
AI:   Calls standup action=team → AI summarizes today's planned work

You:  "Are there any recurring blockers across the team?"
AI:   Calls standup action=team → AI identifies patterns in reported blockers

Async Standup Workflow

The standup tool enables fully asynchronous standups — no meetings, no interruptions. Here's a typical daily workflow:

1. Submit your standup at the start of the day

You:  "My standup: yesterday I completed the user dashboard redesign and
       reviewed 2 PRs. Today I'll work on the notification system.
       Blocked by the staging environment being down."
AI:   Submits standup → "Standup submitted for Backend project"

2. Review team progress mid-morning

You:  "What's the team working on today?"
AI:   Calls standup action=today → summarizes team plans and blockers

3. Address blockers proactively

You:  "What blockers does the team have?"
AI:   Calls standup action=today → "2 blockers reported:
       - Sarah: waiting on design approval
       - Mike: staging environment is down"

4. Update your standup if plans change

You:  "Update my standup — I got pulled into a production incident,
       switching my today to incident response"
AI:   Updates standup → "Standup updated"

Team Visibility Patterns

Standups drive alignment across distributed teams. Common visibility patterns:

• Daily digest. Use today at the end of each day to review what the team accomplished and identify carryover items.
• Blocker escalation. Use team or today to surface blockers early. Cross-reference with task data to understand impact.
• Sprint retrospective input. Use list with date ranges to review standup patterns across a sprint — recurring blockers and shifting priorities become visible.
• 1:1 preparation. Use my to review your own standup history before manager check-ins.

Next Steps

• Analytics: Access project health reports and agile metrics.
• Activity: Monitor project-wide activity feeds and audit trails.
• Tasks: Manage the tasks referenced in your standups.
• Sprints: Plan sprints and track progress alongside standup data.