MCP Client icon

MCP Client

Use MCP client
Join our community

Actions7

Overview

This node connects to an MCP (Model Context Protocol) server to perform various operations related to tools, prompts, and resources. Specifically, for the 'List Tools' operation, it retrieves a list of available tools from the MCP server. This node supports multiple connection types including Command Line (STDIO), Server-Sent Events (SSE), and HTTP Streamable protocols. It is useful in scenarios where users want to dynamically fetch and interact with tools provided by an MCP server, such as in AI or automation workflows.

Use Case Examples

  1. Fetching a list of AI tools available on an MCP server to display in a UI.
  2. Integrating with an MCP server to dynamically select and execute tools based on user input.
  3. Automating workflows that require querying available resources and tools from an MCP server.

Properties

Name Meaning
Connection Type Selects the transport protocol to connect to the MCP server. Options include Command Line (STDIO), Server-Sent Events (deprecated), and HTTP Streamable.

Output

JSON

  • tools - An array of available tools retrieved from the MCP server. Each tool object contains 'name', 'description', and 'schema' properties describing the tool and its input schema.

Dependencies

  • Requires credentials for MCP client connection depending on the selected connection type (e.g., API keys or command line credentials).
  • Uses external MCP SDK packages for client communication and tool handling.

Troubleshooting

  • Common issues include connection failures due to incorrect credentials or network issues. The node throws errors if it cannot connect to the MCP server or if no tools are found.
  • Errors parsing tool parameters if provided in an invalid JSON format.
  • If the selected connection type is not supported or credentials are missing, the node will fail to initialize the transport.
  • Warnings are logged if no tools are found in the MCP client response.

Links

Discussion