@rubytech/create-maxy-code 0.1.26 → 0.1.27

package/payload/platform/plugins/listings/skills/supplier-booker/SKILL.md

@@ -0,0 +1,39 @@
+---
+name: supplier-booker
+description: "Draft and stage booking requests to photographer, floorplan supplier, and other property-prep suppliers from the agent's preferred-supplier list. Built for use inside new-instruction."
+---
+
+# Supplier booker
+
+A building-block skill called by `new-instruction`. Stages the booking emails that get the photographer and the floorplan supplier into the property in the first 48 hours after instruction.
+
+## What it does
+
+For each supplier the workflow needs to book (photographer, floorplan, and optionally a combined supplier when one provider handles both), the skill drafts an email to the agent's preferred supplier from the profile. The draft includes:
+
+- Property full address with postcode
+- Access details (vendor contact, key location, lockbox code, alarm code) read from the CRM record
+- The agent's standard brief for that supplier (photography style preferences, number of shots, floorplan format)
+- Preferred date range
+- Reply-to address
+
+If the photographer and floorplan supplier are the same provider, the skill combines them into one booking request rather than sending two emails.
+
+## What it does not do
+
+- It does not send. Sending requires the operator's approval.
+- It does not book the supplier into the calendar. The supplier confirms back, then the calendar entry is created.
+- It does not pay the supplier or set up an invoice. Supplier payment runs through `month-end-close`.
+
+## Connectors
+
+Read: profile (preferred suppliers, briefs), CRM (vendor contact, access details).
+Write (staged only): email to each supplier.
+
+## Profile keys
+
+- `realagent.suppliers.photographer`
+- `realagent.suppliers.floorplan`
+- `realagent.suppliers.combined` (boolean, true if one provider handles both)
+- `realagent.suppliers.brief.photography` (default brief, learned)
+- `realagent.suppliers.brief.floorplan`

package/payload/platform/plugins/listings/skills/talk-track-composer/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: talk-track-composer
+description: "Draft the talk-track block for the valuation prep pack: three questions for the vendor, two likely objections, the agent's USP in the agent's voice. Built for use inside valuation-prep."
+---
+
+# Talk-track composer
+
+A building-block skill called by `valuation-prep`. Produces the prompt the agent uses in the room.
+
+## What it produces
+
+Three sub-sections, in this order.
+
+1. **Questions to ask the vendor.** Three open questions tailored to the property and the vendor's situation. Examples vary with context: timeline pressure, chain position, prior agent contact, fee sensitivity.
+2. **Likely objections.** Two objections most likely to come up, given the comparables and the local stats. Each shown with a one-sentence acknowledgement and a one-sentence response in the agent's voice.
+3. **The USP.** The agent's USP framed in the agent's words, from the profile's voice samples. The phrasing tightens over time as the workflow watches which phrasings get used versus edited.
+
+## Voice source
+
+The skill reads the profile's voice samples (three to five emails the agent has written) and prior successful talk-tracks. If voice samples are not yet seeded, the output uses a generic professional tone and flags the absence so the operator knows to add samples.
+
+## What it does not do
+
+- It does not draft messages to send. That is `tone-matched-drafter`.
+- It does not write to anything.
+- It does not pretend to know the vendor when the CRM record has no prior contact. If the vendor is new, the questions are designed to learn rather than to anchor.
+
+## Connectors
+
+Read: profile (voice samples), CRM (vendor history if any). No writes.
+
+## Profile keys
+
+- `realagent.voice_samples` (list of email bodies, used for tone extraction)
+- `realagent.usp_phrases` (list, learned)
+- `realagent.objection_responses` (map of common objections to preferred responses, learned)

package/payload/platform/plugins/listings/skills/terms-of-business-drafter/SKILL.md

