AsyncFlow
om.asyncPublished by async.omOfficial publisherv4.5.0Updated Oct 30, 2026
Manage AsyncFlow tickets: find, read, create, update, assign, move, link, archive and attach files.
Overview
Remote AsyncFlow connector that lets an assistant search, read, create, update, assign, comment on and archive tickets in your company's workspaces.
- What you can do
- See the company and its workspaces, and check who the connection is acting as
- Search and read tickets with board filters, view ticket details, history, workspace summaries and image attachments
- Create and update tickets, assign them, move them through transitions, link or unlink them, and request or decide approvals
- Log time, upload, attach and remove files, archive, restore and list archived tickets
- Add comments, including with files
- When to use it
- Useful when you want to work with your team's AsyncFlow tickets from an AI chat instead of the web app: triaging, looking up history, filing new tickets, updating fields or commenting, within the access you grant at sign-in.
- Requirements
- A remote MCP endpoint over streamable HTTP with OAuth; no local install. You sign in through a browser, choose the company and tick the access to allow. Clients must support remote MCP with OAuth; ChatGPT needs a plan that allows custom connectors, and some clients need their redirect or callback address allow-listed by the vendor.
Installation
In SourceWeft
- Open AsyncFlow in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/om.async%2Fasyncflow/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"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
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.
Licence
MIT. This repository only holds the connector setup. The AsyncFlow service is operated by Async Solution.
Source: README.md at commit 1a6542c
Tools
0Version history
1- v4.5.0LatestOct 30, 2026
Score
85% 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 daysRequired25 pts
- Auth declaredRequired10 pts
- 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
Other Async integrations
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.
Open & Async
com.open-and-async
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.