Actions7
Overview
This node acts as a client interface to an MCP (Model Context Protocol) server, allowing users to interact with various resources, prompts, and tools provided by the MCP ecosystem. Specifically, for the "List Resource Templates" operation, it retrieves and outputs a list of available resource templates from the MCP server.
Common scenarios where this node is beneficial include:
- Automating workflows that require fetching metadata about resource templates available on an MCP server.
- Integrating MCP resource templates into larger automation pipelines for AI or data processing tasks.
- Exploring available resource templates dynamically before performing further operations like reading or using those resources.
Practical example:
- A user wants to get all resource templates to display them in a UI or select one for further processing. This node fetches that list directly from the MCP server.
Properties
| Name | Meaning |
|---|---|
| Connection Type | Choose the transport type to connect to MCP server. Options: - Command Line (STDIO) - Server-Sent Events (SSE) |
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 inspection.
Example output structure:
{
"resourceTemplates": [
{
// resource template details here
},
...
]
}
No binary data output is produced by this operation.
Dependencies
- Requires connection to an MCP server via either:
- Command Line interface using STDIO transport, configured with a command and optional arguments.
- Server-Sent Events (SSE) transport, configured with a URL and optional headers.
- Requires appropriate credentials for the chosen connection type (an API key or authentication token).
- Environment variables starting with
MCP_can be used to pass additional environment settings when using the command line transport. - The node depends on the MCP SDK client libraries bundled within the node's code.
Troubleshooting
- Connection errors: If the node fails to connect to the MCP server, verify that the connection type is correctly set and credentials are valid. Check network accessibility and correct URLs or commands.
- Transport errors: Errors related to the transport layer (e.g., SSE or STDIO) will throw descriptive messages. Ensure the MCP server supports the selected transport and that any required headers or environment variables are properly configured.
- Empty or missing resource templates: If no resource templates are returned, confirm that the MCP server has resource templates available and that the user account has permission to access them.
- Operation not supported error: This occurs if an unsupported operation name is passed. Make sure the operation parameter is exactly
"listResourceTemplates"for this functionality.