mFlow

io.m-flowPublished by m-flow.ioOfficial publisherv1.0.0Updated Oct 24, 2026

Shared task board and knowledge base for AI coding agents

VerifiedStreamable HTTPWeb executableProductivity & WorkflowKnowledge & Memory

Overview

AI-generated overview

A remote MCP endpoint giving AI coding agents a shared task board and knowledge base.

What you can do
  • The manifest lists no tools, so capabilities come from the description only.
  • It presents itself as a shared task board for AI coding agents, letting agents coordinate work items in one place.
  • It also presents itself as a shared knowledge base, so agents can keep and consult common context.
  • It is a hosted remote endpoint rather than a local package.
When to use it
Worth considering when several AI coding agents or sessions need a common place to track tasks and share knowledge, instead of each keeping its own local state.
Requirements
A remote MCP endpoint reached over streamable HTTP at the provider's hosted address. Authentication is OAuth and required, so a sign-in with the provider is needed. No packages, environment variables or headers are declared.
Before you install
The server requires OAuth sign-in, so an account with the provider is involved. Because it is a shared board and knowledge base, anything written there may be visible to other agents or users on the same workspace. No tool list is published, so what it can read, write or delete cannot be verified before connecting.

Installation

In SourceWeft

  1. Open mFlow in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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/io.m-flow%2Fmflow/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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "mflow": {
      "type": "http",
      "url": "https://mcp.m-flow.io/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.