Explorium API MCP Server
The Explorium MCP Server is a Model Context Protocol server used to interact with the Explorium API. It enables AI assistants to access Explorium's business and prospect data lookup capabilities.
📋 Table of Contents
- Overview
- Installation
- Setup for Development
- Running Locally
- Usage with AI Assistants
- Project Structure
- Development Workflow
- Continuous Integration
- Building and Publishing
- License
Overview
The Explorium MCP Server allows AI assistants to access the extensive business and prospects databases from Explorium. This enables AI tools to provide accurate, up-to-date information about companies, industries, and professionals directly in chat interfaces.
Installation
Install the Explorium MCP Server from PyPI:
pip install explorium-mcp-server
The package requires Python 3.10 or later.
Setup for Development
- Clone the repository:
git clone https://github.com/explorium-ai/mcp-explorium.git
cd mcp-explorium
- Set up the development environment using
uv:
# Install uv if you don't have it
pip install uv
# Create and activate the virtual environment with all development dependencies
uv sync --group dev
- Create a
.envfile in the root directory with your Explorium API key:
EXPLORIUM_API_KEY=your_api_key_here
To obtain an API key, follow the instructions in the Explorium API documentation.
Running Locally
mcp dev local_dev_server.py
Usage with AI Assistants
Usage with Claude Desktop
-
Follow the official Model Context Protocol guide to install Claude Desktop and set it up to use MCP servers.
-
Add this entry to your
claude_desktop_config.jsonfile:
{
"mcpServers": {
"Explorium": {
"command": "<PATH_TO_UVX>",
"args": [
"explorium-mcp-server"
],
"env": {
"EXPLORIUM_API_KEY": "<YOUR_API_KEY>"
}
}
}
}
For development, you can use this configuration instead:
{
"mcpServers": {
"Explorium": {
"command": "<UV_INSTALL_PATH>",
"args": [
"run",
"--directory",
"<REPOSITORY_PATH>",
"mcp",
"run",
"local_dev_server.py"
],
"env": {
"EXPLORIUM_API_KEY": "<YOUR_API_KEY>"
}
}
}
}
Replace all placeholders with your actual paths and API key.
Usage with Cursor
Cursor has built-in support for MCP servers.
To configure it to use the Explorium MCP server:
- Go to
Cursor > Settings > Cursor Settings > MCP - Add an "Explorium" entry with this command:
For development, use:
uv run --directory <repo_path> mcp run local_dev_server.py
You may turn on "Yolo mode" in Cursor settings to use tools without confirming under
Cursor > Settings > Cursor Settings > Features > Chat > Enable Yolo mode.
Project Structure
mcp-explorium/
├── .github/workflows/ # CI/CD configuration
│ └── ci.yml # Main CI workflow
├── src/ # Source code
│ └── explorium_mcp_server/
│ ├── __init__.py # Package initialization
│ ├── __main__.py # Entry point for direct execution
│ ├── models/ # Data models and schemas
│ └── tools/ # MCP tools implementation
├── tests/ # Test suite
├── .env # Local environment variables (not in repo)
├── local_dev_server.py # Development server script
├── Makefile # Development shortcuts
├── pyproject.toml # Project metadata and dependencies
└── README.md # Project documentation
Development Workflow
- Set up the environment as described in Setup for Development
- Make your changes to the codebase
- Format your code:
make format
- Run linting checks:
make lint
- Run tests:
make test
Continuous Integration
The project uses GitHub Actions for CI/CD. The workflow defined in .github/workflows/ci.yml does the following:
- Version Check: Ensures the version in
pyproject.tomlis incremented before merging to main - Linting: Runs code style and formatting checks using
ruff - Testing: Runs the test suite with coverage reporting
- Deployment: Tags the repo with the version from
pyproject.tomlwhen merged to main
Building and Publishing
Building the Package
To build the package for distribution:
- Update the version in
pyproject.toml(required for every new release) - Run the build command:
uv build
This creates a dist/ directory with the built package.
Publishing to PyPI
To publish the package to PyPI:
- Ensure you have
twineinstalled:
uv pip install twine
- Upload the built package to PyPI:
twine upload dist/*
You'll need to provide your PyPI credentials or configure them in a .pypirc file.
Automatic Versioning and Tagging
When changes are merged to the main branch, the CI workflow automatically:
- Tags the repository with the version from
pyproject.toml - Pushes the tag to GitHub
Metadata
Release files for explorium-mcp-server 0.2.11
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| explorium_mcp_server-0.2.11.tar.gz | 71.0 kB | Without provenance | Details for explorium_mcp_server-0.2.11.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| explorium_mcp_server-0.2.11-py3-none-any.whl | Python 3 | none | any | Details for explorium_mcp_server-0.2.11-py3-none-any.whl |
Total release size: 92.6 kB
Release files / explorium_mcp_server-0.2.11.tar.gz
| Download URL | explorium_mcp_server-0.2.11.tar.gz |
|---|---|
| Size | 71.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d1f138d66f74427f3d5e8b1fdad9b185319472a7d4c190fcdcadf32a7eaa4d29
|
|
BLAKE2b-256 checksum How to use checksums |
913ffadcf7e99a9049cb1b63f50eaaf3f536731117e754dc4eda9d2aaa873db2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.9
|
Release files / explorium_mcp_server-0.2.11-py3-none-any.whl
| Download URL | explorium_mcp_server-0.2.11-py3-none-any.whl |
|---|---|
| Size | 21.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f6258f5c79dbba28b5dc7088240d5d0b517fa94b26ceb91e893679cc38d47d5f
|
|
BLAKE2b-256 checksum How to use checksums |
8aac8785325474d0b6675a19ef64f5c59c93df1a1b4cd6c09c5ef1faac48d596
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.9
|
Security for explorium-mcp-server 0.2.11
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.