FlowNode

io.flownodePublished by flownode.ioOfficial publisherv1.0.0Updated Oct 24, 2026

Generate images, video, audio and 3D with FlowNode; results land in your asset library.

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

FlowNode is a remote MCP server that lets an assistant generate images, video, audio and 3D content, with results saved to your asset library.

What you can do
Generate images, video, audio and 3D content from assistant prompts through FlowNode's hosted service. Results are placed in your FlowNode asset library rather than returned only inline. The manifest lists no individual tools, so the exact generation options and parameters are not documented here.
When to use it
Use it when you want an assistant to produce visual, audio or 3D media and keep the outputs organized in a hosted asset library, without running any local software.
Requirements
A remote MCP connection to the FlowNode endpoint over streamable HTTP, plus OAuth sign-in to a FlowNode account. No local runtime, packages, environment variables or headers are declared.
Before you install
OAuth grants the server access to your FlowNode account, and generation may consume paid credits or quota depending on your plan; the input does not state pricing. Prompts and generated content are sent to FlowNode's hosted service. Review what account access the OAuth consent requests before connecting.

Installation

In SourceWeft

  1. Open FlowNode 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.flownode%2Fflownode/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": {
    "flownode": {
      "type": "http",
      "url": "https://mcp.flownode.io/"
    }
  }
}

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.