MCP Client icon

MCP Client

Use MCP client
Join our community

Actions7

Overview

This node acts as a client for the MCP (Model Context Protocol) server, enabling various operations such as executing tools, listing tools, prompts, resources, and reading specific resources. It supports multiple connection types including Command Line (STDIO), Server-Sent Events (SSE), and HTTP Streamable protocols for real-time communication. The node is useful for integrating MCP server capabilities into workflows, allowing users to execute specific tools with parameters, retrieve prompt templates, and manage resources programmatically.

Use Case Examples

  1. Executing a specific tool on the MCP server by providing the tool name and JSON parameters.
  2. Listing all available tools or prompts from the MCP server to dynamically adapt workflow logic.
  3. Reading a resource by its URI to fetch detailed information from the MCP server.

Properties

Name Meaning
Connection Type Selects the transport protocol to connect to the MCP server (Command Line, SSE, or HTTP Streamable).
Uri Override Overrides the default URL from credentials with a custom URL for SSE or HTTP connections.
Headers Override Additional HTTP headers to send with the request, merged with credential headers, for SSE or HTTP connections.
Tool Name Name of the tool to execute on the MCP server.
Tool Parameters JSON object containing parameters to pass to the tool during execution.

Output

JSON

  • resources - List of resources returned from the MCP server.
  • resourceTemplates - List of resource templates available on the MCP server.
  • resource - Details of a specific resource read by URI.
  • tools - List of available tools with their names, descriptions, and input schemas.
  • result - Result of executing a specific tool with given parameters.
  • prompts - List of available prompt templates.
  • prompt - Details of a specific prompt template retrieved by name.

Dependencies

  • @modelcontextprotocol/sdk

Troubleshooting

  • Ensure the connection type matches the credentials provided; mismatched connection types can cause connection failures.
  • Invalid URI override format will throw an error; verify the URI is correctly formatted.
  • Tool parameters must be valid JSON; parsing errors will prevent tool execution.
  • If the specified tool does not exist on the MCP server, an error listing available tools will be thrown.
  • Transport errors during communication with the MCP server will result in node operation errors; check network and server status.

Links

Discussion