13FLOW MCP Server

What the code does

We read the source, 2 h ago · tools taken from the live server · rules 3dff92dd89df

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

  const result = spawnSync(process.execPath, [server], {

            cpath = os.path.join(cache_dir, f"confluence-{window}.json")

  document.getElementById("buys").innerHTML = buys.rows.length? buys.rows.map(r=>`

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

runuser -u flowmcp -- /usr/bin/node --input-type=module -e '

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

claude mcp add 13flow --transport http https://13flow.eu/api/mcp

{
  "mcpServers": {
    "13flow": {
      "url": "https://13flow.eu/api/mcp"
    }
  }
}

[mcp_servers.13flow]
url = "https://13flow.eu/api/mcp"

{
  "mcpServers": {
    "13flow": {
      "url": "https://13flow.eu/api/mcp"
    }
  }
}

{
  "mcpServers": {
    "13flow": {
      "url": "https://13flow.eu/api/mcp"
    }
  }
}

Available tools 13

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

Endpoints