Explorium Intelligence Conduit via MCP

Leverage verified external datasets to synthesize deep insights on organizations and key personnel.

This repository furnishes the necessary setup definitions for interfacing with Explorium's Model Context Protocol (MCP) endpoint, enabling generative AI agents to query comprehensive business intelligence repositories.

Core Functionality

The Explorium Intelligence Conduit empowers AI agents with on-demand data access, including:

Firmographic Retrieval: Search entities by name, web domain, or identifiers; retrieve detailed corporate profiles.
Personnel Identification: Discover and append verified professional contact details.
Strategic Context: Obtain data on technological infrastructure, investment history, expansion metrics, and corporate milestones.
Data Freshness: Real-time aggregation from a multitude of vetted external sources.
Operational Flow: Effortless embedding of external business context directly into AI-driven processes.

Query any target entity or individual to retrieve data ranging from verified contact vectors (email, phone) to organizational scope, technological footprint, growth indicators, and recent corporate activities. This facilitates superior lead qualification, prospect research, talent mapping, and personalized communication generation—all within the confines of your preferred AI workspace.

Deployment Instructions

Integration Guide: Claude Desktop

#### Remote Endpoint Configuration In Claude Desktop, navigate to `Settings` > `Connectors` > `Add Custom Connector`. Set the name to `ExploriumBI` and provide the remote MCP URL: `https://mcp.explorium.ai/mcp`. #### Local Execution Setup Modify your `claude_desktop_config.json` in the developer settings to include the following server definition. Consult the official [Claude Desktop MCP documentation](https://modelcontextprotocol.io/quickstart/user) for further context. { "mcpServers": { "explorium": { "command": "npx", "args": ["-y", "mcp-remote", "https://mcp.explorium.ai/mcp"] } } }

Integration Guide: Cursor IDE

