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 using either a command line (STDIO) or Server-Sent Events (SSE) transport. It allows users to list available resources, tools, prompts, and resource templates on the MCP server. Specifically, the 'List Resources' operation fetches and returns all available resources from the MCP server. This node is useful for discovering and interacting with AI agent capabilities, managing resources, and integrating external AI tools and prompts. For example, it can be used to dynamically retrieve resource metadata for further processing or automation workflows.
Properties
| Name | Meaning |
|---|---|
| Connection Type | Selects the transport method to connect to the MCP server. Options are 'Command Line (STDIO)' for local command execution or 'Server-Sent Events (SSE)' for event-driven HTTP connection. |
Output
JSON
resources- An array of resource objects available on the MCP server, each containing metadata such as name, description, and URI.
Dependencies
- Requires credentials for MCP client connection, either an API key or command configuration depending on the connection type.
- Uses '@modelcontextprotocol/sdk' packages for MCP client communication.
- Environment variables prefixed with 'MCP_' can be used to configure the command line environment.
Troubleshooting
- Connection errors may occur if credentials are missing or incorrect; ensure proper API keys or command configurations are set.
- If the MCP server is unreachable or the transport type is mismatched, connection attempts will fail with logged errors.
- Malformed or unexpected responses from the MCP server may cause JSON parsing warnings; verify server compatibility.
- Errors during resource listing will be logged and surfaced as node operation errors with detailed messages.
- Ensure the selected connection type matches the available credentials and server capabilities.