Review Acquisition Targets in Claude with Dealport MCP

Connect Claude to Dealport's MCP endpoint, choose an existing acquisition Project, and ask for up to ten qualified leads. The list_projects and project_leads tools read your existing results without charging Dealport credits. Start there to review what you already know before asking for more research.

The useful output is a shortlist you can check: each target's supported fit, an unresolved question, any returned source links and a link back to its Dealport result. An unanswered criterion should stay unanswered.

Connect Dealport to Claude

You need access to the intended Dealport workspace and an existing Project with results. If you have not started a Project, open Dealport and start with a search.

1. In Claude, open Customize → Connectors, then Add → Add custom connector.
2. Name the connector Dealport and enter https://app.dealport.com/api/mcp as its remote URL.
3. Complete the connector's sign-in flow with your Dealport account. Choose the workspace whose Projects you want to review.
4. Enable Dealport for the conversation in Claude's connector menu.

On a Team or Enterprise account, an organization owner may need to add the connector before members can connect. Anthropic maintains the current custom-connector setup instructions. Dealport's connector reference describes the endpoint and workspace selection.

Copy this first prompt

Use only Dealport's list_projects and project_leads tools for this task. First list my Projects and ask which one I want to review. After I choose, call project_leads once for that Project with show="qualified", limit=10 and offset=0. Do not fetch another page. For each returned lead, show its name, supported fit, one unresolved question, any reason_sources actually returned, and its Dealport link. Keep Unknown and Needs review checks visible. A source attached to a reason to reach out supports that reason, not every other claim about the company. If a claim has no returned source, say so. Do not call search_companies, search_buildings, get_record, find_contact or research_company. Do not send messages or change records. Stop after the shortlist.

Review the proposed calls before allowing them. A prompt expresses your intended boundary; it does not create a hard account spending limit or guarantee that every client follows it.

What the connector should read

The first call is list_projects with empty arguments. Select a project_id from its actual result. Then use:

{
  "project_id": "<project_id returned by list_projects>",
  "show": "qualified",
  "limit": 10,
  "offset": 0
}

These are arguments for project_leads, not a request to start a new search. A connection already bound to a workspace uses that workspace.

A lead can pass a Project screen while still having an unknown answer. For example, a synthetic result might include “Meets: Owner-operated” and “Unknown: Headcount.” The shortlist should carry both. It should not turn that into a claim that the company has a particular employee count.

Check the result before expanding the job

Open two returned Dealport links. Compare the assistant's explanation with the underlying checks and evidence. Confirm that any cited source supports the specific statement beside it. A reason to contact an owner does not establish that the owner wants to sell.

If the qualified list is empty, check the Project in Dealport. Ask separately for leads awaiting review using show="review" if that is useful. Do not quietly switch to a paid search to fill the page.

For a further research task, agree on the companies, missing facts and credit allowance before allowing additional calls. Inspect the current balance and rates through account_balance. If a call returns an error or an unclear outcome, check what completed before trying again.

Use the same review from your own software

The existing-Project reads also have REST endpoints:

GET https://app.dealport.com/api/v1/projects
GET https://app.dealport.com/api/v1/projects/{project_id}/leads?show=qualified&limit=10&offset=0

REST requests use a workspace API key as a bearer token. Keep the key outside shared prompts and documents. The API reference explains authentication and response fields; MCP sign-in avoids putting that key into this tutorial.

Open your next search in Dealport, or use the prompt above to review a Project you already have.

Product source and setup references checked October 29, 2026.