
Open & Async
com.open-and-asyncPublished by open-and-async.comv1.1.0Updated Oct 24, 2026
Draft decision docs, turn meetings into async artifacts, and triage sync vs async in your editor.
The publisher's own server: AsyncFlow
Overview
Local stdio MCP server that gives an assistant tools to draft decision docs, convert meetings to async artifacts, score status updates and triage sync vs async.
- What you can do
- Draft decision docs and convert meetings into async artifacts with an owner and deadline
- Score status-update drafts against a rubric and triage whether a task should be sync or async
- Generate async standup templates and run a composed coaching prompt for a whole situation
- Browse the book's outline, chapter summaries, taglines and role-aware guidance
- Search principles and map objections to reframes, with cited snippets
- When to use it
- Useful for remote or distributed teams that want async-first working practices inside the editor: turning decisions, meetings and status updates into written artifacts, or settling whether something needs a live call.
- Requirements
- Runs as a local process over stdio, typically started with npx from the npm package @open-and-async/mcp, so Node.js is needed unless the one-click desktop bundle is used. No accounts, API keys, environment variables or headers are declared.
Installation
In SourceWeft
- Open Open & Async in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Open and Async — MCP Server
[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
coachprompt 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 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:
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.
The toolbox
Method tools — pure utility, use them on any project
Reference tools — the book's thinking, on demand
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.
Source: README.md at commit 66c777d
Tools
0Version history
4- v1.1.0LatestOct 20, 2026
- v1.0.5Oct 19, 2026
- v1.0.4Oct 19, 2026
- v1.0.1Sep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.
Other Async integrations

AsyncFlow
om.asyncOfficial publisher
Remote AsyncFlow connector that lets an assistant search, read, create, update, assign, comment on and archive tickets in your company's workspaces.

AsyncAPI channel count, body discarded
Published by GitHub account sadri-dridi
A remote MCP endpoint of small utility tools: time, URL and hostname parsing, HTTP status checks, simple validation, and a few index lookups.

Mcp Arangodb Async
Published by GitHub account PCfVW
A local MCP server that gives an AI assistant 46 tools to query, modify, and analyze an ArangoDB database, including graphs and multi-tenancy.