reggiechan74/crm-mcp-server/deal-parties

Purpose

Map all CRM contacts connected to a specific deal or property, with roles, relationships, and gaps.

Workflow

1. Run crm_vector_search for deal name, property address, or project name across all dossiers.
2. For each hit, run crm_read with section="index" to capture role, org, and relationship strength.
3. Run crm_connections to cross-reference relationships between parties.
4. Identify expected-but-missing roles for this deal type.
5. Include expected roles guidance for sale transactions: broker, buyer's broker, lawyers, appraiser, lender, title. For infrastructure assignments: client, subconsultant, utility company, municipality, environmental consultant. For lease transactions: landlord broker, tenant rep, landlord counsel, tenant counsel.

Output Template

# Deal Party Map: [Deal/Property Name]
 
## Parties Identified ([count] contacts)
 
| Role | Contact | Organization | Relationship | Strength | Last Contact |
|------|---------|-------------|-------------|:--------:|:------------:|
| Seller's Broker | [Name] | [Org] | [Category] | [1-10] | [Date] |
| Buyer's Counsel | [Name] | [Org] | [Category] | [1-10] | [Date] |
| ... | | | | | |
 
## Relationship Map
[which parties know each other, potential alliances, conflict risks]
 
## Missing Parties
[roles you'd expect on this deal type but don't have in CRM — e.g., "No appraiser identified"]
 
## Recommended Next Actions
1.[e.g., "Reach out to [Name] for intel on buyer's timeline"]
2.[e.g., "Create dossier for the buyer's counsel — you'll need them later"]

Edge Cases

• Zero search results: If crm_vector_search returns no contacts mentioning the deal, ask the user to provide party names manually, then search for each.
• Relationship Map format: Present key links narratively (e.g., '[Name A] and [Name B] are at the same firm') or as a simple connection list.

Shared Conventions

See skills/_shared/conventions.md for output format, contact resolution, token awareness, and error handling rules.