NodeFoxMCP 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.
Live NodeFox product capture from the live NodeFox application: MCP management surface with server, scope, and tool control context.
Protocol model in NodeFox
NodeFox treats MCP servers as tool providers and applies orchestration controls around them:
- Attach specific MCP servers to specific nodes.
- Restrict exposed tools to the minimum needed.
- Route tool outputs through validation and decision gates.
- 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
Optional configuration:
| Field | Description |
|---|---|
| Command | Executable to start server (npx, node, etc.) |
| Arguments | Startup args for the MCP server |
| Environment Variables | Secrets/config for server process |
Remote HTTP/SSE
- Connect to remotely hosted MCP endpoints
- NodeFox handles protocol compatibility across supported transports
- Best for shared/team-managed tool infrastructure
Optional configuration:
| Field | Description |
|---|---|
| URL | MCP endpoint |
| Headers | Optional auth/custom headers |
Gateway responsibilities
For local/studio operations, 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:
- Validate tool return shapes before downstream writes.
- Bound tool-call count using model/tool limits.
- Separate read-only and mutating tool paths.
- Route high-impact mutations to approval branches.
Functions vs MCP
| Functions | MCP | |
|---|---|---|
| Defined where | In-workspace code | External server |
| Best fit | Domain-specific internal logic | Shared external integrations |
| Typing | TypeScript-style signatures in function definitions | Server-side tool schema/contracts |
| Reuse scope | Workspace-level | Any MCP-compatible client |
Use Functions when logic should live with the workflow. Use MCP when integration capability is shared infrastructure.
Troubleshooting checklist
- Confirm server is enabled.
- Verify auth headers/environment variables.
- Test tool visibility at node attachment.
- Check run logs for timeout or schema mismatch.
- Add explicit fallback routing for tool failures.