MCP Client icon

MCP Client

Use MCP client
Join our community

Actions7

Overview

This node acts as a client for the Model Context Protocol (MCP) server, enabling interaction with various MCP services such as listing prompts, tools, resources, and executing tools. It supports multiple connection types including Command Line (STDIO), Server-Sent Events (SSE), and HTTP Streamable protocols. The node is useful for workflows that require dynamic access to AI model prompts, tools, and resources managed by an MCP server, allowing automation and integration of AI capabilities.

Use Case Examples

  1. List available AI prompts to dynamically select one for further processing.
  2. Execute a specific AI tool with custom parameters to perform a task.
  3. Retrieve a list of available resources or resource templates from the 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.
Uri Override Overrides the default URL from credentials with a custom URL for SSE or HTTP connection types.
Headers Override Additional HTTP headers to send with the request, specified in NAME=VALUE format separated by newlines. These headers override those from credentials for SSE or HTTP connection types.

Output

JSON

  • prompts - An array of available prompt templates returned by the MCP server when listing prompts.
  • tools - An array of available tools with their names, descriptions, and input schemas returned by the MCP server.
  • resources - An array of available resources returned by the MCP server.
  • resourceTemplates - An array of available resource templates returned by the MCP server.
  • prompt - A specific prompt template retrieved by name from the MCP server.
  • result - The result of executing a specific tool with given parameters.
  • resource - A specific resource read by its URI from the MCP server.

Dependencies

  • Requires credentials for MCP client API depending on the connection type (command line, SSE, or HTTP).
  • Uses external MCP SDK packages for client communication and transport protocols.

Troubleshooting

  • Invalid URI override format: Ensure the URI override parameter is a valid URL when using SSE or HTTP connection types.
  • Transport error: Indicates issues with the underlying transport connection; check network connectivity and credentials.
  • Failed to connect to MCP server: Verify the MCP server is reachable and credentials are correct.
  • No tools found from MCP client: The MCP server returned no tools; verify server configuration and availability.
  • Tool parameters must be a JSON object: Ensure the tool parameters input is valid JSON and correctly formatted.
  • Tool does not exist: The specified tool name is not available on the MCP server; check the list of available tools.

Links

Discussion