Actions7
Overview
This node acts as a client for the Model Context Protocol (MCP) server, enabling interaction with MCP resources, tools, and prompts. It supports multiple connection types (Command Line STDIO, HTTP Streamable, and deprecated SSE) to communicate with the MCP server. The node is useful for scenarios where users want to list available resource templates, resources, tools, prompts, execute specific tools, or read specific resources from the MCP server. For example, it can be used to fetch a list of resource templates to dynamically configure workflows or execute a tool with specific parameters to automate tasks.
Use Case Examples
- Listing available resource templates to dynamically populate options in a workflow.
- Executing a specific tool on the MCP server with JSON parameters to perform automated processing.
- Fetching a specific prompt template for use in generating content or responses.
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
resourceTemplates- Array of available resource templates retrieved from the MCP server.
Dependencies
- Requires credentials for MCP client connection depending on the selected connection type (command line, SSE, or HTTP).
- Uses MCP SDK client libraries for communication and tool execution.
Troubleshooting
- Common issues include connection failures due to incorrect credentials or server unavailability.
- Errors parsing tool parameters if the JSON is invalid or not an object.
- Errors when executing tools that do not exist or have invalid parameters.
- Timeouts or transport errors depending on the connection type used.
Links
- Model Context Protocol Documentation - Official documentation for MCP server and client usage.