# FlowDot [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/flowdot-llc/mcp-server  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/flowdot

## Description
Build and run AI workflows, apps, toolkits and knowledge bases on FlowDot from any MCP client.

## Tools
Capabilities this server exposes over MCP:

- **list_workflows** — List all workflows accessible to the authenticated user
- **execute_workflow** — Execute a workflow with optional inputs (sync or async)
- **get_execution_status** — Get the status and results of a workflow execution
- **agent_chat** — Chat with the FlowDot AI agent for workflow assistance
- **get_workflow_metrics** — Impressions, success/failure rates, average duration
- **get_workflow_comments** — Comments and ratings on workflows
- **get_execution_history** — Past execution history with timestamps and status
- **get_workflow_details** — Detailed workflow info including nodes, connections, signature
- **get_workflow_inputs_schema** — Input schema with expected types and required fields
- **duplicate_workflow** — Create a copy of an existing workflow
- **toggle_workflow_public** — Make a workflow public or private
- **favorite_workflow** — Add/remove workflow from favorites
- **cancel_execution** — Cancel running/pending workflow executions
- **retry_execution** — Retry failed executions with the same inputs
- **stream_execution** — Real-time SSE streaming of workflow execution
- **get_workflow_tags** — Get tags associated with a workflow
- **set_workflow_tags** — Set/update workflow tags
- **search_workflows** — Search workflows by name, description, tags
- **search** — Unified search across workflows, apps, custom nodes
- **get_public_workflows** — Browse public workflows shared by other users
- **create_workflow** — Create a new empty workflow
- **delete_workflow** — Permanently delete a workflow
- **get_workflow_graph** — Get complete graph structure (all nodes + connections)
- **validate_workflow** — Validate for missing connections, invalid config, disconnected nodes
- **list_available_nodes** — List all node types organized by category
- **get_node_schema** — Full schema for a node type (inputs, outputs, properties)
- **add_node** — Add new node (built-in or custom via `custom_node_{hash}`)
- **update_node** — Update node position or properties
- **delete_node** — Delete node and all its connections
- **add_connection** — Connect a node output to a node input
- **delete_connection** — Remove a connection between two nodes
- **get_node_connections** — Get all connections to/from a specific node
- **list_custom_nodes** — List your custom nodes with search/category filtering
- **search_public_custom_nodes** — Search public nodes shared by the community
- **get_custom_node** — Detailed custom node info (inputs, outputs, script code)
- **get_custom_node_comments** — Comments and ratings on a custom node
- **get_custom_node_template** — Generate a working script template based on I/O definitions
- **create_custom_node** — Create new custom node with script, inputs, outputs (validated with AST parsing)
- **update_custom_node** — Update name, description, code, properties
- **delete_custom_node** — Permanently delete a custom node
- **copy_custom_node** — Copy a public node to your library
- **toggle_custom_node_visibility** — Change visibility (private/public/unlisted)
- **vote_custom_node** — Upvote/downvote/remove vote
- **favorite_custom_node** — Add/remove from favorites
- **add_custom_node_comment** — Add comment or reply
- **list_apps** — List your React frontend apps
- **search_apps** — Search the public app marketplace
- **get_app** — Detailed app info including React code and linked workflows
- **create_app** — Create a new React app (Tailwind + React 18, sandboxed)
- **update_app** — Update name, description, code, config, mobile settings
- **delete_app** — Permanently delete app
- **publish_app** — Publish to the public marketplace
- **unpublish_app** — Make a published app private
- **clone_app** — Clone a public app to your library
- **link_app_workflow** — Link a workflow to an app for `invokeWorkflow()` use
- **unlink_app_workflow** — Unlink a workflow from an app
- **link_app_toolkit** — Link a toolkit to an app for `invokeTool()` use
- **unlink_app_toolkit** — Unlink a toolkit from an app
- **get_app_template** — Get starter code templates (basic, chat, dashboard, form-builder, data-viewer)
- **edit_app_code** — Find/replace specific strings in app code
- **append_app_code** — Append content before the closing brace
- **prepend_app_code** — Prepend content to the start
- **insert_app_code** — Insert content after a specific pattern match
- **list_app_files** — List all files in a multi-file app
- **get_app_file** — Get content of a specific file
- **create_app_file** — Create new file (jsx, js, ts, tsx, css, json, md)
- **update_app_file** — Update file content and type
- **delete_app_file** — Delete a file
- **rename_app_file** — Rename or move a file
- **set_app_entry_file** — Set a file as the app's entry point
- **get_workflow_public_url** — Public shareable URL for a workflow
- **list_shared_results** — Shared execution results for a workflow
- **get_shared_result** — Specific shared result with outputs/inputs
- **get_shared_result_comments** — Comments on a shared result
- **create_shared_result** — Create a shareable link (with optional expiry)
- **add_workflow_comment** — Comment on a workflow
- **add_shared_result_comment** — Comment on a shared result
- **vote_workflow** — Upvote/downvote a workflow
- **vote_shared_result** — Upvote/downvote a shared result
- **list_input_presets** — Pre-configured input sets for a workflow

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "flowdot": {
    "command": "npx",
    "args": ["-y","@flowdot.ai/mcp-server"],
    "env": {
      "FLOWDOT_API_TOKEN": ""
    }
  }
}
```

**Requires environment variables:** `FLOWDOT_API_TOKEN` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What the FlowDot MCP server does

FlowDot MCP server exposes FlowDot’s workflow platform to AI clients that support the Model Context Protocol. Agents can find workflows, inspect their details and input schemas, create new workflows, modify graph structure, validate configurations, and execute workflows with optional inputs.

The available operations also cover execution oversight and workflow collaboration. An agent can retrieve execution results and history, stream live execution events over SSE, cancel pending or active runs, retry failed runs, and review workflow metrics, comments, ratings, tags, favorites, and public visibility. Search tools cover workflows and other FlowDot resources such as apps and custom nodes.

The README describes a broader platform interface with 150 tools in 17 categories. In addition to workflows, those categories include custom nodes, React-based apps, agent recipes, knowledge bases, agent toolkits, agent characters for voice calls, and community sharing. The tool list supplied for this listing focuses on workflow and node operations.

## How it works

An MCP client starts the server locally and communicates with it through the configured command. The server authenticates requests with a FlowDot token, then exposes FlowDot actions as callable MCP tools. Clients can first inspect available node types and individual node schemas, create or retrieve a workflow graph, add or update nodes, connect node inputs and outputs, and run validation before execution.

Execution can be synchronous or asynchronous. Asynchronous runs can be checked with status and history tools, followed through real-time SSE streaming, cancelled, or retried with the original inputs. Workflow discovery can use names, descriptions, tags, public listings, or unified search.

The server also provides eight educational `learn://` resources covering FlowDot concepts such as workflows, recipes, custom nodes, apps, toolkits, knowledge bases, and agent characters. These resources can be read through the MCP resource interface before calling tools.

