mcp

Bring async-first working practices into your editor and AI assistant. This Model Context Protocol server gives your AI the tools to draft a decision doc, turn a meeting into an async artifact, pressure-test a status update, or settle a sync-vs-async debate — without leaving the tools you already work in.

It's the method from Open and Async — the collaborative software-development playbook for remote and distributed teams — as working tools, not reading.

• Stop writing decision docs from a blank page. Hand your AI the decision and the options; get back a structured ADR scaffold — context, tradeoffs, the call, and how reversible it is.
• Turn "let's hop on a call" into an artifact. Give it a meeting's purpose and agenda; get the async equivalent with an owner and a deadline.
• Ship status updates that don't blindside anyone. Score a draft against the "work loudly / no surprises" rubric and get concrete fixes before you post it.
• Settle sync vs. async in seconds. Describe the task; get a recommendation and the rule behind it.
• Run a standup without a meeting. Drop in a structured async-standup template your team can adopt today.
• Win the "async is too slow" argument. Map common objections to a ready reframe, pull role-aware guidance, or search the book's principles — each answer cited and linked.
• Get coached end to end. Run the coach prompt with a situation and it triages sync vs. async, generates the right artifact, adds role guidance, and caps with a shareable line — one composed answer, or a nudge to just have the conversation when that's the better call.

Claude Code:

claude mcp add open-async -- npx -y @open-and-async/mcp

Claude Desktop (claude_desktop_config.json):

{
  "mcpServers": {
    "open-async": {
      "command": "npx",
      "args": ["-y", "@open-and-async/mcp"]
    }
  }
}

Any MCP client that speaks stdio works the same way: run npx @open-and-async/mcp.