← Registry

Developer Tools

w-flow.tech

Enables querying and editing workflow automations by listing workflows, retrieving node type details, and validating workflow definitions.

1 endpoint10 known toolsFirst detected October 6, 2026Last detected October 6, 2026

ENDPOINT 1

https://w-flow.tech/mcp

No auth detected

MCP server metadata

Name
w-flow
Version
2.0.0
Capabilities
tools
Server instructions

Tools named wflow_* read and build W flow workflows: call wflow_get_reference first, look up node types with wflow_list_node_types / wflow_get_node_type, check with wflow_validate_workflow, then save with wflow_create_workflow or wflow_update_workflow (always the complete workflow). Every other tool runs one of the user's workflows with its arguments as input. A run that takes long answers with a run_id — fetch it with wflow_get_run.

Known tools 10

wflow_get_reference

READ THIS FIRST before writing or changing a workflow.

Inferred read-only
wflow_list_node_types

Search the node catalog (~470 types: triggers, actions, logic, AI, files, feeds, integrations).

Inferred read-only
wflow_get_node_type

Everything about one node type: its settings (keys, types, allowed values, defaults, help), what it outputs (the fields the next node can use in {{placeholders}}) and its output handles.

Inferred read-only
wflow_list_workflows

The workflows this token can see: id, name, description, node count, last change, whether it is offered as a tool, and its link in the editor.

Inferred read-only
wflow_get_workflow

One workflow as JSON (name, description, nodes, edges) plus the validator's findings.

Inferred read-only
wflow_validate_workflow

Check a workflow JSON without saving it: unknown node types, broken edges, wrong branch handles, unknown settings, invalid values, {{placeholders}} nothing before the node outputs.

Inferred read-only
wflow_create_workflow

Save a new workflow in the user's account and return its id and editor link.

Inferred read-only
wflow_update_workflow

Replace a workflow's name, description, nodes and edges with the given JSON (send the COMPLETE workflow, not a patch — read it with wflow_get_workflow first).

Potential side effects
wflow_run_workflow

Run any workflow of this token's scope with an input (it arrives as the trigger's payload, like a webhook body).

Inferred read-only
wflow_get_run

The result of a run that answered with a run_id (still running, or its answer).

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.w-flow]
url = "https://w-flow.tech/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "w-flow": {
      "type": "http",
      "url": "https://w-flow.tech/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: w-flow
Remote MCP URL: https://w-flow.tech/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "w-flow": {
      "url": "https://w-flow.tech/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "w-flow": {
      "type": "http",
      "url": "https://w-flow.tech/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "w-flow",
  "transport": "streamable-http",
  "url": "https://w-flow.tech/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.