## Setup and configuration

Create a FlowDot account and generate an MCP token from the MCP Tokens settings. The token begins with `fd_mcp_`; scopes can be selected when the token is created. Provide it to the client as the `FLOWDOT_API_TOKEN` environment variable.

For Claude Code, the documented setup uses `claude mcp add` with `npx -y @flowdot.ai/mcp-server`. Other clients can launch the package with `npx`, install it globally with npm, or use the Claude Desktop `.mcpb` extension bundle. After changing configuration, restart the client so it loads the server. Claude Code uses the configuration on its next session.

The free plan is documented as including five workflow runs per day and ten toolkit calls per day. The README also lists a Creator plan with monthly and daily limits; current plan details should be checked on FlowDot’s site.

## Tools and capabilities

The FlowDot MCP server includes tools for:

- Listing, searching, inspecting, duplicating, tagging, favoriting, publishing, and deleting workflows.
- Creating workflow graphs and adding, updating, deleting, and connecting nodes.
- Reading node types and full node schemas, including inputs, outputs, and properties.
- Validating workflows for disconnected nodes, missing connections, and invalid configuration.
- Executing, streaming, monitoring, cancelling, and retrying workflow runs.
- Reviewing execution history, metrics, comments, and ratings.
- Managing custom nodes, including creation, script updates, visibility, community discovery, and comments.
- Creating and editing FlowDot React apps and linking them to workflows or toolkits, as described in the README.

## Limitations and notes

Recipes can be designed through MCP but are not executed by the MCP server according to the README. Their execution requires the FlowDot CLI because recipes are long-running agentic programs that may exceed AI client timeouts and need local file, code, or shell access.

Destructive operations such as deleting workflows, nodes, custom nodes, or apps should be used carefully. The supplied material does not document a local workflow file format, offline mode, or client-specific permission behavior. Token scopes are selectable during token creation, so the available operations depend on the permissions granted to the token.

_Full upstream README: https://allmcps.com/mcp/flowdot/readme_