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 such as listing available prompts, tools, resources, resource templates, reading a specific resource, executing a tool, and retrieving a specific prompt template. This node is useful for integrating MCP server capabilities into workflows, enabling automation of tasks like fetching prompts, executing tools, and managing resources.
Use Case Examples
- Listing all available prompts from the MCP server to dynamically select a prompt for further processing.
- Executing a specific tool on the MCP server with given parameters to perform automated tasks.
- Reading a resource by its URI to retrieve detailed information for use in a workflow.
Properties
| Name | Meaning |
|---|---|
| Connection Type | Choose the transport type to connect to MCP server. Options include Command Line (STDIO), Server-Sent Events (SSE) (deprecated), and HTTP Streamable for real-time communication. |
Output
JSON
prompts- List of available prompts returned by the MCP server when listing prompts.
Dependencies
- Requires credentials for MCP client connection depending on the chosen transport type: an API key or connection details for Command Line, SSE, or HTTP Streamable transport.
Troubleshooting
- Common issues include connection failures due to incorrect or missing credentials, transport errors, or timeouts. Ensure correct credentials are configured for the selected connection type.
- Errors like 'No tools found from MCP client' indicate the MCP server returned no tools; verify the server state and permissions.
- Parsing errors for tool parameters occur if the input is not valid JSON; ensure parameters are correctly formatted JSON objects.
- Operation not supported errors occur if an unsupported operation is selected; verify the operation name is correct and supported by the node.