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 operations related to MCP resources, such as reading a specific resource by its URI. The node is useful for workflows that need to retrieve and process data from MCP resources in real-time or batch scenarios. For example, it can be used to fetch configuration data, content, or metadata from an MCP server for further automation or analysis.
Use Case Examples
- Reading a resource by specifying its URI to retrieve its content for processing.
- Using the HTTP Streamable connection type to stream resource data in real-time for live updates.
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. |
| Resource URI | The URI of the specific resource to read from the MCP server. This is required for the Read Resource operation. |
Output
JSON
jsonresource- The content of the resource read from the MCP server, returned as a JSON object.
Dependencies
- Requires credentials for MCP client connection depending on the chosen transport type (command line, SSE, or HTTP).
- Uses MCP client SDK and transport libraries for communication with the MCP server.
Troubleshooting
- Connection errors may occur if the transport credentials are incorrect or the MCP server is unreachable. Verify credentials and network connectivity.
- If the resource URI is invalid or the resource does not exist, the node will throw an error. Ensure the URI is correct and the resource is available on the MCP server.
- Parsing errors may occur if tool parameters are not valid JSON when executing tools (not applicable for Read Resource but relevant for other operations).