MCP Client icon

MCP Client

Use MCP client
Join our community

Actions7

Overview

This node connects to an MCP (Model Context Protocol) server using one of three transport types: Command Line (STDIO), Server-Sent Events (SSE), or HTTP Streamable. It performs various operations related to MCP resources, tools, and prompts. Specifically, for the 'List Resource Templates' operation, it retrieves and outputs a list of available resource templates from the MCP server. This node is useful for workflows that need to dynamically access and manage resource templates within the MCP ecosystem, such as automation of resource management or integration with other systems.

Use Case Examples

  1. A user wants to fetch all available resource templates from an MCP server to display them in a dashboard.
  2. An automation workflow needs to list resource templates to decide which template to apply for a new resource creation process.

Properties

Name Meaning
Connection Type Selects the transport protocol to connect to the MCP server. Options include Command Line (STDIO), Server-Sent Events (SSE) (deprecated), and HTTP Streamable (recommended for real-time communication). Default is Command Line (STDIO).

Output

JSON

  • resourceTemplates - An array containing the list of available resource templates retrieved from the MCP server.

Dependencies

  • Requires credentials for MCP client connection depending on the chosen transport type: an API key or command configuration for Command Line, SSE URL and headers for SSE, or HTTP stream URL and headers for HTTP Streamable.

Troubleshooting

  • If the node fails to connect, verify the credentials and connection parameters for the selected transport type.
  • Errors like 'No transport available' indicate missing or misconfigured connection credentials.
  • Parsing errors for tool parameters indicate invalid JSON input; ensure parameters are correctly formatted JSON objects.
  • If no tools or resources are found, check the MCP server availability and permissions.

Links

Discussion