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 Resources' operation, it retrieves and outputs a list of available resources from the MCP server. This node is useful for workflows that need to interact with MCP servers to manage or utilize AI model resources, tools, and prompts in real-time or batch processes.
Use Case Examples
- A user wants to fetch and display all available resources from an MCP server to decide which resource to use in subsequent workflow steps.
- A workflow needs to dynamically list resources from the MCP server to automate resource selection and processing.
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. |
Output
JSON
resources- An array of available resources retrieved from the MCP server.
Dependencies
- Requires credentials for MCP client connection depending on the chosen transport type (API keys or command line credentials).
- Depends on MCP SDK client libraries for communication and operations.
Troubleshooting
- Common issues include connection failures due to incorrect credentials or transport configuration.
- Errors may occur if the MCP server is unreachable or if the requested operation is unsupported.
- Tool execution errors may arise from invalid tool names or malformed JSON parameters.
- Timeouts can happen if the MCP server does not respond within the configured timeout period.
Links
- Model Context Protocol Documentation - Official documentation for MCP server and client usage.