Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@explee-mcp Search for CTOs at fintech startups in NYC"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP server wrapping the Explee B2B data API. Gives AI agents tools to search companies and people, enrich emails and phones, run AI agents, and manage deduplication lists.
Tool | Description |
| Search companies by industry, geography, size, revenue, tech stack, funding, traffic |
| Bulk-enrich company profiles by domain |
| Search professionals by job title and company filters |
| Find contacts at companies by domain |
| Convert natural-language ICP description to structured filters |
| Find verified professional email by name + domain |
| Find work phone via LinkedIn URL |
| Async bulk email enrichment — returns a |
| Poll results of a batch enrichment job |
| Combined search + email enrichment in one async job |
| Poll results of a find-and-enrich job |
| List all async jobs on your account |
| Browse available pre-built Explee AI agents |
| Run a pre-built agent by ID |
| Run a custom agent with your own system prompt and schema |
| Poll status and results of an agent run |
| Web search within agent workflows |
| Check your Explee credit balance |
| Purchase additional credits |
| List people deduplication lists |
| Create an exclusion list of LinkedIn URLs |
| Retrieve contents of a people dedup list |
| Delete a people dedup list |
| List company deduplication lists |
| Create an exclusion list of company domains |
| Retrieve contents of a company dedup list |
| Delete a company dedup list |
Related MCP server: LeadClaw
No local setup needed. Pass your Explee API key as a Bearer token when registering the server.
claude mcp add --transport http explee https://explee.drreamer.digital/mcp \
--header "Authorization: Bearer YOUR_EXPLEE_API_KEY"Or add manually to .mcp.json at your project root:
{
"mcpServers": {
"explee": {
"type": "http",
"url": "https://explee.drreamer.digital/mcp",
"headers": {
"Authorization": "Bearer YOUR_EXPLEE_API_KEY"
}
}
}
}Codex reads the token from an environment variable rather than embedding it in the command:
export EXPLEE_API_KEY=your_api_key_here
codex mcp add explee --url https://explee.drreamer.digital/mcp \
--bearer-token-env-var EXPLEE_API_KEYOr add manually to ~/.codex/config.toml (global) or .codex/config.toml (project):
[mcp_servers.explee]
url = "https://explee.drreamer.digital/mcp"
bearer_token_env_var = "EXPLEE_API_KEY"git clone https://github.com/digitaldrreamer/explee-mcp
cd explee-mcp
npm install
cp .env.example .envEdit .env:
EXPLEE_API_KEY=your_api_key_here
PORT=3000Build and start:
npm run build
npm startFor development with auto-reload:
npm run devThe server listens at http://localhost:3000/mcp.
claude mcp add --transport http explee http://localhost:3000/mcpNo --header needed — the server reads EXPLEE_API_KEY from its own .env.
Or manually in .mcp.json:
{
"mcpServers": {
"explee": {
"type": "http",
"url": "http://localhost:3000/mcp"
}
}
}codex mcp add explee --url http://localhost:3000/mcpOr manually in .codex/config.toml:
[mcp_servers.explee]
url = "http://localhost:3000/mcp"curl http://localhost:3000/health
# {"ok":true,"server":"explee-mcp","version":"1.0.0"}This server cannot be deployed
MCP server unifying ERPs, CRMs, APIs and knowledge base for Claude, ChatGPT and Gemini.
Remote MCP server to enrich company profiles with structured B2B data and confidence scores.
Managed LinkedIn MCP server for AI agents: search, connect, message and enrich on accounts you own.
API-first CRM for LLMs - contacts, companies, deals and activities over a native MCP server.
