FlowRunner Prompt to Flow

ai.flowrunnerPublished by flowrunner.aiOfficial publisherv1.0.0Updated Nov 5, 2026

Describe an automation in plain English and get a working FlowRunner flow with approval steps.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Remote FlowRunner server that turns a plain-English automation description into a working flow with approval steps.

What you can do
  • Generate an automation flow from a natural-language description of what should happen.
  • Include approval steps in the generated flow so a person can sign off before actions run.
  • Work inside the FlowRunner platform, which hosts the resulting flows.
  • No individual tools are listed, so the exact operations are not documented here.
When to use it
Useful when you want to sketch or build a FlowRunner automation quickly by describing it in words instead of assembling steps by hand, especially for workflows that should pause for human approval.
Requirements
A remote MCP endpoint at the FlowRunner app; no local package or runtime is needed. OAuth authentication is required, so a FlowRunner account that can authorize the connection is needed. Network access to the endpoint is required.
Before you install
The connection is authorized through OAuth, granting the server access to your FlowRunner account. Generated flows may perform real actions once run, so review them and their approval steps before enabling or executing them.

Installation

In SourceWeft

  1. Open FlowRunner Prompt to Flow 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/ai.flowrunner%2Fprompt-to-flow/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": {
    "flowrunner-prompt-to-flow": {
      "type": "http",
      "url": "https://app.flowrunner.ai/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.0LatestNov 5, 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.