How my team killed manual standups with Claude + Kollabe MCP

#ai #webdev #productivity #agile

The standup didn't die because we hated the meeting. It died because the update part (yesterday, today, blockers) turned into a five-minute morning tax I was already paying in PRs and Jira tickets. I'd close my IDE, open the standup tool, and re-type the same information into a shorter form.

Three weeks ago I stopped. Now Claude reads my activity, drafts the update, I edit it for thirty seconds, and submit. Same content. None of the typing tax. The unexpected part? My EM said the team's standups got better, not worse.

Here's what we tried, what stuck, and what surprised me.

What we replaced

Our old standup was async-by-policy and screenshot-by-reality. Eight engineers, four timezones, a Slack channel pinned to the top of the workspace, and a 9am Sydney "soft deadline" that meant nothing to the engineer in Berlin who'd just woken up. People wrote the update they remembered, not the update that was true. The 4pm thing where you helped a teammate debug a deploy? Forgotten. The PR you shipped before lunch? Forgotten. The blocker you mentioned in standup three days ago? Still there, mentioned for the third time, with no thread connecting the three appearances.

A 2023 Atlassian survey put manager time on status collection at around 17% of the working week. That number tracks for me. The expensive bit was never the meeting itself, which was already 60 seconds of skimming. The expensive bit was the writing and the chasing and the synthesising into something a stakeholder could read on a Friday.

We didn't want to replace the standup. We wanted to remove the typing.

The new workflow, end to end

Every engineer on the team runs one saved Claude prompt in the morning. Five steps, none of which involve typing into the standup tool.

The engineer opens Claude Desktop. Or Cursor. Or Claude Code. Pick your client.
They run their saved standup prompt.
Claude reads yesterday's GitHub PRs, Jira transitions, and (if they've connected it) calendar.
Claude drafts answers for each standup question. The engineer reads, edits anything wrong, adds a real blocker if there is one.
The engineer says "submit". Claude calls Kollabe's standup_submit_answers tool. The update lands in the standup view exactly as if the engineer had typed it.

The whole loop is about thirty seconds on a normal day. On a day with a real blocker it's two minutes, because the engineer adds context the AI can't infer.

The prompt itself is the only thing worth copying:

You are drafting my Kollabe standup for today.

1. Use the Kollabe MCP to find my standup.
2. Pull my activity from yesterday using the GitHub MCP (PRs opened/merged/reviewed,
   commits on branches I own) and the Jira MCP (issues I transitioned, commented on,
   or that were assigned to me).
3. Use Kollabe to get the question list for my standup.
4. Draft an answer for each question, in plain language, no bullets longer than 12 words.
   - "Yesterday" = what I shipped or moved.
   - "Today" = what's actually on my calendar / picked up, not aspirational.
   - "Blockers" = empty unless I genuinely have one.
5. Show me the draft. Wait for me to approve.
6. On approval, submit via Kollabe.

Save it as a Claude Project, a slash command, or a snippet in your client of choice. Mine lives as a saved prompt called /standup in Claude Code so I can fire it from the terminal.

Why this beats a Slackbot, a form, or just yelling in chat

I've used the Slackbots. I've built the forms. I've yelled in chat. None of those solved the real problem, which is that the update was always a half-remembered version of the day. An AI draft built from actual activity is grounded. It catches the 4pm thing because the 4pm thing exists in your commit history.

There's a more boring reason this matters too: structured data. When the standup is text in a Slack channel, the AI summary on Friday is doing pattern recognition on noise. When the standup is structured submissions in Kollabe, the same summary works against typed fields it actually understands. You can ask "which blockers appeared more than once this sprint" and get a real answer instead of a guess.

The other thing took me a sprint to notice: acting identity. The MCP token submits the standup as the engineer, with their role and permissions, against a real audit trail. There's no bot user posting on someone's behalf. The blocker is owned by the person who hit it, and the threading goes to the person who can fix it. Sounds like a small detail. It isn't.

The manager-side win

Before this, my EM read about twelve standups a day, mostly skimmed, asked clarifying questions in DMs. By Friday she'd compile a sprint roll-up by hand, and her Friday morning was that.

Now she runs one prompt:

Summarise the team's Kollabe standups for the last 5 working days
from the "Web" space. Group recurring themes. Flag any blocker that
appears in more than one submission.

Behind the scenes that's standup_list_submissions for the date range, standup_get_summary for the days where Kollabe has already produced one, and Claude clustering across the rest. The output is a markdown digest she can paste into a doc.

For end-of-sprint reporting she runs the same prompt with a fortnightly window. End-of-quarter, monthly, same prompt with a different range. No typing.

She told me last week, almost as a side note: "I used to spend Friday mornings making the report. Now I spend it asking better questions." That's the line that convinced me this wasn't a productivity-hack post. It's a job-shape-changing post.

What about the live standup?

Some teams still gather. Timezone-overlap teams, junior-heavy teams, teams who actually like seeing each other. We used to be one of them, and one of our smaller teams still is.

Live standup with pre-submitted updates is a different meeting than live standup without. Everyone walks in with their answers already in the tool. Nobody reads aloud. The fifteen minutes goes to discussion of blockers and dependencies, not roll call.

Stop reading what's on the screen. The screen already says what you did. The room is for what you need.

That reframe, more than the AI bit, is what changed the meeting for the smaller team. AI just made it cheap to always have the screen pre-filled.

The book-of-record argument

This is the part nobody talks about until they've been on Kollabe for a quarter and then tried to leave.

Slack standups vanish. They scroll, they're searchable in theory, they're un-readable in practice after a week. The blocker mentioned three days ago lives in someone's memory or it doesn't exist at all.

A persistent standup tool that AI-summarises is a book of record for the team's day-to-day. When someone asks "when did we first notice the OAuth issue", the answer is two clicks, not a Slack archaeology session. Sprint review prep becomes one prompt. Onboarding a new manager becomes "go read the last four weeks". Performance review season becomes a thing the data already exists for.

You don't notice you need this until you've had it for a while and then can't go back.

What didn't work

I'm not going to pretend any of this was clean.

For the first two days, Claude over-quoted commit messages verbatim. The standup looked like a git log. Fix: I added "summarise, don't transcribe" to the prompt and the issue disappeared.

One engineer turned off the auto-pull workflow because she likes writing her standup with a coffee. That's fine. Both workflows coexist. Kollabe doesn't care whether the submission came from a chat panel or a keyboard.

The worst one: an engineer connected his calendar MCP to the workflow and Claude pulled the title of a 1:1 ("promotion conversation: ") into the "Today" line. He noticed before submitting. We now strip 1:1 titles from the calendar prompt by default. If you connect calendar to anything that posts, do this first, not after.

These are the kinds of things you'll hit. None of them are dealbreakers. All of them are worth knowing about before you ship the workflow to your team.

Setup, in four minutes

Connect Claude Desktop (or your client) to Kollabe MCP. There's a 60-second setup guide. The config snippet is:

{
  "mcpServers": {
    "kollabe": {
      "url": "https://kollabe.com/api/mcp",
      "transport": "http"
    }
  }
}

Restart the client, approve the OAuth prompt, pick your org. Drop the prompt above into a Claude Project or save it as a slash command.

First standup with the new workflow: review carefully, edit liberally, submit. Second standup: review less. Third: tab-tab-submit and you're done before your coffee's cold.