NodeFox

MCP View

Overview

MCP (Model Context Protocol) lets workflows call external tools through a standardized interface. In NodeFox, MCP is integrated as a runtime capability rather than a separate scripting layer.

NodeFox MCP View in NodeFoxNodeFox MCP View in NodeFox

Live NodeFox product capture from the live NodeFox application: MCP management surface with server, scope, and tool control context.

Two directions of MCP integration

Tools used by a workflow: a Conversation step can use selected tools from configured MCP servers. The browser environment connects through its configured gateway; the workflow still needs checks, permissions and explicit approval boundaries around consequential actions.

An external agent using NodeFox: the NodeFox MCP bridge exposes workspace operations such as reading a network, inspecting it, applying supported DSL changes and invoking a run. It connects to the active workspace environment and has its own authentication and write permissions. This does not turn NodeFox into a universally hosted REST service or grant an agent unrestricted system access.

Headless invocation is a separate deployment path. Verify the runner’s supported operations rather than assuming browser MCP and OAuth connections transfer unchanged. See deployment, headless execution and the AI workflow example.

Protocol model in NodeFox

NodeFox treats MCP servers as tool providers and applies orchestration controls around them:

  1. Attach specific MCP servers to specific nodes.
  2. Restrict exposed tools to the minimum needed.
  3. Route tool outputs through validation and decision gates.
  4. Apply fallback branches when tool calls fail or return invalid payloads.

Transport modes

Stdio (local)

  • Process launched locally through Gateway
  • Communication over stdin/stdout
  • Best for local dev tools and local packages

Connection configuration (supply the command or endpoint for the chosen transport):

FieldDescription
CommandExecutable to start server (npx, node, etc.)
ArgumentsStartup args for the MCP server
Environment VariablesSecrets/config for server process

Remote HTTP/SSE

  • Connect through the gateway to remotely hosted MCP endpoints
  • NodeFox handles protocol compatibility across supported transports
  • Best for shared/team-managed tool infrastructure

Connection configuration (supply the command or endpoint for the chosen transport):

FieldDescription
URLMCP endpoint
HeadersOptional auth/custom headers

Gateway responsibilities

For configured MCP connections, the Gateway manages:

  • Process lifecycle
  • Message routing
  • Protocol framing and translation where needed
  • Connectivity diagnostics

See Installation for setup details.

MCP in execution flow

Typical pattern:

Input -> Conversation (MCP tools) -> Decision/Code -> Writer

Recommended controls:

  1. Validate tool return shapes before downstream writes.
  2. Bound tool-call count using model/tool limits.
  3. Separate read-only and mutating tool paths.
  4. Route high-impact mutations to approval branches.

Functions vs MCP

FunctionsMCP
Defined whereIn-workspace codeExternal server
Best fitDomain-specific internal logicShared external integrations
TypingTypeScript-style signatures in function definitionsServer-side tool schema/contracts
Reuse scopeWorkspace-levelAny MCP-compatible client

Use Functions when logic should live with the workflow. Use MCP when integration capability is shared infrastructure.

Troubleshooting checklist

  1. Confirm server is enabled.
  2. Verify auth headers/environment variables.
  3. Test tool visibility at node attachment.
  4. Check run logs for timeout or schema mismatch.
  5. Add explicit fallback routing for tool failures.