Prospect Locally
Articles

Connect ChatGPT, Claude, or GoHighLevel to Prospect Locally

You can run a lead search by typing a sentence into ChatGPT, claude.ai, or GoHighLevel instead of filling in a form. The assistant calls the Prospect Locally MCP server on your behalf, using your account and your credits. This article explains how to add the server, what the consent screen asks you to approve, what the assistant can and cannot do once it is connected, and how the limits on campaigns and export links work.

What MCP is, in one paragraph

MCP, the Model Context Protocol, is a standard way for an AI assistant to call tools that live on another server. Prospect Locally runs one MCP server at an address that ends in /api/mcp. The server offers 19 tools, covering location lookup, searches, enrichment, campaigns, exports, phone verification, and a credit balance check. An assistant reads the tool list when it connects, so you do not teach it the names.

Add the server

ChatGPT, claude.ai, and GoHighLevel connect with no API key. You add the server address as a custom connector, sign in to your Prospect Locally account when the assistant asks, and approve the connection. The steps are the same in each product, although the menu names differ:

  1. Copy the server address from the “Connect your AI” block on the home page or from the MCP section of the docs. Each tab of that block, one for each assistant, has a ready prompt and a Copy button.
  2. In the assistant’s settings, open the place where custom connectors or MCP servers are added, and paste the address. Leave any API key field empty.
  3. Start the connection. The assistant opens a Prospect Locally sign-in page. Sign in with the account whose credits you want to use.
  4. Read the consent screen, then press Allow.

The menu for custom connectors differs between products and changes over time, and some plans of some products limit who can add one. If you cannot find the setting, check the assistant’s own help pages for the current name of the feature.

What the consent screen says

The screen shows three things: the name of the application that is asking, the email address of the account you are signed in with, and one sentence: “Allow <app> to search, enrich, and export leads using your credits.” Two buttons follow, Allow and Deny.

Read the account email before you press Allow. If you manage more than one account, the credits that the assistant spends are the credits of the account shown on this screen. Pressing Deny ends the attempt, and the assistant gets no access.

What the assistant can do

With the connection in place, the assistant can call any of the tools on your behalf:

  • Look up locations and categories, and read your credit balance. These calls cost no credits.
  • Start a search, read its status and results, and enrich up to ten domains at a time. These calls spend credits from your balance.
  • Preview, create, start, pause, stop, and edit campaigns, and read their leads. Previewing and creating a campaign cost nothing, and starting one spends credits as it finds businesses.
  • Verify phone numbers, which costs credits for each number that is looked up.
  • Export a campaign as a CSV and fetch the download link.

The assistant sees and spends only the data and credits of the account that approved the connection. It cannot read another account’s searches or campaigns. None of the 19 tools changes your plan, your billing details, or your sign-in settings, so a connected assistant has no way to alter them.

What the assistant cannot do with your credits

Credits are the limit. A search or a campaign cannot spend more than the account holds: an enrichment call that needs more credits than you have is refused without a partial charge, and a campaign that runs out of credits pauses until you add more and resume it. The assistant cannot buy credits or change your plan.

The assistant can still spend the credits you do have, so give it a rule. The setup prompts end with “Tell me the credit cost before searching, enriching or starting a campaign.” An assistant that follows that sentence reports the cost and waits for your yes. If you want the same behavior in every conversation, add the sentence to the assistant’s custom instructions.

The 500-lead default on campaigns an assistant creates

A campaign created through MCP carries a default max_leads cap of 500 leads. The cap limits how much a single request from an assistant can spend. The campaign starts no further locations once it has charged that many unique leads. The cap is not an exact row count, because a location that is already running finishes first, so the final total can be higher than the cap.

You can raise the cap. Ask the assistant to update the campaign with a larger max_leads, or edit it yourself in the app. The minimum value for any campaign is 100. The region article explains campaigns in full.

Export links last 1 hour

When the assistant exports a campaign, the tool returns a download link, and the link expires after 1 hour. If you open it after that, ask the assistant for a fresh link, or download the file from the Downloads page of the app, where every export is listed with its file name, format, and row count. The files sit in private storage, and each click on Download creates a fresh signed link.

Keep the results small

The tools that read leads return trimmed records: 50 rows by default and at most 200 per call. This keeps one answer within what an assistant can hold in a conversation. For a full file with every column, ask for an export and open the CSV in your own tools.

Coding agents such as Claude Code, Cursor, and Codex connect differently, with an API key in a header. The connection article for coding agents covers that route.