MCP Client EnhancedInstall

Overview

This node, "MCP Client Enhanced," connects to an MCP (Model Context Protocol) server using one of several transport protocols and performs various operations related to resources, prompts, and tools managed by the MCP server. It supports multi-tenant environments, smart prompts, and enterprise features.

The List Resource Templates operation retrieves a list of available resource templates from the MCP server. This is useful when you want to discover or enumerate predefined resource templates that can be used or referenced in your workflows.

Common scenarios:

• Automating discovery of resource templates for dynamic workflow configuration.
• Integrating with MCP servers to fetch metadata about resource templates before processing or creating resources.
• Building dashboards or monitoring tools that display available resource templates.

Example:
You might use this node to fetch all resource templates and then iterate over them to create or update resources based on those templates dynamically.

Properties

Output

The output JSON contains a single field:

• resourceTemplates: An array of resource template objects retrieved from the MCP server. Each object represents a resource template available for use or reference.

Example output structure:

{
  "resourceTemplates": [
    {
      // resource template details here
    },
    {
      // another resource template
    }
  ]
}

No binary data output is produced by this operation.

Dependencies

• Requires connection credentials to the MCP server, which vary depending on the selected connection type:
  • For Command Line (STDIO): A command and arguments to run the MCP client locally.
  • For HTTP Streamable: URL endpoints and optional headers for HTTP streaming.
  • For Server-Sent Events (SSE): URL endpoints and optional headers (deprecated).
• The node uses the MCP SDK client libraries internally to communicate with the MCP server.
• Environment variables starting with MCP_ may be used to configure the environment for the command line transport.
• Proper API keys or authentication tokens must be configured in the credentials for secure access.

Troubleshooting

• Connection errors: If the node fails to connect to the MCP server, verify that the credentials are correct and that the server is reachable via the chosen transport protocol.
• Timeouts: The node has configurable timeouts; if operations take too long, consider increasing the timeout values in the credentials.
• No transport available: Ensure that the appropriate credentials are set for the selected connection type.
• Empty or missing resource templates: If no resource templates are returned, confirm that the MCP server actually has resource templates available and that the user account has permission to list them.
• Deprecated SSE transport: Avoid using the SSE option as it is deprecated; prefer HTTP Streamable for real-time communication.
• Invalid JSON errors: Not applicable for this operation but relevant for other operations involving JSON parameters.

Links and References

• Model Context Protocol (MCP) Documentation
• n8n Custom Node Development
• Zod Schema Validation Library (used internally for schema validation)