Actions7
Overview
This node acts as a client for the Model Context Protocol (MCP) server, enabling interaction with MCP to perform various operations such as listing available prompts, tools, resources, and resource templates, reading specific resources, executing tools, and retrieving prompt templates. It supports multiple connection types including Command Line (STDIO), Server-Sent Events (SSE - deprecated), and HTTP Streamable for real-time communication. This node is useful for workflows that require dynamic access to MCP-managed AI tools, prompts, and resources, facilitating automation and integration of AI capabilities.
Use Case Examples
- Listing all available prompts to dynamically select one for further processing.
- Executing a specific tool with JSON parameters to perform AI-driven tasks within a workflow.
- Retrieving a specific prompt template by name for use in generating AI 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. |
| Operation | Specifies the MCP operation to perform, such as listing prompts, executing tools, or reading resources. |
| Prompt Name | Name of the prompt template to retrieve (used with Get Prompt operation). |
Output
JSON
prompts- Array of available prompt templates returned by the List Prompts operation.
Dependencies
- Requires credentials for MCP client connection depending on the selected connection type (Command Line, SSE, or HTTP Streamable).
- Uses MCP SDK client libraries for communication with MCP server.
Troubleshooting
- Connection errors may occur if credentials or transport configuration are incorrect; verify credentials and connection parameters.
- Tool execution errors may arise if the specified tool does not exist or parameters are invalid; ensure tool name is correct and parameters are valid JSON objects.
- Timeouts can happen especially with HTTP or SSE transports; adjust timeout settings if needed.
- Deprecated SSE transport is discouraged; prefer HTTP Streamable for real-time communication.
Links
- Model Context Protocol Documentation - Official documentation for MCP client and server interactions.