MCP Client Tool

Node catalog Artificial intelligence

On this page

Call tools on an MCP server

Usage and specifics

Create an MCP credential with server URL and optional key. toolName or toolsFilter selects tools; approval rules apply to their calls.

Technical type : ai_tool_mcp_client. Runtime : nodulz.

Credentials and prerequisites

Create and configure the credential : mcp

Create credentials in your nodulz instance’s Credentials area, then select them on the node. Availability depends on ownership and sharing. See the credentials guide for access and rotation.

Parameters

Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.

Parameter	Type	Default	Values / limits
`name`	`string`	`"mcp"`	-
`description`	`string`	`"Call MCP server tools"`	-
`credentialId`	`string`	-	-
`toolName`	`string`	`""`	-
`toolsFilter`	`string`	`""`	-
`requireApproval`	`boolean`	`false`	-

Initial configuration

Initial catalog configuration example, to adapt before running. Keep secrets in credentials.

json

{
  "name": "mcp",
  "description": "Call MCP server tools",
  "toolName": "",
  "toolsFilter": "",
  "requireApproval": false
}

Verification

Test with representative data. Check node output in the inspector and logs, then use editor mapping for downstream fields. A trigger test with a simulated payload does not validate external service delivery.