Claude Code: Automating Async Workflows with MCP

Async communication is usually a mess of long Slack threads and redundant meetings because most people don't know how to document decisions properly. The "Open and Async Advisor" MCP server attempts to solve this by turning remote-work frameworks into executable tools that an LLM agent can trigger.

Instead of reading a handbook on remote work and trying to apply it manually, this server lets you pipe your chaotic meeting notes or draft updates directly into a set of specialized tools that enforce async best practices.

Installation and Setup

To integrate this into Claude Code or any MCP-compatible client, run the following command in your terminal:

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

Deep Dive: Available Tools and Real-World Use

This isn't just a knowledge base; it's a set of functional utilities. Here is how the specific tools operate within an AI workflow:

• convert_meeting_to_async: This is the most practical tool in the kit. You can feed it a transcript or a rough set of meeting notes, and it rewrites the content into an async-first format (clear action items, documented context, and specific asks) so you can cancel the next follow-up meeting.
• draft_decision_doc: When a team is circling a problem in a chat thread, this tool helps the LLM structure a formal decision document. It forces the "Why," the "Alternatives Considered," and the "Final Verdict," which prevents the same argument from resurfacing three months later.
• score_status_update: This acts as a quality gate for your internal updates. It analyzes a status report and gives it a score based on clarity and signal-to-noise ratio, suggesting edits to make the update more useful for stakeholders.
• triage_sync_vs_async: You can input a proposed agenda, and the tool determines if the topic actually requires a live conversation or if it can be handled via a shared document.

Practical Example: Converting a Sync Thread

If you have a messy Slack conversation where a decision was vaguely reached, you can now prompt your agent:

"Use the convert_meeting_to_async tool on the following chat log and then use draft_decision_doc to formalize the outcome for the engineering team."

The result is a shift from "we talked about this" to a permanent, searchable record.

Performance Analysis: MCP vs. Standard Prompting

I compared using these specialized tools against simply asking Claude 3.5 Sonnet to "make this async" using standard prompt engineering.

• Consistency: Standard prompting often results in a "polite summary." The MCP tools enforce a specific structural rigor (e.g., the decision doc template) that doesn't drift over long conversations.
• Context Window: Because the logic is handled by the MCP server, you don't have to paste a 2,000-word "Async Guide" into your system prompt every time you start a new session.
• Precision: The score_status_update tool provides a quantitative check that is much more objective than asking an LLM "does this look okay?"

For anyone building an LLM agent-based workflow for team management, moving these "soft skill" frameworks into MCP servers is the right move. It transforms a static PDF of "best practices" into a live deployment of operational efficiency.