eliottreich/crawdar-mcp

Crawdar gives AI agents evidence-backed public business research through a hosted MCP server. It separates verified fits, likely fits, and excluded candidates, keeps source URLs attached, and explains why candidates were rejected.
No package or local crawler is required.
Optional local stdio bridge
This repository also provides an MIT-licensed, runnable bridge for clients that require stdio. It uses pinned mcp-remote to forward MCP traffic to https://crawdar.com/api/mcp. The crawler backend remains hosted and is not included in this repository. This is not an offline or self-hosted crawler.
With Node.js 22 or newer, run npm ci --ignore-scripts, then configure your MCP client to launch node with the absolute path to node_modules/mcp-remote/dist/proxy.js, followed by https://crawdar.com/api/mcp --transport http-only as separate arguments. For a container, build with docker build -t crawdar-mcp . and launch with docker run --rm -i crawdar-mcp (no TTY).
The bridge exposes the hosted server's tools and sends tool inputs to Crawdar over HTTPS. Live research remains subject to Crawdar's quotas and service availability. Credentials are not embedded. The fictional sandbox and tool discovery require no key. For authenticated usage, use the direct HTTP configuration below or the bridge's --header-file option with a private local header file. Never commit credentials or include them in command arguments.
Bring a difficult search brief
We are recruiting five independent builders to test a real company-research workflow. Describe your brief and acceptance rules. We will confirm a small sample scope first, then review what matched, what failed and what remains unknown. No stars, referrals or positive reviews required.
GitHub issues are public. Keep confidential briefs and all credentials out of them; use hello@crawdar.com for private support. The general Crawdar web tool does not require a GitHub account.
Connect
Remote MCP endpoint:
Claude Code:
Codex configuration:
Generic MCP configuration:
Tools
- research_businesses: One-call research from a natural-language brief.
- search_businesses: Structured target and geography search.
- sandbox_businesses: Fictional integration test with no search-provider usage.
- start_lead_search: Start a private resumable job.
- get_lead_search: Poll status and page through compact or full results.
- refine_lead_search: Create a revised job without changing the original.
- retry_lead_search: Recover from a stopped job.
- cancel_lead_search: Cancel a queued or running job.
- explain_crawdar: Read result semantics, limits, and safe-use guidance.
Try a visual workflow in n8n
Download the n8n sandbox workflow, import it into your n8n instance, and click **Execute Workflow**. This demonstrates routing, not real prospect discovery. No Crawdar account, key, AI-model subscription, or CRM credentials are needed. You still need n8n itself.
It fetches three fictional businesses, keeps source evidence and sandbox labels attached, and sends two explicitly qualified examples down one branch and one uncertain example to review. No emails, CRM writes or scheduled scans. Changing the brief only changes fixture labels, not real research. A qualified status is not a guarantee of fit: review the underlying evidence before consequential use.