Explorium MCP Client icon

Explorium MCP Client

Connect to Explorium Agent Source

Overview

This node connects to the Explorium Model Context Protocol (MCP) server via a Server-Sent Events (SSE) endpoint. It retrieves a list of AI tools available from the MCP server and outputs them for further use in workflows. This node is useful when you want to dynamically fetch and utilize AI-powered tools provided by Explorium’s MCP service, enabling integration with external AI capabilities without manual tool configuration.

Practical examples include:

  • Automatically loading AI tools from Explorium MCP to enrich data processing workflows.
  • Dynamically updating available AI tools in your automation based on the latest offerings from the MCP server.
  • Using the fetched tools as inputs for subsequent nodes that perform AI-driven tasks.

Properties

Name Meaning
Authentication The method used to authenticate with the SSE endpoint. Options: "Header Auth", "None".
Credentials The API key credential used for header authentication. Only shown if "Header Auth" is selected.

Output

The node outputs an array of AI tools under the json output field named "ai_tool". Each item represents a tool retrieved from the MCP server, converted into a dynamic tool format compatible with n8n. These tools can then be invoked or integrated within the workflow.

If the node supports binary data, it is not indicated in the code; thus, only JSON output with tool definitions is provided.

Dependencies

  • Requires access to the Explorium MCP SSE endpoint at https://mcp.explorium.ai/sse.
  • If using header authentication, an API key credential must be configured in n8n and selected in the node.
  • Utilizes utility functions (connectMcpClient, getAllTools, mcpToolToDynamicTool, createCallTool) from bundled dependencies to handle connection and tool transformation.

Troubleshooting

  • Connection failures: If the node cannot connect to the MCP server, ensure the SSE endpoint is reachable and the network allows outgoing connections.
  • Authentication errors: When using header authentication, verify that the API key credential is correctly set up and selected.
  • Empty tool list: If the MCP server returns no tools, check the server status or credentials, as this indicates successful connection but no available tools.
  • Error messages:
    • "HTTP Header Authentication is required": Occurs if header auth is selected but credentials are missing or invalid.
    • "Could not connect to Explorium MCP server.": Indicates failure to establish a connection; check endpoint URL and network.
    • "Explorium MCP Server returned no tools": Connection succeeded but no tools were returned; verify server configuration.

Links and References

Discussion