---
name: privsource-mcp-connector
description: Use when an agent needs to connect to PrivSource MCP, understand OAuth/account scope, choose which PrivSource MCP tool family to use, or recover from missing tool access.
---

# PrivSource MCP Connector

PrivSource MCP exposes account-scoped tools for live deals, seller deal submission, buyer- and seller-side mandate matches, buyer lists, target lists, and Contact Agent enrichment.

## Connect

- MCP endpoint: `https://api.privsource.com/mcp`
- Auth: OAuth 2.0 authorization code with PKCE.
- Scope: `mcp:api`.
- Users authorize a PrivSource team. Tool availability depends on that team's buyer/seller accounts and feature flags.
- Human setup docs: `https://privsource.com/docs/mcp-integration`.

## First Call

Call `privsource_whoami` before choosing a workflow when account scope is unclear.

Use the returned `apis`:

- `deals`: use `search_deals` and `get_deal`.
- `pending-deals`: use `create_pending_deal` to submit a new seller deal for PrivSource admin review and `get_pending_deal` to track its status through to a live listing.
- `seller-deals`: use `update_seller_deal` to edit live deals and `set_seller_deal_auto_share` to set automatic sharing.
- `buyside-mandates`: use buyside mandate tools to manage the buyer account's own published acquisition criteria and review the deals PrivSource matched to them.
- `seller-mandate-matches`: use seller mandate match tools to review the buyer mandates matched to the seller account's live deals and contact those buyers.
- `buyer-lists`: use buyer-list tools for seller-side acquirer research.
- `target-lists`: use target-list tools to build lists of target companies that match filters.
- `contact-agents`: use Contact Agent tools for standalone contact enrichment.

## Tool Selection

- Buyer searching for acquisition opportunities: use deal tools.
- Buyer creating or maintaining their own acquisition mandate for sellers to find: use buyside mandate tools (`create_buyside_mandate`, `update_buyside_mandate`, `publish_buyside_mandate`, ...).
- Buyer reviewing the deals PrivSource matched to a mandate: use `get_buyside_mandate_matches` and `update_buyside_mandate_match`.
- Seller reviewing buyer mandates matched to a live deal: start with `list_seller_deals`, then use `get_seller_deal_matches`, `get_seller_mandate_match`, and `update_seller_mandate_match`. Use `send_seller_mandate_outreach` only when the user asks to contact the buyer and confirms which matched deals to share.
- Seller editing a pending submission: use `update_pending_deal`. For deletion, return the link from `get_pending_deal_deletion_link`.
- Seller editing a live deal: use `update_seller_deal`. Use `set_seller_deal_auto_share` for automatic sharing.
- Seller submitting a new deal to be listed on PrivSource: use `create_pending_deal`, then `get_pending_deal` to track review status.
- Seller building a list of potential acquirers for a company being sold: use buyer-list tools.
- Buyer building a list of target companies that match filters (sector, size, geography): use target-list tools (`create_target_list`, `refine_target_list_filters`, `get_target_list_results`, ...).
- User has a set of companies or named contacts and wants emails/phones: use Contact Agent tools.

## Error Handling

- If a tool is absent, do not invent it. Call `privsource_whoami` and explain the missing API access.
- If a write tool returns a payment, allowance, or credit error, stop and report the exact message.
- Use the ids returned by PrivSource tools verbatim. Do not synthesize ids or pass numeric database ids.