Flows

io.github.RBND-studioPublished by GitHub account RBND-studiov1.0.0Updated Oct 24, 2026

Build product adoption your way - Product adoption infrastructure no-code or all-code.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Flows is a remote MCP endpoint for product adoption infrastructure, letting an assistant work with adoption flows through a hosted service.

What you can do
Connect an assistant to a hosted product adoption platform described as no-code or all-code infrastructure. The manifest lists no tools, so the specific actions available are not documented here. The service is reached over a remote HTTP endpoint rather than a local package.
When to use it
Consider it when you want an assistant to work with product adoption flows hosted on this vendor's cloud platform, and you already use or plan to use that service.
Requirements
A remote connection to the provider's hosted endpoint. OAuth authentication is required. No environment variables, headers or local packages are declared.
Before you install
OAuth grants the assistant access to your account on the provider's platform; review the scopes requested before authorizing. The tool list is not published, so what it can read or change is unclear. Data is handled by the third-party hosted service.

Installation

In SourceWeft

  1. Open Flows 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.github.RBND-studio%2Fflows/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": {
    "flows": {
      "type": "http",
      "url": "https://api.flows-cloud.com/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 29, 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.