Access the configuration via: `Settings` -> `Cursor Settings` -> `MCP` -> `Add new global MCP server`. The recommended method involves populating your `~/.cursor/mcp.json` file with this structure. Local project configuration is also supported via `.cursor/mcp.json` in the root. Refer to [Cursor MCP documentation](https://docs.cursor.com/context/model-context-protocol) for detailed instructions. #### Remote Connection Payload { "mcpServers": { "explorium": { "url": "https://mcp.explorium.ai/mcp" } } } #### Local Execution Payload { "mcpServers": { "explorium": { "command": "npx", "args": ["-y", "mcp-remote", "https://mcp.explorium.ai/mcp"] } } }

Integration Guide: Windsurf

Incorporate the necessary stanza into your Windsurf MCP configuration file. Consult [Windsurf MCP documentation](https://docs.windsurf.com/windsurf/cascade/mcp) for path details. #### Remote Server Definition { "mcpServers": { "explorium": { "serverUrl": "https://mcp.explorium.ai/mcp" } } } #### Local Execution Definition { "mcpServers": { "explorium": { "command": "npx", "args": ["-y", "mcp-remote", "https://mcp.explorium.ai/mcp"] } } }

Integration Guide: VS Code

Add the following configuration object to your VS Code MCP settings file. See the [VS Code MCP documentation](https://code.visualstudio.com/docs/copilot/chat/mcp-servers) for precise location. #### VS Code Remote Connection "mcp": { "servers": { "explorium": { "type": "http", "url": "https://mcp.explorium.ai/mcp" } } } #### VS Code Local Execution "mcp": { "servers": { "explorium": { "type": "stdio", "command": "npx", "args": ["-y", "mcp-remote", "https://mcp.explorium.ai/mcp"] } } }

Integration Guide: Zed Editor

Installation is available through the [Zed Extensions Marketplace](https://zed.dev/extensions?query=Explorium), or manually by updating your Zed `settings.json` as follows. Review [Zed Context Server docs](https://zed.dev/docs/assistant/context-servers) for specifics. { "context_servers": { "Explorium": { "command": { "path": "npx", "args": ["-y", "mcp-remote", "https://mcp.explorium.ai/mcp"] }, "settings": {} } } }

Integration Guide: Cline

Explorium is accessible via the [Cline MCP Server Marketplace](https://cline.bot/mcp-marketplace). Follow these steps: 1. Launch **Cline**. 2. Access the main menu (☰) and navigate to **MCP Servers**. 3. Search the **Marketplace** tab for 'Explorium'. 4. Click the **Install** button.

Integration Guide: Roo Code

Configure this connection within your Roo Code MCP settings structure. Consult [Roo Code MCP documentation](https://docs.roocode.com/features/mcp/using-mcp-in-roo) for file location. #### Roo Code Remote Connection { "mcpServers": { "explorium": { "type": "streamable-http", "url": "https://mcp.explorium.ai/mcp" } } } #### Roo Code Local Execution { "mcpServers": { "explorium": { "command": "npx", "args": ["-y", "mcp-remote", "https://mcp.explorium.ai/mcp"] } } }

Integration Guide: Gemini CLI

Refer to [Gemini CLI Configuration](https://google-gemini.github.io/gemini-cli/docs/tools/mcp-server.html) for setup details. 1. Locate and open your Gemini CLI configuration file (`~/.gemini/settings.json`). 2. Augment the `mcpServers` section with the following remote definition: { "mcpServers": { "explorium": { "httpUrl": "https://mcp.explorium.ai/mcp" } } } For local execution: { "mcpServers": { "explorium": { "command": "npx", "args": ["-y", "mcp-remote", "https://mcp.explorium.ai/mcp"] } } } Ensure the `mcpServers` object is present.

Integration Guide: JetBrains AI Assistant

Refer to the [JetBrains AI Assistant Documentation](https://www.jetbrains.com/help/ai-assistant/configure-an-mcp-server.html) for comprehensive steps. 1. In your JetBrains IDE, navigate to `Settings` > `Tools` > `AI Assistant` > `Model Context Protocol (MCP)`. 2. Initiate addition via the `+ Add` button. 3. Select the `As JSON` option after clicking `Command` in the dialog's header. 4. Input the following local server configuration and confirm with `OK`: { "mcpServers": { "explorium": { "command": "npx", "args": ["-y", "mcp-remote", "https://mcp.explorium.ai/mcp"] } } } 5. Finalize by clicking `Apply`. This method is also applicable to JetBrains Junie under its respective `MCP Settings`.

Integration Guide: Kiro

Follow the setup guide outlined in the [Kiro Model Context Protocol Documentation](https://kiro.dev/docs/mcp/configuration/): 1. Navigate to the `Kiro` menu option and select `MCP Servers`. 2. Use the `+ Add` button to introduce a new server. 3. Paste the following structure for local execution: { "mcpServers": { "Explorium": { "command": "npx", "args": ["-y", "mcp-remote", "https://mcp.explorium.ai/mcp"], "env": {}, "disabled": false, "autoApprove": [] } } } 4. Save the configuration.

Connection Protocols for External Clients

Advanced users seeking integration with non-standard MCP clients can utilize these direct configuration methods:

You can interface with Explorium's MCP service through several communication methods:

Streamable HTTP (Recommended for Web Clients)

Endpoint URL: https://mcp.explorium.ai/mcp
JSON Configuration Snippet:

{ "mcpServers": { "Explorium": { "url": "https://mcp.explorium.ai/mcp" } } }

Server-Sent Events (SSE)

Endpoint URL: https://mcp.explorium.ai/sse
JSON Configuration Snippet:

{ "mcpServers": { "Explorium": { "url": "https://mcp.explorium.ai/sse" } } }

Standard Input/Output (STDIO) via Local Wrapper

JSON Configuration Snippet:

{ "mcpServers": { "explorium": { "command": "npx", "args": ["-y", "mcp-remote", "https://mcp.explorium.ai/mcp"] } } }

Authentication Protocols

Crucial Note: API key requirements vary significantly by connection topology:

✅ Default Desktop Clients (e.g., Claude Desktop) - Zero key exchange required.
✅ Remote MCP Connections (HTTP/SSE) - No client secret necessary; authentication is handled server-side.
🔑 Self-Contained Docker Deployments - Mandatory API key for authorization.

Obtaining Access Credentials

For containerized environments requiring authorization, an API access token is mandatory. Acquire your credential here: https://admin.explorium.ai/api-key

Containerized Deployment

This package supplies necessary files for self-hosting the connection layer via Docker:

bash

Build the execution image

docker build -t explorium-data-pipe .

Launch the container, supplying the requisite authorization token

docker run -e API_ACCESS_TOKEN=your_explorium_secret_token explorium-data-pipe

Mandatory Environment Variables: - API_ACCESS_TOKEN - Your unique Explorium authentication key (obtainable via this link)

Configuration can be simplified using docker-compose:

yaml

docker-compose.yml example

version: '3.8' services: explorium-mcp-service: build: . ports: - "44280:44280" environment: - API_ACCESS_TOKEN=${EXPLORIUM_TOKEN}

Available Data Access Capabilities

Upon successful registration with an MCP client, the following data utility groups become accessible:

Entity Resolution: Matching enterprises via name, web presence, or unique IDs.
Business Profile Augmentation: Retrieving detailed firmographics, technology stacks, and strategic intelligence.
Corporate Monitoring: Tracking financing events, location shifts, and organizational expansion indicators.
Talent Sourcing: Searching for specific professional roles within target organizations.
Professional Detail Enhancement: Accessing career timelines, current roles, and biographical data for contacts.
Career Event Tracking: Monitoring promotions, job transitions, and professional trajectory changes.

Connection Diagnostics

If integration problems arise when linking your generative AI application to the Explorium MCP service, review these common failure points:

Client Protocol Support Check
Confirm that your AI application's framework natively recognizes and supports the Model Context Protocol (MCP) specification for server connectivity.
Remote Access Validation
Some clients are restricted from direct external server access. If this applies, utilize the provided Docker configuration for local hosting or direct execution.
Developer Outreach
If your platform lacks MCP integration entirely, we encourage submitting a feature request to the platform developers to enable context server support.

Repository Contents Summary

This source tree comprises:

package.json - Project dependencies and execution scripts.
manifest.json - Metadata defining the extension's properties.
Dockerfile - Blueprint for self-contained execution environments.
server/index.js - A placeholder file; actual service logic is remote.
entrypoint.sh - Script managing container startup procedures.

Crucial Caveat: The local server/index.js file is purely structural. Operational service access requires connecting to the Explorium-managed endpoint (https://mcp.explorium.ai/mcp) using established methods like mcp-remote or the specified protocols above. The live MCP gateway is hosted externally by Explorium.

Reference Materials & Assistance

For technical faults or inquiries, please contact support@explorium.ai.

Software Licensing

This work is distributed under the terms of the MIT License. Full details are located in the LICENSE file.

explorium-data-enrichment-connector

Author

explorium-ai

Quick Info

Actions

Tags