Today · Standup over MCP

Standup over MCP

The standup is not a product feature. It is a prompt. RepoOps already ships the daily digest by email and chat webhook; this recipe is the bring-your-own-agent version. Point any MCP client (Claude Code, Claude Desktop, Cursor) at the RepoOps MCP server and ask for the team summary on your own schedule, in your own words.

Setup

  1. Connect an MCP client to RepoOps.

    Hosted: add https://repoops.ai/mcp as a Streamable HTTP MCP server and sign in when prompted (OAuth 2.1; a scoped bearer token also works for headless callers). For Claude Code: claude mcp add --transport http repoops https://repoops.ai/mcp. Local desktop alternative: the stdio server bin/mcp-brain.mjs, bound to one repo, no auth needed.

  2. Check the tools are visible.

    The standup reads from tools the server already exposes: list_sessions, search_telemetry, get_accountability_loops, list_pending_questions, and ask_brain. If your client lists them, you are done with setup.

  3. Ask for the standup.

    Use the prompt below, or your own variant. Schedule it however your agent schedules things (a cloud routine, a cron, or typing it with coffee).

The prompt

Summarize what everyone on my team has been working on in the last 24 hours, using the RepoOps MCP tools. One short narrative subsection per engineer: what they shipped (merged PRs with titles), what it cost, and any open questions they left. Keep session counts to a single footnote line. Run this for me every morning at 7 am.

The scheduled, zero-setup version of the same summary is the daily digest: email to team admins, plus your team chat webhook if one is set on /team. This recipe exists for teams that want the summary in their own agent, their own tone, or their own channel.

Honest limits

  • Hosted scope is your team only: every tool call is bounded to the signed-in account's team. No cross-tenant reads.
  • Merged-PR detail (titles, authors) comes from git history via the desktop; the hosted rollup carries the desktop's distilled snapshot, so a team with no bound desktop sees activity and spend but not PR titles.
  • The agent, its schedule, and its model bill are yours. RepoOps serves the facts; it does not run the summarizer.
ⓘ
Prefer zero setup?
The built-in daily digest already includes the per-developer standup narrative and merged-PR counts (the local desktop digest adds a cross-session questions count). This page is for the bring-your-own-agent pattern, not a replacement for it.

Read more