MCP Client Tool icon

MCP Client Tool

Dynamically executes tools from an MCP server based on AI agent input. Fetches tool metadata from /tools and provides dynamic tool definitions for agents.

MCP Client Tool

AI-generated

Summary

Execute a specified tool from an MCP server by invoking its API endpoint with provided parameters, supporting dynamic tool selection and strict parameter validation.

Inputs

  • Endpoint (required) — The MCP server URL, including optional path (e.g., /mcp) for metadata endpoints.
  • Server Transport — Choose the server transport protocol: HTTP (streamable) or deprecated Server Sent Events.
  • Tools to Include — Select which tools to include in execution: all, selected list, or all except selected.
  • Selected Tools — Specify tools to include or exclude when applicable, loaded dynamically from the MCP server.
  • Strict Parameter Validation — Enable to enforce that all required parameters for the chosen tool are provided with exact names.

Output shape

A single-item array containing an object with a 'json' property that includes either the tool execution response or error details.

Output includes 'tool', HTTP method, path, full URL invoked, and the JSON response on success. On error, includes 'error' flag, message, and input causing the failure. Supports multiple input items, each invoking potentially different tools. Requires input JSON to specify at minimum a 'tool' field with optional 'arguments' object matching tool parameters.

Examples

Example 1: Call a specific MCP tool

Set Endpoint to MCP server URL, leave default HTTP transport, set Tools to Include as desired, enable strict validation, provide input JSON with 'tool' and 'arguments' fields matching tool's schema.

Discussion