Explorium MCP Client icon

Explorium MCP Client

Connect to Explorium Agent Source

Explorium MCP Client

AI-generated

Overview

This node, named "Explorium MCP Client," 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 as dynamic tools for further use in workflows. This node is useful when you want to integrate Explorium's AI-powered tools dynamically into your automation processes, enabling you to leverage external AI capabilities without hardcoding tool definitions.

Practical examples include:

  • Dynamically loading AI tools from Explorium to enrich data processing workflows.
  • Using the retrieved tools to perform AI-driven tasks such as predictions, classifications, or data enrichment within n8n.
  • Automating the integration of new or updated AI tools as they become available on the MCP server without manual updates.

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 object containing a response field, which is an array of dynamic AI tools fetched from the MCP server. Each tool in this array is transformed into a format compatible with n8n's dynamic tool system, allowing subsequent nodes to invoke these tools directly.

Additionally, the output includes a closeFunction, an asynchronous function that can be called to close the connection to the MCP server gracefully.

No binary data output is produced by this node.

Dependencies

  • Requires access to the Explorium MCP SSE endpoint at https://mcp-auth.explorium.ai/sse.
  • If using "Header Auth" authentication, an API key credential must be configured in n8n and provided to the node.
  • Relies on utility functions (connectMcpClient, getAllTools, mcpToolToDynamicTool, createCallTool) imported from a local utils module to handle connection and tool transformation logic.

Troubleshooting

  • Connection failures: If the node cannot connect to the MCP server, ensure the SSE endpoint URL is reachable and the API key credential (if required) is correctly configured.
  • Empty tool list: If the MCP server returns no tools, verify that the server is properly set up and has tools available for retrieval.
  • Authentication errors: When using "Header Auth," missing or invalid API keys will cause authentication failures. Double-check the credentials configuration.
  • Error messages:
    • "HTTP Header Authentication is required": Indicates missing or misconfigured API key credentials.
    • "Could not connect to Explorium MCP server.": Connection to the MCP SSE endpoint failed.
    • "Explorium MCP Server returned no tools": Connection succeeded but no tools were returned.

In all error cases, the node throws detailed errors linked to the specific item index for easier debugging.

Links and References

Discussion