Smart MCP Client
Connects to and interacts with an MCP server, discovering capabilities for AI Agents.
Actions8
Overview
This node connects to an MCP (Model Context Protocol) server to retrieve a specific prompt template by its name. It supports two connection types: Command Line (STDIO) and Server-Sent Events (SSE). The node is useful when you want to fetch predefined prompt templates from an MCP server for use in AI workflows or automation scenarios, such as dynamically loading prompt templates for language models or AI agents.
Properties
| Name | Meaning |
|---|---|
| Connection Type | Specifies the transport method to connect to the MCP server, either via command line interface (STDIO) or server-sent events (SSE). This affects how the node communicates with the MCP server. |
| Prompt Name | The exact name of the prompt template to retrieve from the MCP server. This is required to identify which prompt template to fetch. |
Output
JSON
*- The JSON object representing the retrieved prompt template, including all its properties as returned by the MCP server.
Dependencies
- Requires credentials for MCP server connection, either an API key or command configuration depending on the connection type.
Troubleshooting
- Connection errors may occur if the MCP server credentials are missing or incorrect; ensure proper credentials are configured for the selected connection type.
- If the specified prompt name does not exist on the MCP server, the node will throw an error indicating failure to get the prompt; verify the prompt name is correct and available.
- Parsing errors may occur if the MCP server returns unexpected data formats; check server compatibility and node version.
- Transport errors may be logged if the connection to the MCP server is interrupted or misconfigured; review logs for detailed error messages and verify network connectivity.