
Flows
io.github.RBND-studiov1.0.0Updated Sep 29, 2026
Build product adoption your way - Product adoption infrastructure no-code or all-code.
Overview
AI-generated overview
A remote MCP endpoint from Flows for building product adoption experiences, described as no-code or all-code adoption infrastructure.
- What it does
- Flows is a hosted MCP server reachable at a remote endpoint. Its registry description says it provides product adoption infrastructure that can be used no-code or all-code. No tools, packages, or authentication details are declared in the supplied manifest, so the exact assistant-facing capabilities are not documented here.
- When to use it
- Consider it when you want an assistant to work with product adoption tooling from Flows, such as onboarding, in-app guidance, or adoption flows, and you already use or plan to use that platform. Because no tool list is published, confirm the available actions before relying on it.
- Requirements
- A remote MCP client that supports streamable HTTP, plus network access to the Flows endpoint. The manifest declares no authentication, environment variables, or headers, but the provider may still require an account or credentials in practice.
Before you install
The manifest declares no authentication, so verify how access is actually controlled before connecting. No tool list is published, so what the server can read or change is unclear; treat any write, send, or delete behavior as unverified until documented.
Installation
In SourceWeft
- Open Flows in the dashboard and add it to a workspace.
- 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.
Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"flows": {
"type": "http",
"url": "https://api.flows-cloud.com/mcp"
}
}
}Tools
0Tool metadata has not been indexed yet.
Version history
1- v1.0.0LatestSep 29, 2026
