run_async_standup
A structured async-standup template a team can adopt.
How to use it
Project documentation lists run_async_standup for the MCP MCP server. Add the server to your MCP client (Claude Desktop, Cursor, Windsurf and others), then check which tools your installed version makes available. Tool availability can depend on configuration and credentials. A server handshake does not verify this tool’s behavior. See the full listing for setup details.
Install MCP
claude mcp add open-async -- npx -y @open-and-async/mcpOther tools in MCP (10)
Sections + chapters + one-line TL;DRs. The map.
Meeting purpose/agenda → the async equivalent (artifact, owner, deadline).
Decision + options → a structured ADR/decision-doc scaffold (context, options, tradeoffs, decision, reversibility).
A chapter's TL;DR + taglines + read-the-chapter link.
Role-aware (manager/ic) guidance for a topic.
Taglines + their /q/<slug> quote-card URLs.
Maps skepticism ("async is slow") to the book's reframe.
Scores a draft update against the "work loudly / no surprises" rubric and suggests fixes.
Keyword search over the summary corpus; short cited snippets.
Recommends sync vs async for a task, with the decision rule.