mcpField
O
Open & Async

Open & Async

Local
open-and-async.comProductivity51Updated 1w ago

About Open & Async

Open & Async is an MCP server that brings async-first practices into editors and AI assistants, for remote and distributed teams. It combines practical tools for decision documents and meeting alternatives with cited reference material and prompts for coaching a situation.

Key features

  1. 01Drafts structured decision documents
  2. 02Turns meeting agendas into async artifacts
  3. 03Scores status updates against a rubric
  4. 04Recommends sync or async approaches
  5. 05Provides cited principles and role guidance
  6. 06Includes coaching and task prompts

Use cases

  1. 01Creating an ADR from a decision and its options
  2. 02Replacing a proposed meeting with an async artifact
  3. 03Reviewing a status update before sharing
  4. 04Choosing a sync or async approach for a task

MCP support

The server exposes tools, book resources, and prompts to MCP clients over stdio. Its browser package registers the same tools with WebMCP, without resources or prompts.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"com-open-and-async": {
"command": "npx",
"args": [
"-y",
"@open-and-async/mcp"
]
}
}
}
Run commandnpx -y @open-and-async/mcp

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@open-and-async/mcp1.1.0

Tools

11

Saved tool list · updated 1w ago

ParameterTypeRequiredDescription
contextstringNoBackground: what forces this decision now.
optionsarrayNoCandidate options. Two or three is plenty.
decisionstringYesThe decision to be made, in one line.

Details

From the project README

Open and Async — MCP Server

npm MCP registry CI

Open and Async MCP Server — async-first working practices as tools your AI assistant can use

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.

What you can do with it

  • 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.

Install

Claude Code:

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

Claude Desktop: download open-and-async.mcpb and open it. Claude Desktop installs it in one click, with no config file and no separate Node.js install.

Or add it by hand to 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.

In the browser (WebMCP): @open-and-async/mcp/browser registers the same tools with a page's model context, so an agent in a WebMCP browser can call them without installing anything. It exists for open-and-async.com, the place to use them. The data license doesn't cover serving the book data from other sites. WebMCP carries tools only, not resources or prompts.

import { registerWebMcpTools } from "@open-and-async/mcp/browser";

const modelContext = document.modelContext ?? navigator.modelContext;
// book: the parsed contents of data/book.json.br. Browsers can't decode Brotli
// streams, so the site re-encodes it as gzip at build time.
if (modelContext) registerWebMcpTools({ book, modelContext });

The toolbox

Method tools — pure utility, use them on any project
ToolWhat it does
draft_decision_docDecision + options → a structured ADR/decision-doc scaffold (context, options, tradeoffs, decision, reversibility).
convert_meeting_to_asyncMeeting purpose/agenda → the async equivalent (artifact, owner, deadline).
score_status_updateScores a draft update against the "work loudly / no surprises" rubric and suggests fixes.
run_async_standupA structured async-standup template a team can adopt.
triage_sync_vs_asyncRecommends sync vs async for a task, with the decision rule.
Reference tools — the book's thinking, on demand
ToolWhat it does
book_outlineSections + chapters + one-line TL;DRs. The map.
get_chapter_summaryA chapter's TL;DR + taglines + read-the-chapter link.
search_principlesKeyword search over the summary corpus; short cited snippets.
handle_objectionMaps skepticism ("async is slow") to the book's reframe.
get_guidanceRole-aware (manager/ic) guidance for a topic.
get_taglinesTaglines + their /q/<slug> quote-card URLs.
Resources
  • book://outline — sections, chapters, TL;DRs (JSON)
  • book://taglines — taglines + quote-card URLs (JSON)
  • book://about — what this server is, what it does and doesn't contain, and where to get the book
Prompts

Invoke these directly from your client (e.g. as slash commands):

  • coach — the full method on one situation. Triages sync vs. async, generates the right artifact, enriches with role guidance, and caps with a shareable tagline — one composed deliverable. Stops and recommends a real-time conversation when the situation genuinely needs one.
  • async-standup, write-adr, meeting-to-issue, weekly-update — parameterized templates for a single task.

Good to know

It's a real tool, not a paywall. The method tools work on their own — no book required. The reference tools answer from the book's already-public summaries and a paraphrased framework layer, always capped and always cited so you can trace any snippet to its chapter. The "get the book" link surfaces about once per session, not on every line — it's a tool, not an ad. No verbatim book prose is bundled (the only data file is data/book.json.br), so what you install is genuinely useful, not a teaser.

Staying current. data/book.json.br ships with a version that tracks the book's edition, so the server can tell you which edition it's based on and re-sync when a new one lands.

Generated output is a template, not the author speaking. The method tools format your input into decision docs, standups, and triage calls. That output is generated guidance to adapt — it is not a personal statement, quote, or endorsement by Ben Balter or Open & Async LLC, and shouldn't be presented as one. Reference-tool snippets are summaries the tool cites back to the book, not verbatim prose.

Licensing

This package is split-licensed — see LICENSE for the overview:

  • Code (everything under src/) — MIT.
  • Data (data/book.json.br) — proprietary; © Open & Async LLC. You may use it only as part of running this software. No redistribution as a standalone dataset, no derivative datasets, no model training. See DATA-LICENSE.md.

The full work — the stories, the voice, the complete argument — lives in the book: open-and-async.com.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.