NodeFox logoNodeFox

Agentic Tool Connectivity

MCP View

Connect workflow steps to MCP-compatible tools and context providers while keeping invocation paths explicit and reviewable. MCP View helps teams expand capability without losing control of where tools are used, what data they receive, and what actions they can trigger.

NodeFox — MCP Servers

MCP Servers

Bridge • 11 tools
  • GitHub MCP
    RemoteOn
  • Postgres MCP
    RemoteOn
  • Filesystem
    LocalConnecting…
  • Slack MCP
    RemoteOn
  • Stripe MCP
    RemoteOff

GitHub MCP

Remotehttps://mcp.nodefox.ai/github/sse

Available Tools

(4 of 4 enabled)
list_repos
create_issue
open_pull_request
get_file_contents
Ready · awaiting tool call
NodeFox — MCP Servers

MCP Servers

Bridge • 11 tools
  • GitHub MCP
    RemoteOn
  • Postgres MCP
    RemoteOn

Add New MCP Server

Configure a new Model Context Protocol server

Server Information

GitHub MCP
Remote (SSE / HTTP)
Connect to a hosted MCP server
Local (stdio)
Run a local command via Bridge
e.g., https://api.example.com/mcp
Authentication & Headers
Authorization
••••••••

Standardized tool access for agentic workflows

MCP reduces one-off integration friction. NodeFox lets teams compose MCP usage inside deterministic graphs so model calls, tool actions, and fallback behavior stay observable and governable in production.

NodeFox — MCP Servers

MCP Servers

Bridge • 14 tools
Stripe MCPRemote

Available Tools

(3 of 4 enabled)

Uncheck tools to hide them from the AI during runs.

get_customer
list_charges
create_refundapproval
delete_customer

Invocation Trace

Control where and how tools are used

Pair MCP actions with Decision nodes, schema checks, and approval gates so tool-enabled steps remain policy-aware. This gives teams practical guardrails when workflows can perform external writes, account mutations, or other high-impact operations.

Build practical agentic systems

Use MCP connectivity with explicit workflow controls to balance capability and safety. Keep tool usage scoped, explainable, and reviewable across technical and non-technical stakeholders.