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.

Start here if you want the morning team summary with no agent of your own: Team home, where the daily digest and its chat webhook are set.

Setup

  1. Connect an MCP client to RepoOps.

    Local desktop: the stdio server bin/mcp-brain.mjs, bound to one repo, no auth needed. Register it with claude mcp add repoops-brain -- node bin/mcp-brain.mjs. The Streamable HTTP transport (POST /mcp on the RepoOps server, OAuth 2.1, or a dev bearer token for headless callers) is built but off by default, and repoops.ai does not serve it. An operator who turns it on (REPOOPS_HOSTED_MCP=1) connects a client with claude mcp add --transport http repoops https://<your-host>/mcp.

  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 the team's owners and 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

  • Over the HTTP transport every tool call is scoped to the signed-in account's repos, the same boundary the dashboard's Ask the brain uses. No cross-account reads.
  • Merged-PR detail (titles, authors) comes from git history via the desktop; the hosted digest carries per-developer merged-PR counts from the desktop's 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 hosted daily digest already carries per-developer merged-PR counts; the desktop digest adds the per-developer narrative with PR titles and the cross-session questions count. This page is for the bring-your-own-agent pattern, not a replacement for it.

Read more

Last updated