Flowral AI Tools

app.flowral.mcpPublished by mcp.flowral.appOfficial publisherv1.0.2Updated Oct 24, 2026

Streamable HTTP MCP server exposing planner flows, tasks, and squads.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

A remote MCP server that exposes Flowral planner flows, tasks, and squads to an AI assistant.

What you can do
Flowral AI Tools is a remote MCP server reached over streamable HTTP at the provider's endpoint. According to its registry description, it exposes planner flows, tasks, and squads, so an assistant can work with planning content held in Flowral. No individual tools are listed in the available information, so the exact operations are not documented here.
When to use it
Consider it when you use Flowral for planning and want an assistant to reach your flows, tasks, and squads directly instead of copying information between tools. It is less relevant if you do not already keep planning work in Flowral.
Requirements
A remote MCP client that supports streamable HTTP, pointed at the provider's endpoint. Authentication is required and uses OAuth, so you need a Flowral account and must complete the OAuth sign-in flow. No environment variables or headers are declared.
Before you install
Access is granted through OAuth, so review which permissions the sign-in requests before approving it. The description mentions tasks and squads, which suggests the assistant may read or change shared planning data; confirm what it can write before use. No tool list is published, so the exact scope of access is unclear.

Installation

In SourceWeft

  1. Open Flowral AI Tools 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/app.flowral.mcp%2Fplanner/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": {
    "flowral-ai-tools": {
      "type": "http",
      "url": "https://mcp.flowral.app/"
    }
  }
}

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.2LatestSep 16, 2026

Score

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

    Publish an icon in the registry entry.

  • 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.