NOVA CLI reference 0.5.0 GitHub
  1. nova
  2. nova flow

nova flow mcp

Serve NovaFlow's MCP server (flow authoring) over stdio

Synopsis

Serve the MCP server of NovaFlow on the cell over stdio, for MCP clients that start a local command (Claude Code, Cursor, …).

NovaFlow's control plane has an MCP endpoint for authoring flows (behavior trees): the action catalog, the tree schema, validation, and reading and saving flows. It is an HTTP endpoint behind the instance login, and portal logins expire after a day. 'nova flow mcp' forwards every message to it with a fresh login, so a client set up once keeps working:

claude mcp add novaflow -- nova flow mcp

The instance is resolved when the client starts the server (--instance, NOVA_INSTANCE or the selected instance); pin one with 'claude mcp add novaflow -- nova flow mcp --instance <name>'. Log in with 'nova login' first: the server never starts an interactive login. NovaFlow must be installed on the cell, version 2026.9 or newer ('nova flow status').

The server runs until stdin ends. Batches are split into single messages, and every request gets one answer: failures (login, network, HTTP) come back as JSON-RPC errors.

--print shows the endpoint and the command to register the server instead.

Instance tools (cells, controllers, motion) are served by 'nova mcp'; both can be registered side by side.

nova flow mcp [flags]

Examples

  claude mcp add novaflow -- nova flow mcp
  claude mcp add novaflow-lab -- nova flow mcp --instance lab
  nova flow mcp --print

Options

  -h, --help    help for mcp
      --print   Print the endpoint and the command to register the server instead of serving it

Options inherited from parent commands

      --debug                      Write diagnostic output to stderr: HTTP requests and responses, external commands, the resolved instance. Known secrets are redacted, but bodies (app environments, kubeconfigs) can still contain some: don't share the output unreviewed (env: NOVA_DEBUG=1)
      --env string                 (Wandelbots internal) Portal environment for this invocation: prod, stg or dev (default: the environment of the cloud instance, else of the last 'nova login'; env: NOVA_ENV)
      --insecure-skip-tls-verify   If true, the server's certificate will not be checked for validity (disables TLS verification for all requests)
      --instance string            Name of the instance to work against for this invocation (overrides the selected instance; env: NOVA_INSTANCE)
  -y, --yes                        Answer yes to questions, e.g. to install NovaFlow when it is missing

SEE ALSO

  • nova flow - Manage NovaFlow and its flows on the current cell