AsyncFlow

om.async由 async.om 发布官方发布者v4.5.0更新于 Oct 30, 2026

Manage AsyncFlow tickets: find, read, create, update, assign, move, link, archive and attach files.

已验证Streamable HTTP可网页运行效率与工作流沟通与协作

服务详情

标识符: om.async/asyncflow
传输: Streamable HTTP
运行时: Web executable
信任: Verified
发布于: Oct 30, 2026

安全提示

MCP 服务会接收对话中的工具调用请求，并可能执行外部操作。启用前请先了解该服务能做什么，并只授予它所需的权限。

注册中心已验证此服务的命名空间属于 async.om，且该域名同时运行其端点。这可以确认发布者，但并不代表该服务的工具是安全的。

SourceWeft 的检查只涵盖条目是否完整、端点是否响应；不审查服务器的代码，也不审查其工具的行为。

在 README 中添加徽章

向读者展示该 MCP 服务已收录于 SourceWeft，徽章链接到本页。

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/om.async%2Fasyncflow.svg)](https://sourceweft.com/mcp/om.async%2Fasyncflow?utm_source=readme&utm_medium=badge)

概览

AI 生成的概览

远程 AsyncFlow 连接器，让助手在公司工作区中搜索、读取、创建、更新、指派、评论和归档工单。

可以做什么: 查看公司及其工作区，确认当前连接以谁的身份操作
按看板筛选条件搜索和读取工单，查看工单详情、历史、工作区摘要和图片附件
创建和更新工单、指派、流转状态、建立或解除关联，并申请或审批
记录工时，上传、附加和移除文件，归档、恢复及列出已归档工单
添加评论，可附带文件
适用场景: 适合在 AI 对话中处理团队的 AsyncFlow 工单，而不必打开网页端：分诊、查历史、提交新工单、修改字段或发表评论，范围限于登录时授予的权限。
运行要求: 通过 streamable HTTP 加 OAuth 连接的远程 MCP 端点，无需本地安装。需在浏览器中登录，选择公司并勾选允许的权限。客户端须支持带 OAuth 的远程 MCP；ChatGPT 需要允许自定义连接器的套餐，部分客户端还需由服务方将重定向或回调地址加入白名单。

安装前请注意

该连接可以写入：创建和更新工单、指派与流转、关联、记录工时、上传和移除附件、归档与恢复、发表评论。权限受登录时勾选的访问范围和你在各工作区的角色限制，对话无法删除任何内容。AsyncFlow 密码不会传给对话；可随时在“设置 → 已连接的应用”中断开。

安装

在 SourceWeft 中

打开控制台中的 AsyncFlow，将其添加到工作区。
连接所需的凭据。它们会被私密存储，绝不会在公开页面上展示。
为需要使用其工具的对话启用该服务。

Web executable，通过 Streamable HTTP。远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/om.async%2Fasyncflow/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。客户端会在首次连接时完成 OAuth 登录。

{
  "mcpServers": {
    "asyncflow": {
      "type": "http",
      "url": "https://flow.async.om/api/mcp"
    }
  }
}

README

AsyncFlow connector

Use your AsyncFlow tickets from an AI chat. You can search, open, create, update, assign, move and comment on tickets in your own company, with the access you choose when you connect.

The connector address is:

When you connect, a browser opens. Sign in to AsyncFlow, pick the company and tick the access to allow. Nothing is installed on your computer, and your AsyncFlow password never reaches the chat. You can disconnect a chat at any time in AsyncFlow under Settings → Connected apps.

Claude Code

Install the plugin. It sets up the connector and adds a skill that tells Claude how to work with tickets safely.

Then run /mcp, choose asyncflow and sign in.

To add only the connector, without the skill:

Claude (web and desktop)

Settings → Connectors → Add custom connector. Name it AsyncFlow and paste the address above.

ChatGPT

Add a custom connector in ChatGPT's settings and paste the address above. This needs a plan that allows custom connectors.

Cursor

Add this to ~/.cursor/mcp.json:

VS Code

Other chats

Any client that supports remote MCP servers over streamable HTTP with OAuth can connect. If the chat says its redirect address isn't allowed, send that address to Async Solution and it will be added.

What the chat can do

Access	What the chat can do
See the company and its workspaces	`whoami`, `list_projects`
Read tickets you can already read	`list_ticket_options`, `search_tickets` (board filters: created or resolved dates, due, assigned to me, SLA and more), `get_tickets`, `get_ticket`, `get_ticket_history`, `workspace_summary`, `get_attachment` (images are shown to the chat)
Create and manage tickets	`create_ticket`, `update_ticket` (any field, parent), `assign_ticket`, `transition_ticket`, `link_tickets`, `unlink_tickets`, `request_approval`, `decide_approval`, `log_time`, `upload_attachment`, `start_upload`, `attach_file`, `remove_attachment`, `archive_tickets`, `restore_tickets`, `list_archived_tickets`
Add comments	`add_comment` (with files)

Your role in each workspace still applies, and the chat can't delete anything. Due dates and other planning fields stay visible to the delivery team only.

Microsoft Teams and Microsoft 365 Copilot

In Copilot Studio, create an agent, add a tool of type Model Context Protocol with the address above and OAuth 2.0, dynamic discovery, and publish it to the Teams and Microsoft 365 Copilot channel. Copilot Studio shows a callback URL: send it to Async Solution so it can be allowed.