flow-codeblock-mcp

Flow Codeblock's local stdio MCP Server and Codex Skill. The MCP only invokes the Flow Codeblock Rust REST API and does not execute user JavaScript on the user's computer; user code is still executed by the server-side fixed-version Bun Supervisor.

Installation

Requires Bun 1.4.0 or higher:

bunx --bun flow-codeblock-mcp@0.2.6

Must be configured:

FLOW_CODEBLOCK_BASE_URL=https://qingcode.oalite.com
FLOW_CODEBLOCK_TOKEN=flow_xxx

FLOW_CODEBLOCK_BASE_URL is the address of the deployed Flow Codeblock Rust API. Use https://qingcode.oalite.com for the public service; only when the user has deployed the Rust service on their own machine should you change it to the corresponding localhost address. The token should be configured through the client's environment variables or secrets; do not write it into prompts, tool arguments, or public files.

Related MCP server: Node.js Sandbox MCP Server

General stdio MCP configuration

{
  "mcpServers": {
    "flow-codeblock": {
      "command": "bunx",
      "args": ["--bun", "flow-codeblock-mcp@0.2.6"],
      "env": {
        "FLOW_CODEBLOCK_BASE_URL": "https://qingcode.oalite.com",
        "FLOW_CODEBLOCK_TOKEN": "<YOUR_FLOW_CODEBLOCK_TOKEN>"
      }
    }
  }
}

The npm package contains the MCP runtime source code, the flow-codeblock Skill, AGENT_PROMPT.md, module/danger-mode rules, and the interface documentation Schema. Regular MCP clients do not automatically install the Codex Skill, but flow_write_code directly reads the authoritative rules inside the package, so the full code contract is still available without Skill injection.

Usage constraints

• Call flow_write_code before writing code; in non-script mode read from input.<field>, and in script mode read from input.query/header/body/cookies.

• Before creating or updating a script, you must call flow_preview_script_change, show the preview to the user, and only call flow_apply_script_change after obtaining explicit confirmation.

• Script POST callers submit the business JSON directly; do not wrap it as input or input.body.

• The MCP does not provide a tool for deleting scripts; deletion must be performed by the user via the web page or the REST API.

• Operations proceed with the usual authentication, rate limiting, quota deduction, security checks, statistics, and auditing.