@@ -0,0 +1,54 @@
+---
+name: terms-of-business-drafter
+description: "Populate the agency's terms of business template with the deal specifics for a new instruction and stage it in DocuSign with the vendor as recipient. Built for use inside new-instruction; the operator does not invoke it directly. Owned by the compliance specialist."
+---
+
+# Terms of business drafter
+
+A building-block skill called by `new-instruction`. Produces the terms document the vendor signs before any marketing begins.
+
+## What it does
+
+Reads the agency's terms-of-business template path from the profile, then populates it with:
+
+- Property full address and tenure
+- Vendor name(s) and contact details
+- Fee structure (sole agency, multi agency, with-other-agents, or the agent's named variant)
+- Fee amount or percentage
+- Minimum fee where applicable
+- Marketing period in weeks
+- Withdrawal fee policy
+- Notice period
+- VAT inclusion and registration number
+- CMP scheme membership, redress scheme membership, ICO registration (TPO code requires display)
+- Effective date
+
+The populated document is staged in DocuSign as a recipient envelope with the vendor as signatory. Nothing is sent until the operator approves.
+
+## Compliance ground
+
+The terms of business is the document the Estate Agents Act 1979 s.18 requires to be in writing before instruction is accepted. Failure to comply makes the contract unenforceable except by court order. The Consumer Rights Act 2015 fee transparency obligations also bear on this document. `compliance-flag-checker` runs against the populated draft before the operator sees it.
+
+If the populated draft is missing any of the mandatory fields, the missing fields are listed at the top of the staged output so the operator can fill them before approving.
+
+## What it does not do
+
+- It does not send. Sending requires the operator's explicit approval.
+- It does not amend the agency template. Template changes are made out-of-band.
+- It does not negotiate fees with the vendor. The agreed fee is captured at the appointment.
+
+## Connectors
+
+Read: profile (template path, fee defaults), CRM (vendor and property records).
+Write (staged only): DocuSign envelope creation.
+
+## Profile keys
+
+- `realagent.terms_template_path`
+- `realagent.fee_structure.default`
+- `realagent.fee_structure.minimum`
+- `realagent.fee_structure.withdrawal_fee`
+- `realagent.fee_structure.marketing_period_weeks`
+- `realagent.compliance.cmp_scheme_membership`
+- `realagent.compliance.redress_scheme`
+- `realagent.compliance.ico_registration`

package/payload/platform/plugins/listings/skills/valuation-prep/SKILL.md

@@ -0,0 +1,69 @@
+---
+name: valuation-prep
+description: "Produce the pre-appointment pack the agent reads on the walk from the car to a valuation or market appraisal. Six sections: property, comparables, local stats, vendor, pricing scenarios, talk-track. Triggers when the operator says 'prep my val at <address>', 'valuation pack for <name>', 'what should I take to the <name> appointment', 'I'm at the Smiths tomorrow, get me ready', 'anything I should know about <address> before tomorrow'. Also fires automatically the evening before any appointment in the calendar tagged as a valuation."
+---
+
+# Valuation prep
+
+The master workflow owned by the valuer specialist. Turns a 90-minute prep into a 60-second read. This is the workflow most likely to win new instructions; vendors notice when an agent walks in knowing more than they do.
+
+## Inputs
+
+- Address of the property to value, supplied by the operator or read from the calendar entry.
+- The vendor's name if it is in the diary entry or the CRM.
+- The customisation profile.
+
+If the address is ambiguous, the workflow asks once for the postcode rather than guessing. Every other input is derived from connectors.
+
+## Architecture principles encoded here
+
+- Read before write. Read-only output; the post-appointment instruction pack is a separate workflow.
+- Stage, don't send. Nothing to send.
+- One screen of output. Six short sections, readable in two minutes.
+- Cite the source. Every comparable cites the portal or Land Registry. Every vendor signal cites Land Registry, the title, or the CRM. Every stat cites the area data feed.
+- Teach the profile. Learning hooks documented below.
+- Reversible. Read-only.
+
+## Output shape
+
+Six sections in this order.
+
+1. **Property.** Address, type, beds, baths, last sold price and date if available, EPC if available, last listed price if previously marketed, planning history. Sourced from Land Registry, the EPC register, the council planning portal, and prior portal listings.
+2. **Comparables.** Three SSTC and three sold in the last 12 months within the profile's comparable radius (default 0.5 miles, learns). Each comparable: address, asking or sold price, beds, square footage, time on market, agent. Adds a price-per-square-foot column if at least four of the six have square footage. Built by `comparable-finder`.
+3. **Local stats.** Three numbers maximum: average days on market in the immediate area, asking-to-sold ratio, current stock count. Context, not headline. Built by `local-market-stats`.
+4. **Vendor.** How long they have owned, last purchase price, public signals worth knowing with the privacy line enforced. Built by `vendor-research`. Sensitive signals are flagged at the top of the section if suppressed, so the operator knows there is more if they want it.
+5. **Pricing scenarios.** Three numbers by default: quick-sale (sub-30-day expectation), market (30 to 60 days), aspirational (90 days plus, marked "stretch"). Each with one sentence of reasoning. If the profile has corrected toward a single recommendation with a range, the workflow learns and presents that format instead. Built by `pricing-scenario-builder`.
+6. **Talk-track.** Three questions to ask the vendor, two objections likely to come up, the agent's USP in the agent's voice. Built by `talk-track-composer` reading the profile's voice samples and prior successful talk-tracks.
+
+## The privacy line
+
+`vendor-research` will surface ownership changes, joint owners who appear and disappear, deaths registered against the address, and planning disputes. The profile holds a privacy preference, default: surface ownership and planning, flag-but-suppress death and dispute signals. The operator can adjust by saying "show me everything you find" or "drop the sensitive stuff".
+
+The default is conservative because the agent's reputation is on the line if Claude blurts something inappropriate and the agent quotes it.
+
+## Approval gates
+
+None at the prep stage. The pack is information, not action. Approval gates appear in `new-instruction`, which runs after the appointment if the agent wins the business.
+
+## Continuous learning hooks
+
+- Comparable radius. "Wider comps" or "tighter comps" updates the default radius.
+- Pricing format. Three scenarios versus single-with-range versus a single number. Learned from which version the agent screenshots, copies, or refers to in the appointment notes.
+- Comparable preferences. "Ignore that one, it was a probate sale" feeds the exclude filters: distressed sales, off-market, agent-bought.
+- Talk-track effectiveness. Won appointments tag the talk-track as successful. Lost appointments do not blame the talk-track (too noisy) but ask the agent for one-line feedback if offered.
+- USP drift. The USP tightens as the workflow watches which phrasings get used versus edited out before the appointment.
+
+All writes go through `profile-writer`.
+
+## Connectors
+
+Read: Rightmove, Zoopla, OnTheMarket data feeds; Land Registry; EPC register; council planning portal; CRM. No writes.
+
+## Profile keys
+
+- `realagent.comparable_radius_miles` (default 0.5)
+- `realagent.pricing_format` ("three_scenarios" | "single_with_range" | "single_number")
+- `realagent.comparable_exclude_filters` (list, learned)
+- `realagent.privacy_line.surface` (list)
+- `realagent.privacy_line.suppress` (list)
+- `realagent.usp_phrases` (list, learned)

package/payload/platform/plugins/loop/.claude-plugin/plugin.json

@@ -0,0 +1,17 @@
+{
+  "name": "real-agency-loop",
+  "description": "Loop CRM integration — full read/write access to all 8 resource groups: properties, people, viewings, feedback, team, marketing, customer preferences, and supplier operations. Cross-team aggregation with encrypted key storage.",
+  "version": "0.1.0",
+  "author": {
+    "name": "Rubytech LLC"
+  },
+  "mcpServers": {
+    "real-agency-loop": {
+      "type": "stdio",
+      "command": "node",
+      "args": [
+        "${CLAUDE_PLUGIN_ROOT}/mcp/dist/index.js"
+      ]
+    }
+  }
+}

package/payload/platform/plugins/loop/PLUGIN.md

@@ -0,0 +1,108 @@
+---
+name: real-agency-loop
+description: "Loop CRM integration — full read/write access to all 8 resource groups: properties, people, viewings, feedback, team, marketing, customer preferences, and supplier operations. Cross-team aggregation with encrypted key storage."
+tools:
+  - loop-key-register
+  - loop-key-deregister
+  - loop-key-list
+  - loop-people-search
+  - loop-people-detail
+  - loop-property-search
+  - loop-property-detail
+  - loop-property-listed
+  - loop-property-request
+  - loop-viewing-search
+  - loop-viewing-detail
+  - loop-viewing-create
+  - loop-viewing-update
+  - loop-feedback-get
+  - loop-feedback-submit
+  - loop-team-info
+  - loop-team-availability
+  - loop-marketing-match
+  - loop-marketing-match-batch
+  - loop-marketing-match-request
+  - loop-marketing-enquiry
+  - loop-customer-preferences
+  - loop-supplier
+skills:
+  - skills/tone-matched-drafter/SKILL.md
+  - skills/priority-ranker/SKILL.md
+  - skills/compliance-flag-checker/SKILL.md
+  - skills/vendor-research/SKILL.md
+  - skills/variance-narrator/SKILL.md
+profileKeys:
+  - realagent.cause_phrases
+  - realagent.close.narrative_voice_samples
+  - realagent.compliance.aml_provider
+  - realagent.compliance.cmp_scheme_membership
+  - realagent.compliance.ico_registration
+  - realagent.compliance.mlro_designation
+  - realagent.compliance.propertymark_membership
+  - realagent.compliance.redress_scheme
+  - realagent.compliance.tpo_membership
+  - realagent.phrasing_pet_peeves
+  - realagent.priority_weights.fee_multiplier
+  - realagent.privacy_line.suppress
+  - realagent.privacy_line.surface
+  - realagent.voice_samples
+always: false
+metadata: {"platform":{"optional":true,"embed":["admin"]}}
+---
+
+# Real Agency — Loop CRM
+
+Full integration with Loop CRM V2 API (api.loop.software). Covers all 73 endpoints across 8 resource groups — properties, people, viewings, feedback, team, marketing, customer preferences, and supplier operations. Supports both read and write operations.
+
+## Capabilities
+
+- **Key management** — register, deregister, and list Loop API keys per team
+- **Cross-team aggregation** — query data across all registered teams in a single request
+- **Read and write** — search data, view details, create viewings, record feedback, submit enquiries, manage supplier operations
+- **Role-aware people search** — search buyers, sellers, renters, and landlords with role-specific filters (price, beds, areas, mortgage status)
+- **Channel listings** — query properties listed on Rightmove, Zoopla, OnTheMarket, or the website
+- **Marketing matching** — view matching property details, submit requests, manage auto-responders
+- **Vertical scope** — each team key has configurable endpoint-group permissions (8 groups)
+- **Encrypted storage** — API keys are AES-256-GCM encrypted in Neo4j, never stored in plaintext
+
+## Permissions
+
+Each registered team key controls access to 8 endpoint groups:
+`properties`, `people`, `viewings`, `feedback`, `team`, `marketing`, `customer`, `supplier`
+
+Keys default to all 8 groups. Restrict at registration time to limit what the agent can query for a given team.
+
+## Security
+
+Never include API key values in responses. Identify teams by name only. When the user asks for a key value, explain that keys are encrypted and cannot be retrieved — they must be re-registered from Loop's dashboard.
+
+## When to use these tools
+
+Use Loop tools when the user asks about CRM data: properties, people, viewings, feedback, team info, marketing matches, customer preferences, or supplier operations.
+
+**Write triggers — invoke writes (not reads) when the user says:**
+- "submit", "send", "log", "record" → `loop-feedback-submit`, `loop-marketing-enquiry`, `loop-property-request`
+- "create", "book", "schedule", "set up" a viewing → `loop-viewing-create`
+- "add a note", "leave feedback", "record what they said" → `loop-viewing-update`
+- "request a callback", "request more info", "ask for a viewing" → `loop-property-request` or `loop-marketing-match-request`
+- "update preferences", "save what they're looking for" → `loop-customer-preferences` (action=write)
+- "mark complete", "close out", "finished the job" → `loop-supplier` (action=maintenance-complete or board-complete)
+- "submit a quote" → `loop-supplier` (action=maintenance-submit-quote)
+
+Default to writes when the user's intent is to *change* data in Loop, not just look it up. Reads return information; writes record the user's decision in Loop.
+
+Write operations require specifying which team to act through. If no teams are registered, suggest using `loop-key-register` to add team API keys. If a write fails with a permission error (`Team "X" does not have <group> permission`), the registered key was scoped to fewer than 8 endpoint groups — re-register with the full permissions array (`["properties","people","viewings","feedback","team","marketing","customer","supplier"]`).
+
+## Cross-cutting skills hosted here
+
+This plugin also hosts the five cross-cutting skills that more than one Real Agent workflow composes. They live here rather than in a workflow-specific plugin because every workflow that produces a message, a ranking, a compliance check, a vendor lookup, or a narrative paragraph reuses them.
+
+| Skill | Owner specialist | Purpose |
+|-------|------------------|---------|
+| `tone-matched-drafter` | negotiator | Drafts every outgoing message in the operator's voice per recipient type |
+| `priority-ranker` | shared | Orders any list using the profile's urgency weights |
+| `compliance-flag-checker` | compliance | Flags AML, GDPR, DMCCA material info, ASA standards, Equality Act risks |
+| `vendor-research` | negotiator | Public-record and CRM-history lookup with the privacy line enforced |
+| `variance-narrator` | compliance | Short prose summaries of numerical changes |
+
+The cross-cutting skill `profile-writer` named in spec 00 §6 maps to the Maxy platform's existing `profile-update` tool; no new skill is shipped for it.

package/payload/platform/plugins/loop/mcp/dist/index.d.ts

@@ -0,0 +1,2 @@
+export {};
+//# sourceMappingURL=index.d.ts.map

package/payload/platform/plugins/loop/mcp/dist/index.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":""}

package/payload/platform/plugins/loop/mcp/dist/index.js

@@ -0,0 +1,293 @@
+import { initStderrTee } from "../../../../lib/mcp-stderr-tee/dist/index.js";
+initStderrTee("loop");
+import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
+import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
+import { z } from "zod";
+import { keyRegister } from "./tools/key-register.js";
+import { keyDeregister } from "./tools/key-deregister.js";
+import { keyList } from "./tools/key-list.js";
+import { propertySearch } from "./tools/property-search.js";
+import { propertyDetail } from "./tools/property-detail.js";
+import { propertyListed } from "./tools/property-listed.js";
+import { propertyRequest } from "./tools/property-request.js";
+import { peopleSearch } from "./tools/people-search.js";
+import { peopleDetail } from "./tools/people-detail.js";
+import { viewingSearch } from "./tools/viewing-search.js";
+import { viewingDetail } from "./tools/viewing-detail.js";
+import { viewingCreate } from "./tools/viewing-create.js";
+import { viewingUpdate } from "./tools/viewing-update.js";
+import { feedbackGet, feedbackSubmit } from "./tools/feedback.js";
+import { teamInfo } from "./tools/team-info.js";
+import { teamAvailability } from "./tools/team-availability.js";
+import { marketingMatchDetail } from "./tools/marketing-match.js";
+import { marketingMatchBatch } from "./tools/marketing-match-batch.js";
+import { marketingMatchRequest } from "./tools/marketing-match-request.js";
+import { marketingEnquiry } from "./tools/marketing-enquiry.js";
+import { customerPreferences } from "./tools/customer-preferences.js";
+import { supplier } from "./tools/supplier.js";
+import { closeDriver } from "./lib/neo4j.js";
+const accountId = process.env.ACCOUNT_ID;
+if (!accountId) {
+    throw new Error("ACCOUNT_ID environment variable is required");
+}
+const server = new McpServer({
+    name: "maxy-loop",
+    version: "0.2.0",
+});
+const ALL_PERMISSIONS = z.enum([
+    "properties", "people", "viewings", "feedback", "team",
+    "marketing", "customer", "supplier",
+]);
+console.error(`[loop] server started, account=${accountId}`);
+// Helper: wrap a tool function in standard error handling
+function toolHandler(fn) {
+    return async (params) => {
+        try {
+            const text = await fn({ ...params, accountId });
+            return { content: [{ type: "text", text }] };
+        }
+        catch (err) {
+            return {
+                content: [{
+                        type: "text",
+                        text: `Error: ${err instanceof Error ? err.message : String(err)}`,
+                    }],
+                isError: true,
+            };
+        }
+    };
+}
+// ─────────────────────────────────────────────────────────────────
+// Key Management Tools (3)
+// ─────────────────────────────────────────────────────────────────
+server.tool("loop-key-register", "Register a Loop CRM API key for a team. Validates the key against Loop's API, encrypts it, and stores it in the graph. Each key maps to one team.", {
+    teamName: z.string().min(1).describe("Human-readable name for this team (e.g. 'Muvin Main Office')"),
+    apiKey: z.string().min(10).describe("Loop API key (X-Api-Key header value)"),
+    permissions: z
+        .array(ALL_PERMISSIONS)
+        .optional()
+        .describe("Endpoint groups this key can access (default: all 8 groups)"),
+}, async (params) => {
+    try {
+        const result = await keyRegister({ ...params, accountId });
+        let text = `Team "${params.teamName}" registered successfully.`;
+        if (result.warning)
+            text += `\n\nWarning: ${result.warning}`;
+        return { content: [{ type: "text", text }] };
+    }
+    catch (err) {
+        return {
+            content: [{
+                    type: "text",
+                    text: `Failed to register key: ${err instanceof Error ? err.message : String(err)}`,
+                }],
+            isError: true,
+        };
+    }
+});
+server.tool("loop-key-deregister", "Remove a registered Loop CRM team key. The key is permanently deleted from the graph.", { teamName: z.string().min(1).describe("Name of the team to remove") }, async ({ teamName }) => {
+    try {
+        await keyDeregister({ teamName, accountId });
+        return { content: [{ type: "text", text: `Team "${teamName}" deregistered.` }] };
+    }
+    catch (err) {
+        return {
+            content: [{
+                    type: "text",
+                    text: `Failed to deregister: ${err instanceof Error ? err.message : String(err)}`,
+                }],
+            isError: true,
+        };
+    }
+});
+server.tool("loop-key-list", "List all registered Loop CRM teams for this account. Shows team names, addresses, and permissions. Never reveals API key values.", {}, toolHandler(async (p) => keyList({ accountId: p.accountId })));
+// ─────────────────────────────────────────────────────────────────
+// People Tools (2) — permission: people
+// ─────────────────────────────────────────────────────────────────
+server.tool("loop-people-search", "Search people in Loop CRM. Without a role, searches all contacts. With a role (buyers/sellers/renters/landlords), returns role-specific results with rich filters.", {
+    role: z.enum(["buyers", "sellers", "renters", "landlords"]).optional().describe("Role to search (omit for all people)"),
+    searchTerm: z.string().optional().describe("Name or contact search"),
+    maxPrice: z.number().optional().describe("Max price (buyers) or max price filter (sellers)"),
+    minPrice: z.number().optional().describe("Min price (sellers)"),
+    minBeds: z.number().optional().describe("Min bedrooms (buyers/renters)"),
+    maxRent: z.number().optional().describe("Max rent (renters only)"),
+    searchAreas: z.string().optional().describe("Comma-separated outcodes e.g. 'SN7,OX12' (buyers/renters)"),
+    propertyTypes: z.string().optional().describe("Comma-separated property types (buyers/renters)"),
+    startDate: z.string().optional().describe("Start date filter (sellers/landlords)"),
+    endDate: z.string().optional().describe("End date filter (sellers/landlords)"),
+    teamName: z.string().optional().describe("Query a specific team only"),
+    limit: z.number().int().optional().describe("Max results (default 200)"),
+}, toolHandler(async (p) => peopleSearch(p)));
+server.tool("loop-people-detail", "Get full details for a specific person by ID. Optionally specify a role (buyers/sellers/renters/landlords) for role-specific detail.", {
+    personId: z.number().int().describe("Person ID"),
+    role: z.enum(["buyers", "sellers", "renters", "landlords"]).optional().describe("Role for role-specific detail view"),
+    teamName: z.string().optional().describe("Query a specific team only"),
+}, toolHandler(async (p) => peopleDetail(p)));
+// ─────────────────────────────────────────────────────────────────
+// Property Tools (4) — permission: properties
+// ─────────────────────────────────────────────────────────────────
+server.tool("loop-property-search", "Search properties in Loop CRM. Queries /property/residential/sales and /property/residential/lettings. Use department to narrow to one type.", {
+    department: z.enum(["sales", "lettings", "both"]).optional().describe("Department (default: both)"),
+    searchTerm: z.string().optional().describe("Address or keyword search"),
+    minPrice: z.number().optional().describe("Minimum price"),
+    maxPrice: z.number().optional().describe("Maximum price"),
+    minBedrooms: z.number().int().optional().describe("Minimum bedrooms"),
+    maxBedrooms: z.number().int().optional().describe("Maximum bedrooms"),
+    propertyStatuses: z.string().optional().describe("Comma-separated statuses (e.g. 'forSale,underOffer')"),
+    propertyTypes: z.string().optional().describe("Comma-separated property types"),
+    teamName: z.string().optional().describe("Query a specific team only"),
+    limit: z.number().int().optional().describe("Max results (default 200)"),
+}, toolHandler(async (p) => propertySearch(p)));
+server.tool("loop-property-detail", "Get full details for a specific property by ID and department. Optionally include a preview hash for the public preview.", {
+    propertyId: z.number().int().describe("Property ID"),
+    department: z.enum(["sales", "lettings"]).describe("sales or lettings"),
+    previewHash: z.number().int().optional().describe("Preview hash for public preview URL"),
+    teamName: z.string().optional().describe("Query a specific team only"),
+}, toolHandler(async (p) => propertyDetail(p)));
+server.tool("loop-property-listed", "Get properties listed on a specific channel (Rightmove, Zoopla, OnTheMarket, website). Optionally include sold properties.", {
+    channel: z.enum(["rightmove", "onTheMarket", "zoopla", "website"]).describe("Listing channel"),
+    department: z.enum(["sales", "lettings", "both"]).optional().describe("Department (default: both)"),
+    includeSold: z.boolean().optional().describe("Include sold gallery (default: false)"),
+    teamName: z.string().optional().describe("Query a specific team only"),
+    limit: z.number().int().optional().describe("Max results (default 200)"),
+}, toolHandler(async (p) => propertyListed(p)));
+server.tool("loop-property-request", "Submit a viewing, callback, or information request for a property. Requires a specific team.", {
+    teamName: z.string().min(1).describe("Team to submit the request through"),
+    propertyId: z.number().int().describe("Property ID"),
+    department: z.enum(["sales", "lettings"]).describe("sales or lettings"),
+    action: z.enum(["viewing", "call-back", "information"]).describe("Request type"),
+    name: z.string().optional().describe("Requester name"),
+    email: z.string().optional().describe("Requester email"),
+    phone: z.string().optional().describe("Requester phone"),
+    message: z.string().optional().describe("Additional message"),
+}, toolHandler(async (p) => propertyRequest(p)));
+// ─────────────────────────────────────────────────────────────────
+// Viewing Tools (4) — permission: viewings
+// ─────────────────────────────────────────────────────────────────
+server.tool("loop-viewing-search", "Search viewings in Loop CRM. Queries /residential/sales/viewings and /residential/lettings/viewings.", {
+    department: z.enum(["sales", "lettings", "both"]).optional().describe("Department (default: both)"),
+    searchTerm: z.string().optional().describe("Search viewings"),
+    appointmentStartDate: z.string().optional().describe("Filter from date (ISO format)"),
+    appointmentEndDate: z.string().optional().describe("Filter to date (ISO format)"),
+    status: z.string().optional().describe("Viewing status filter"),
+    teamName: z.string().optional().describe("Query a specific team only"),
+    limit: z.number().int().optional().describe("Max results (default 200)"),
+}, toolHandler(async (p) => viewingSearch(p)));
+server.tool("loop-viewing-detail", "Get full details for a specific viewing by ID and department.", {
+    viewingId: z.number().int().describe("Viewing ID"),
+    department: z.enum(["sales", "lettings"]).describe("sales or lettings"),
+    teamName: z.string().optional().describe("Query a specific team only"),
+}, toolHandler(async (p) => viewingDetail(p)));
+server.tool("loop-viewing-create", "Create a new viewing in Loop CRM. Creates the viewing and associated buyer/renter record.", {
+    teamName: z.string().min(1).describe("Team to create the viewing for"),
+    department: z.enum(["sales", "lettings"]).describe("sales or lettings"),
+    propertyId: z.number().int().describe("Property ID"),
+    date: z.string().describe("Viewing date (YYYY-MM-DD)"),
+    time: z.string().describe("Viewing time (HH:mm)"),
+    attendeeName: z.string().describe("Attendee full name"),
+    attendeeEmail: z.string().optional().describe("Attendee email"),
+    attendeePhone: z.string().optional().describe("Attendee phone"),
+}, toolHandler(async (p) => viewingCreate(p)));
+server.tool("loop-viewing-update", "Add a note or record feedback for a viewing. For feedback, specify the party: buyer/seller (sales) or renter/landlord (lettings).", {
+    teamName: z.string().min(1).describe("Team that owns the viewing"),
+    viewingId: z.number().int().describe("Viewing ID"),
+    department: z.enum(["sales", "lettings"]).describe("sales or lettings"),
+    action: z.enum(["note", "feedback"]).describe("note or feedback"),
+    text: z.string().describe("Note text or feedback content"),
+    feedbackParty: z.enum(["buyer", "seller", "renter", "landlord"]).optional().describe("Required for feedback: whose feedback"),
+}, toolHandler(async (p) => viewingUpdate(p)));
+// ─────────────────────────────────────────────────────────────────
+// Feedback Tools (2) — permission: feedback
+// ─────────────────────────────────────────────────────────────────
+server.tool("loop-feedback-get", "Get feedback for a specific viewing. Reads from /feedback/residential/{department}/viewings/{id}.", {
+    teamName: z.string().min(1).describe("Team that owns the viewing"),
+    viewingId: z.number().int().describe("Viewing ID"),
+    department: z.enum(["sales", "lettings"]).describe("sales or lettings"),
+}, toolHandler(async (p) => feedbackGet(p)));
+server.tool("loop-feedback-submit", "Submit feedback for a viewing. Writes to /feedback/residential/{department}/viewings/{id}/feedback.", {
+    teamName: z.string().min(1).describe("Team that owns the viewing"),
+    viewingId: z.number().int().describe("Viewing ID"),
+    department: z.enum(["sales", "lettings"]).describe("sales or lettings"),
+    feedback: z.string().describe("Feedback text"),
+}, toolHandler(async (p) => feedbackSubmit(p)));
+// ─────────────────────────────────────────────────────────────────
+// Team Tools (2) — permission: team
+// ─────────────────────────────────────────────────────────────────
+server.tool("loop-team-info", "Get team details from Loop CRM. Returns team name, address, phone, and email.", {
+    teamName: z.string().optional().describe("Query a specific team only (omit for all teams)"),
+}, toolHandler(async (p) => teamInfo(p)));
+server.tool("loop-team-availability", "Get available time slots for a specific agent on a given date.", {
+    agentId: z.string().describe("Agent GUID identifier"),
+    searchDate: z.string().describe("Date to check availability (YYYY-MM-DD)"),
+    teamName: z.string().optional().describe("Query a specific team only"),
+}, toolHandler(async (p) => teamAvailability(p)));
+// ─────────────────────────────────────────────────────────────────
+// Marketing Tools (4) — permission: marketing
+// ─────────────────────────────────────────────────────────────────
+server.tool("loop-marketing-match", "Get matching property detail and optionally the team profile for that match.", {
+    propertyId: z.number().int().describe("Property ID"),
+    department: z.enum(["sales", "lettings"]).describe("sales or lettings"),
+    includeTeamProfile: z.boolean().optional().describe("Include the team profile for this match (default: false)"),
+    teamName: z.string().optional().describe("Query a specific team only"),
+}, toolHandler(async (p) => marketingMatchDetail(p)));
+server.tool("loop-marketing-match-batch", "Get batch matching results for multiple property IDs.", {
+    propertyIds: z.array(z.number().int()).describe("Array of property IDs to match"),
+    department: z.enum(["sales", "lettings"]).describe("sales or lettings"),
+    teamName: z.string().optional().describe("Query a specific team only"),
+}, toolHandler(async (p) => marketingMatchBatch(p)));
+server.tool("loop-marketing-match-request", "Submit a viewing, information, or callback request for a matching property.", {
+    teamName: z.string().min(1).describe("Team to submit the request through"),
+    propertyId: z.number().int().describe("Matching property ID"),
+    department: z.enum(["sales", "lettings"]).describe("sales or lettings"),
+    action: z.enum(["viewing", "information", "callback"]).describe("Request type"),
+    name: z.string().optional().describe("Requester name"),
+    email: z.string().optional().describe("Requester email"),
+    phone: z.string().optional().describe("Requester phone"),
+    message: z.string().optional().describe("Additional message"),
+}, toolHandler(async (p) => marketingMatchRequest(p)));
+server.tool("loop-marketing-enquiry", "Marketing enquiry operations: submit seller enquiries, manage auto-responder interactions.", {
+    teamName: z.string().min(1).describe("Team to submit through"),
+    action: z.enum([
+        "seller-enquiry", "autoresponder-get", "autoresponder-answers",
+        "autoresponder-details", "autoresponder-refer",
+    ]).describe("Enquiry action"),
+    sellerEnquiryData: z.record(z.string(), z.unknown()).optional().describe("Seller enquiry request body (for seller-enquiry)"),
+    autoResponderId: z.number().int().optional().describe("Auto-responder enquiry ID"),
+    autoResponderKey: z.string().optional().describe("Auto-responder key (UUID)"),
+    answers: z.array(z.unknown()).optional().describe("Auto-responder answers array"),
+    details: z.record(z.string(), z.unknown()).optional().describe("Auto-responder details object"),
+}, toolHandler(async (p) => marketingEnquiry(p)));
+// ─────────────────────────────────────────────────────────────────
+// Customer Tools (1) — permission: customer
+// ─────────────────────────────────────────────────────────────────
+server.tool("loop-customer-preferences", "Read or write customer preferences for a person. Action 'read' returns current preferences, 'write' updates them.", {
+    teamName: z.string().min(1).describe("Team for this operation"),
+    personCode: z.number().int().describe("Person code (ID)"),
+    action: z.enum(["read", "write"]).describe("read or write"),
+    preferences: z.record(z.string(), z.unknown()).optional().describe("Preferences object (required for write)"),
+}, toolHandler(async (p) => customerPreferences(p)));
+// ─────────────────────────────────────────────────────────────────
+// Supplier Tools (1) — permission: supplier
+// ─────────────────────────────────────────────────────────────────
+server.tool("loop-supplier", "Supplier operations: maintenance jobs, quotes, board contractor jobs. Supports listing, completing, and quoting.", {
+    teamName: z.string().min(1).describe("Team for this operation"),
+    action: z.enum([
+        "maintenance-jobs", "maintenance-complete", "maintenance-quotes",
+        "maintenance-submit-quote", "board-jobs", "board-complete",
+    ]).describe("Supplier action"),
+    code: z.string().describe("Unique code assigned to the contractor"),
+    jobId: z.number().int().optional().describe("Job ID (required for all actions except maintenance-submit-quote)"),
+    quoteId: z.number().int().optional().describe("Quote ID (for maintenance-submit-quote)"),
+    quoteData: z.record(z.string(), z.unknown()).optional().describe("Quote data (for maintenance-submit-quote)"),
+    completionData: z.record(z.string(), z.unknown()).optional().describe("Completion data (for board-complete)"),
+}, toolHandler(async (p) => supplier(p)));
+// ─────────────────────────────────────────────────────────────────
+// Lifecycle
+// ─────────────────────────────────────────────────────────────────
+process.on("SIGINT", async () => {
+    await closeDriver();
+    process.exit(0);
+});
+const transport = new StdioServerTransport();
+await server.connect(transport);
+//# sourceMappingURL=index.js.map