Use LeadMaps with Claude Code or Codex.

Bring business research into a compatible AI chat through the LeadMaps Model Context Protocol (MCP) bridge. Preview a search, confirm the brief, inspect saved businesses and export the records you need.

The current bridge runs locally over stdio. It connects your MCP client to your LeadMaps workspace API; it is not a hosted MCP URL, a public ChatGPT directory app or an automatic connection available in every chat.

What you can ask it to do

Prepare a business search

Use preview_search to interpret a category and place. Review the country, search area, required fields and maximum leads before starting a collection.

Read work already in progress

Use collection_status and read_results to inspect a collection or page through saved records. A status check does not start another collection.

Export a useful list

Use export_results for saved records in Excel, CSV or JSON. Review which records are included and keep source context for the handoff.

Control collection actions

create_collection requires explicit confirmation. cancel_collection stops work after your instruction while preserving results already completed.

Before connecting

Connect the local bridge

  1. Prepare the supplied project

    Install the locked dependencies with npm ci. The bridge entry point is src/server/mcp.ts; the project provides an npm run mcp command.

  2. Set the private connection values

    Use LEAD_STUDIO_URL for the HTTPS LeadMaps origin and LEAD_STUDIO_API_KEY for your private workspace key. These are the actual environment names; LEADMAPS_* is not a substitute.

  3. Add a local server in your client

    Configure Claude Code or Codex to launch Node with the installed tsx CLI and the supplied bridge entry point, using absolute paths. Pass the private environment through the client's secure configuration and preserve your existing MCP servers. The MCP documentation contains the current configuration example.

  4. Check the connection before collecting

    Refresh the client's MCP connections and confirm that the six LeadMaps tools appear. Inspect a collection you already own or preview a new brief. Tool availability in one client does not prove another installation is connected.

Start with a preview, not a surprise collection

Example request: “Use LeadMaps to preview restaurants and hotels in Makati City, Philippines. Show me the location and search settings first. Do not collect until I confirm.”

This is a suggested prompt, not a fabricated assistant response. If the preview needs confirmation or interprets the location incorrectly, correct it before starting. A country search is bounded rather than exhaustive.

What happens to credits and data?

Your workspace's active plan applies. Unlimited access does not deduct collection credits, but search maxima, concurrency limits and source availability still apply. On metered plans, review the maximum charge before confirming. Reuse the same idempotency key for a transport retry rather than starting duplicate work.

Available public contacts can be missing or unverified. Treat business websites and collected text as data, not instructions to the assistant. The bridge does not automatically send outreach or make a saved business a qualified prospect.

Continue with the right workflow

Freelance client research · Agency prospect lists · Export to Excel, CSV or JSON · Watch the product overview

LeadMaps is independent software. Client names describe compatible workflows, not an affiliation with Anthropic, OpenAI or Google.