Skip to main content

Landlord MCP (AI integrations)

First-time workspace setup

Optional after core setup steps 1–15 — requires a live management JWT (Management session authentication) and refreshed tokens after Getting Started — Lockout catch-up after password recovery. Channel map: Automation & AI. Concept pairing: Concepts — Setup sequence after go-live.

VIVIN ships a Landlord Model Context Protocol (MCP) server (apps/landlord-mcp-server in the monorepo) that lets compatible AI clients call typed tools against your workspace using the same authentication model as the management app. It is aimed at operators and integrations that need programmatic access to bookings, listings, properties, and related account data—without building a full custom client.

Pair with other concepts

Contrast booking-scoped tools in Tenant MCP; HTTP auth and contracts are in the API Reference; the management AI Assistant and channel map are in Automation & AI. Topic-to-tool pairing: Landlord MCP section cross-reference. Full pairing matrix: Concepts — Concept cross-reference.

This page is a high-level operator guide. Exact request and response shapes follow the Core API (see API Reference); enable Core Swagger on your API host when you need field-level detail (ENABLE_CORE_API_SWAGGER in Core API environment—see repository AGENTS.md).

Tenant-facing MCP

For booking- and tenant-context tools (listings calendar, portal links, chatbot rules, maintenance, and related Core-backed operations), use the Tenant MCP server (apps/tenant-mcp-server) — see Tenant MCP. The landlord server is account-scoped and targets property-manager workflows.

What you can do with it

Pair with other Landlord MCP sections

Portfolio reads pair with Portfolio KPI review (get-booking-summary, get-vacant-units-next-month), Dashboard KPI cards, and Handling a Late Payment — Step 1 when tools surface overdue balances. Full pairing matrix: Landlord MCP section cross-reference.

Typical use cases:

  • Answer portfolio questions from an AI assistant (occupancy, move-ins, vacancy next month, booking summaries).
  • Look up or adjust listings, properties, and bookings when your token has the right permissions.
  • Use the extended tool set for tenants, maintenance, bills, payments, owners, invoices, and pricing where your role allows the underlying HTTP routes.

Every tool is a thin wrapper around the Core API: 403 or validation errors from the API surface in the MCP response like any other client.

How it connects

Pair with other Landlord MCP sections
TopicDetail
ProtocolModel Context Protocol over HTTP (streamable transport).
Base URLConfigured per deployment; locally often http://localhost:8001 (default PORT in server env).
MCP pathStreamable HTTP traffic is served at /mcp on that host (for example http://localhost:8001/mcp). MCP clients and proxies should target this path, not the bare origin alone.
Core APIAPI_BASE_URL must point at your VIVIN Core API (required).
AuthBearer token (JWT) for the management user; clients create a session over HTTP and reuse Mcp-Session-Id on later requests (same pattern as the tenant MCP server).
API keysWorkspace administrators generate keys under Account Settings → AI / MCP (/settings/mcp) for external clients; paste the key as the Bearer token in the MCP client config snippet on that tab.
OAuthHosted OAuth 2.1 on the Core API host for connector clients (Claude.ai, ChatGPT) — PKCE authorization code + refresh token; see Connector OAuth.

Optional MCP_MAX_SESSIONS (default 300 concurrent sessions) and MCP_SESSION_TTL_MS (default 900000 ms — 15 minutes of idle time before a session is treated as expired) cap load and lifetime; see apps/landlord-mcp-server/src/env.validation.ts. API_BASE_URL is required.

Connector OAuth (Claude, ChatGPT)

Some MCP connectors (for example Claude.ai and ChatGPT) authenticate landlords through Vivin's OAuth 2.1 Authorization Server on the Core API host — not through manually pasted API keys. The landlord MCP server remains the resource server; it already accepts the minted management JWT unchanged.

TopicDetail
DiscoveryGET /.well-known/oauth-authorization-server (and /.well-known/openid-configuration) on your API host — returns authorization_endpoint, token_endpoint, and registration_endpoint.
Dynamic registrationPOST /oauth/register — connectors register redirect URIs at runtime. Only trusted callback origins are accepted (Anthropic https://claude.ai/api/mcp/auth_callback, ChatGPT https://chatgpt.com/connector_platform_oauth_redirect and https://chatgpt.com/connector/oauth/…, plus loopback http://localhost / http://127.0.0.1 for native clients per RFC 8252).
AuthorizeGET /oauth/authorizePKCE is mandatory (code_challenge_method=S256). If the landlord already has a Vivin session cookie, the consent page shows their email and the tool domains they will grant; otherwise they sign in on the consent form. Deny returns access_denied.
TokenPOST /oauth/tokenauthorization_code (with code_verifier) or refresh_token grant. Access tokens are the same management JWT shape as login; tokenSource is stamped mcp for audit. Refresh tokens live 60 days and rotate on each use.
ScopeIssued scope is the intersection of Tool permissions and the consenting user's role — one OAuth scope string per allowed tool domain (bookings, listings, properties, tenants, maintenance, payments, bills, owners, analytics).
Zero-tool blockAuthorization is denied when the landlord has no MCP tools enabled — enable at least one domain on Account Settings → AI / MCP before connecting a connector.
RevocationDisabling a user's AI access or stripping every tool domain on refresh causes access_denied on token refresh — the connector must send the landlord through OAuth again.

API keys remain the right path for IDE configs (Cursor, Claude Desktop) and custom scripts that paste a Bearer token into the Connection snippet. OAuth is for hosted connector platforms that run the authorization-code flow on your behalf. Endpoint reference: MCP OAuth.

OAuth consent — signed-in landlord with allowed MCP tool list (Authorize / Cancel)

Request path

flowchart LR
Client[External AI client]
MCP[Landlord MCP server /mcp]
Core[VIVIN Core API]
Client -->|"Bearer JWT, then Mcp-Session-Id"| MCP
MCP -->|"REST via API_BASE_URL"| Core

From MCP tools to HTTP

Pair with other Landlord MCP sections

Swagger and webhook routes pair with API Reference hub, Webhooks & Notifications, and Integrations & Distribution (inbound channel POSTs are HTTP — not MCP tools). Full pairing matrix: Landlord MCP section cross-reference.

Each tool maps to one or more Core API routes. When you need field-level request and response bodies (for example to shape a payload on a write tool), use Integration Swagger on your API host—Try it out shows paths, parameters, and schemas the same way integrators debug listing and booking traffic. See the API Reference index for how to open it and authorize.

Integration Swagger UI — listings operations expanded with Try it out

Inbound partner webhooks (channels → Vivin)

MCP tools call the Core API on your behalf; marketplace channels can also POST lifecycle events into Vivin at integration-scoped webhook routes (Housing Anywhere, Uniplaces). Those paths are HTTP integration surfaces — inspect them in Integration Swagger on your API host, not in the MCP tool catalogue.

IntegrationInbound route (pattern)
Housing AnywherePOST /housinganywhere-integration/{landlordKey}/webhook
UniplacesPOST /uniplaces-integration/{landlordKey}/webhook

Integration Swagger — Housing Anywhere POST webhook expanded with path parameter and request body schema

Integration Swagger — Uniplaces POST webhook expanded with landlordKey path parameter and request body schema

Full event names, auth headers, and payload fields: Webhooks & Notifications.

Request flow (at a glance)

flowchart LR
subgraph clientSide[Your environment]
C[MCP client\nIDE, script, or bridge]
end
subgraph vivinSide[VIVIN services]
L[Landlord MCP server\nHTTP streamable /mcp]
A[Core API\nsame tenancy rules as management]
end
C -->|Initial Bearer JWT\nlater Mcp-Session-Id| L
L -->|API_BASE_URL\ntyped tools map to HTTP routes| A

Each tool call is a normal Core API request under the hood: the JWT must belong to a management user with the same module permissions they would need in the browser.

Tool overview

Pair with other Landlord MCP sections

Write tools mirror management UI permissions — pair create-booking with Processing a New Booking, list-payments / get-payment with Handling a Late Payment — Step 4, and list-tickets with Operations module. Contrast booking-scoped reads in Tenant MCP. Full pairing matrix: Landlord MCP section cross-reference.

registerLandlordTools in apps/landlord-mcp-server/src/server.ts registers tools in two layers:

  1. Core landlord tools (14) — portfolio intelligence, calendar, properties, listings, and bookings.
  2. Extended account tools (36) — registerLandlordCoreApiTools in landlord-core-api-tools.ts; each write tool sends a JSON payload object that must match the Core API body for that route (use Swagger on the API host when Core Swagger is enabled). Together these layers register 50 MCP tool identifiers for a typical build (verify in server.ts + landlord-core-api-tools.ts if you fork or gate tools).

Read-only and intelligence

ToolPurpose
get-booking-summaryBooking counts and short active/upcoming lists for the authenticated account.
get-upcoming-move-insUpcoming move-ins with property and listing names (prefer those fields to identify the unit).
get-vacant-units-next-monthNext-month vacancy / occupancy snapshot.
get-listing-calendarCalendar for a tenant’s unit (needs tenant email or phone identifiers, optional bookingId).

Bookings, properties, and listings

ToolPurpose
create-bookingCreate a booking (POST /bookings; body matches Core CreateBookingWithInlineTenantDto).
get-bookingFetch one booking by ID.
upload-booking-contractUpload an unsigned contract PDF (base64); Core may clear any previous signed contract for that booking—treat as sensitive.
create-property / get-property / list-properties / update-propertyProperty CRUD and paginated list. list-properties pages through GET /properties/portfolio (limit/offset; default limit 50, max 100). When the response includes nextOffset, call again with offset=nextOffset until it is null. The legacy bulk GET /properties list was removed — always page.
create-listing / get-listing / update-listing / list-listingsListing (unit) create and update under a property or by listing ID. list-listings is read-only and returns the thin account-wide projection from GET /listings/options (id, internal name, tags, property) — not the partner partial GET /listings calendar feed in Integration Swagger.

Extended account tools (REST-aligned)

Registered tool identifiers (MCP kebab-case names):

AreaTools
Tenantslist-tenants, get-tenant, create-tenant, update-tenant, get-tenant-bookings
Maintenancecreate-ticket, list-tickets, get-ticket, update-ticket, add-ticket-comment, close-ticket
Billscreate-bill, list-bills, get-bill
Bookingslist-bookings, update-booking, cancel-booking, extend-booking
Listings & rentlist-listings (GET /listings/options), set-listing-pricing-month, get-listing-pricing-table
Payments & invoiceslist-payments, get-payment, create-manual-payment-in, generate-invoice
Ownerslist-owners, create-owner, get-owner, update-owner
Analytics (portfolio metrics)get-revenue-summary, get-finance-overview, get-debt-summary, get-cost-summary, get-maintenance-closure-rate — gated by the Analytics tool domain; revenue/overview figures are Finance-page data (#3183), not legacy /kpi/* analytics

Finance-sourced portfolio metrics (#3183)

Pair with Finance Overview

Assistant and MCP revenue answers must match Finance → Overview and Income — not Analytics ADR/RevPAR charts. Enable the Analytics domain on Account Settings → AI / MCP (requires analytics.module or finance.module on the role). Full pairing matrix: Landlord MCP section cross-reference.

Landlord AI surfaces (AI Chat, WhatsApp Genius, external MCP clients) answer “how much did we make / collect / invoice / are we owed?” from the Finance domain so numbers match the management Finance page:

ToolWhat it returnsUse when…
get-finance-overviewOne-call Finance → Overview snapshot for a month window (default: current month): income expected (paid + scheduled + in debt), income status split, cash collected (system + manual), invoiced / pending invoicing, debt (total, uncovered, aging, top debtors), overdue deposits, pending payouts, collection rate, cash-flow-by-monthAny “how much did I collect / invoice / am I owed?” question — prefer this over stitching several tools
get-revenue-summaryMonthly income expected trend from GET /finance/revenue-summary (paid + scheduled + still in debt for rent, admin fee, cleaning fee, and others), plus previous-period and same-months-last-year comparison (default last 6 months, max 12)Pure monthly income trend / period comparison — not cash collected and not occupancy/ADR
get-debt-summary / get-cost-summary / get-maintenance-closure-ratePortfolio debt, cost, and maintenance closure reads under the same Analytics tool domainNarrow follow-ups after Overview triage

Expected vs collected: incomeExpected / get-revenue-summary totals are not cash in the bank. For “how much did we actually receive?”, use cashCollected (and the system/manual split) from get-finance-overview. For vacancy and occupancy, use get-vacant-units-next-month — do not treat revenue tools as ADR/RevPAR substitutes (those stay on Analytics charts in the UI).

Permissions: Tools live in the MCP Analytics domain (Off / Read-only on AI / MCP → Tool permissions). Core API also requires finance.module (and analytics.module where applicable) so operators without Finance access cannot pull ledger figures through the assistant.

Verify answers: Reconcile assistant output on Finance → Overview (Income chart, Debt Aging, KPI cards) during Portfolio KPI review — Step 7. See FAQ — Why don’t Genius revenue numbers match Analytics?.

Destructive and financial actions

Tools such as cancel-booking and upload-booking-contract can change money, contracts, or availability. Restrict tokens, test on non-production workspaces first, and rely on Core API permissions so only intended roles can invoke write tools.

Permissions and safety

Pair with other Landlord MCP sections

JWT scope and role gates pair with Users and roles, Resetting a Management User Password (token refresh after rotation), and scope contrast in Tenant MCP. Full pairing matrix: Landlord MCP section cross-reference.

  • All data access is scoped to the authenticated account the same way as the management frontend; there is no cross-tenant escape hatch in the tool design.
  • Write tools require the same module and permission flags as the Core API (for example bookings.create, listings.edit, bookings.edit_items).
  • Prefer read-only tools (booking summary, vacancy snapshot, move-ins, calendar) for analytics and reporting rather than ad-hoc database access.

Relation to in-app AI Assistant

Pair with other Landlord MCP sections

In-app AI Assistant uses the same tool catalogue in-process — pair with AI Chat module, Deep Links — AI Assistant, surface choice in Automation & AI — Choosing surfaces, and internal cost polling on AI usage API (landlord_chat on GET /ai-usage/summary). Full pairing matrix: Landlord MCP section cross-reference.

Tools > AI Assistant (/ai-chat) is another consumer of the same Landlord MCP tool definitions the HTTP server exposes — portfolio reads and permitted writes run inside Core API with the signed-in management user’s JWT, not through a separate Mcp-Session-Id client. Differences for operators:

In-app AI ChatLandlord MCP (HTTP)
UIConversation history, Examples, inline rename/archiveYour MCP-compatible client (IDE, custom bot)
AuthManagement session cookie / bearer from the browserBearer JWT + Mcp-Session-Id on follow-up requests
AudienceVivin internal accounts only in the current productAny role with a valid management JWT and tool permissions

See AI Chat module, Automation & AI, and AI usage API when you audit landlord_chat token cost during Portfolio KPI review — Step 7.

Landlord MCP section cross-reference

Use this table when one Landlord MCP topic naturally leads into operator UI, HTTP contracts, or a module tab — each row links to the docs you should read before or after wiring an external MCP client.

| Landlord MCP topic | Pair with these docs | | --------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | What you can do with it | Portfolio KPI review, Portfolio KPI review — Step 1 (get-booking-summary before wide month ranges), Portfolio KPI review — Step 3 (list-bookings, get-vacant-units-next-month), Portfolio KPI review — Step 7, Dashboard module, Analytics module, Notifications — Payment overdue alerts, Handling a Late Payment — Step 1 | | How it connects | Management session authentication, API Reference hub, Automation & AI — External AI clients | | From MCP tools to HTTP | API Reference — Webhooks & notifications, Integrations & Distribution, Full listing feeds | | Tool overview — read-only and intelligence | Onboarding a New Property — Step 7 (get-vacant-units-next-month, get-booking-summary), Bookings module, Booking Lifecycle, Sales — Multicalendar, Manual block hygiene (get-vacant-units-next-month, get-listing-calendar during Step 5 reconciliation), Managing a Check-in — Step 1 (get-upcoming-move-ins), Portfolio KPI review — Step 2 (get-booking-summary), Portfolio KPI review — Step 7 (get-vacant-units-next-month, get-upcoming-move-ins, get-listing-calendar), Cancelling a Booking — Step 5 (get-listing-calendar, get-vacant-units-next-month), Notification triage — Step 1 (get-upcoming-move-ins), Notification triage — Step 2 (get-booking-summary), Notification triage — Step 5 (get-booking-summary) | | Tool overview — bookings, properties, listings | Onboarding a New Property — Step 1 (list-owners, create-owner via extended tools), Onboarding a New Property — Step 2 (create-property, get-property, list-properties), Onboarding a New Property — Step 3 (create-listing, get-listing), Onboarding a New Property — Step 5 (list-listings, get-listing with unavailabilities, get-listing-calendar, list-properties, get-property), Onboarding a New Property — Step 6 (get-property utility IDs), Onboarding a New Property — Step 7 (list-properties, list-listings read-only pass), Processing a New Booking — Step 1 (list-bookings, get-booking; list-listings, get-listing with unavailabilities, get-listing-calendar, get-property for overlap checks), Processing a New Booking — Step 2 (create-booking), Processing a New Booking — Step 3 (get-booking, get-listing-pricing-table), Processing a New Booking — Step 4 (upload-booking-contract), Processing a New Booking — Step 5 (create-manual-payment-in), Entering Monthly Utility Bills — Step 4 (get-booking — overage spot-check), Settings > Tenant categories (default for integration-created tenants; create-booking does not set category), FAQ — Assign tenant category for direct booking, Listings module, Glossary — Tenant category | | Tool overview — extended account tools | Onboarding a New Property (list-owners, create-owner Step 1; get-listing-pricing-table, set-listing-pricing-month Step 3; list-bills, create-bill Step 6 contrast), Finance module, Operations module, Tenants module, Tenants — Tenant category filter, Settings > Tenant categories, Settings > Owners, Notifications — Payment overdue alerts, Handling a Late Payment — Step 1, Handling a Late Payment — Step 4 / Step 4b (create-manual-payment-in pending until operator approval), Handling a Late Payment — Step 6 (get-booking-summary, list-bookings, list-payments, get-payment, get-booking, list-tickets, get-ticket; cancel-booking write tool — confirm refund type in UI), Using in-app support (Vivin product tickets when JWT scope or tool coverage fails), Resetting a Management User Password — Step 3 / Troubleshooting (refresh Bearer JWT and Mcp-Session-Id after management password rotation), Processing a New Booking — Step 5b (list-payments, get-payment; approval remains operator UI), Entering Monthly Utility Bills — Step 1 (list-bills — prior-period baseline) / Step 2 / Step 3 / Step 4 (get-booking when external clients spot-check Payment plan overage lines; contrast Tenant MCP get-payment-info) / Step 4b (list-payments, get-payment; approval remains operator UI) / Step 5 (create-bill, list-bills, get-bill; prefer UI Upload PDF for AI extraction), Managing a Check-in — Step 2 (list-tickets, create-ticket, get-ticket, update-ticket, close-ticket, add-ticket-comment; Cost allocation remains operator UI) / Step 3 (get-booking, list-payments, get-payment) / Step 3b (list-payments, get-payment; approval remains operator UI), Managing a Check-out — Step 1 / Step 2 (list-bookings, get-booking, get-booking-summary, create-ticket, list-tickets, get-ticket) / Step 5 (get-booking, list-payments, get-payment; pending until Step 6b; Mark refunded and dispute freeze remain operator UI) / Step 6b (list-payments, get-payment; approval remains operator UI), Cancelling a Booking — Step 2 / Step 2a (list-payments, get-payment, get-booking, create-manual-payment-in) / Step 4 (cancel-booking write tool; confirm refund type in UI) / Step 6 (list-tickets, get-ticket, close-ticket), Portfolio KPI review — Step 4 (get-listing-pricing-table, set-listing-pricing-month), Portfolio KPI review — Step 5 (list-tickets, get-ticket), Portfolio KPI review — Step 7 (list-payments, get-payment), Notification triage — Step 1 (list-tickets when ticket-category pings dominate the bell list), Notification triage — Step 3 (list-bookings, get-booking, list-tenants, get-tenant, get-tenant-bookings, list-payments, get-payment when search narrows the slice; Unread / Read pills remain operator UI only), Notification triage — Step 4 (get-booking, list-payments, get-payment, create-manual-payment-in), Notification triage — Step 5 (list-bookings; read-state changes remain operator UI only), Glossary — Tenant category | | Finance-sourced portfolio metrics | Finance → Overview, Finance → Income, AI Chat — How answers are produced, Automation & AI — WhatsApp Genius, AI / MCP — Analytics domain, Portfolio KPI review — Step 7, FAQ — Genius revenue vs Analytics | | Permissions and safety | Users and roles, Resetting a Management User Password (refresh Bearer JWT after management password rotation), Tenant MCP (scope contrast) | | Relation to in-app AI Assistant | AI Chat module, Management Frontend Deep Links — AI Assistant, Automation & AI — Choosing surfaces, AI usage API (landlord_chat ledger) | | Lockout catch-up after password recovery | Sign-in restored; concept validation backlog accumulated | Common Workflows — Lockout catch-up, Getting Started — Lockout catch-up, Resetting a Management User Password — Step 3 | | Pending manual receipt approval | Recorded bank transfers still pending until Approve payments | Common Workflows — Pending manual receipt approval, Finance — Pending manual payments, FAQ — Manual receipt still pending | | Reject/revert mistaken receipts | Duplicate or wrong-booking receipts after Approve | Common Workflows — Reject/revert mistaken receipts, Payment Allocation — Correcting mistaken receipts, Glossary — Credit note (payment reject/revert) | | Portfolio segmentation by tenant category | Review one tenant segment across modules | Common Workflows — Portfolio segmentation, Settings > Tenant categories, Finance — Tenant category filter, Tenants — Tenant category filter | | Notification row-click navigation | Portfolio MCP reads after /notifications row-click | Concepts — Notification row-click navigation, Common Workflows — Notification row-click navigation, Notifications module — Notification row-click navigation | | Payment alert to receivables triage | list-bookings debt context vs alert triage | Concepts — Payment alert to receivables triage, Common Workflows — Payment alert to receivables triage, Handling a Late Payment — Step 1 | | Confirmation alert triage | New booking MCP tools vs confirmation alerts | Concepts — Confirmation alert triage, Common Workflows — Confirmation alert triage, Processing a New Booking — Step 5b |


Pair with other Landlord MCP guide sections

Related below links this concept to modules, workflows, settings, and escalation paths. Pair Documentation map & escalation with Concepts hub — Documentation map & escalation; pair Portfolio reads & month-end reconciliation with Portfolio KPI review. Topic-to-section pairing in sections above: Landlord MCP section cross-reference. Full hub matrix: Concept cross-reference.

Documentation map & escalation

Pair with other Landlord MCP guide sections
Pair with other Landlord MCP guide sections

Scope contrast & automation surfaces

Pair with other Landlord MCP guide sections

Scope contrast & automation surfaces bullets pair with the matching topic rows in Landlord MCP section cross-reference above. Full pairing matrix: Concept cross-reference.

Portfolio reads & month-end reconciliation

Pair with other Landlord MCP guide sections

Portfolio reads & month-end reconciliation bullets pair with the matching topic rows in Landlord MCP section cross-reference above. Full pairing matrix: Concept cross-reference.

Bookings, inventory & channel context

Pair with other Landlord MCP guide sections

Bookings, inventory & channel context bullets pair with the matching topic rows in Landlord MCP section cross-reference above. Full pairing matrix: Concept cross-reference.

Finance, operations & messaging writes

Pair with other Landlord MCP guide sections

Finance, operations & messaging writes bullets pair with the matching topic rows in Landlord MCP section cross-reference above. Full pairing matrix: Concept cross-reference.

Deeper workflow reads

Pair with other Landlord MCP guide sections

Workflow reads pair with Common Workflows hub subsection index and Portfolio reads & month-end reconciliation above. Each workflow sub-guide reciprocates with [Deeper workflow reads](../concepts/landlord-mcp.md#deeper-workflow-reads) anchors on Landlord MCP bullets — hub parity: Concepts hub — Deeper workflow reads. Full pairing matrix: Landlord MCP section cross-reference · Concept cross-reference.

Deeper concept reads

Pair with other Landlord MCP guide sections

Deeper API reads

Pair with other Landlord MCP guide sections

Lockout catch-up after password recovery

Pair with other Landlord MCP guide sections

Pending manual receipt approval

Pair with other Landlord MCP guide sections

Payment tools read pending Layer 2 state until operators Approve — pair with Payment Allocation. Hub parity: Common Workflows — Pending manual receipt approval. Full pairing matrix: landlord-mcp-section-cross-reference · Concept cross-reference.

Reject/revert mistaken receipts

Pair with other Landlord MCP guide sections

Portfolio segmentation by tenant category

Pair with other Landlord MCP guide sections

Portfolio reads should respect tenant-category filters on operator UI — pair with Bookings — Other filters. Hub parity: Common Workflows — Portfolio segmentation by tenant category. Full pairing matrix: landlord-mcp-section-cross-reference · Concept cross-reference.

Notification row-click navigation

Pair with other Landlord MCP guide sections

External list-notifications / portfolio tools complement but do not replace /notifications row-click — operators still finish Notification triage — Step 4 in the UI. Hub parity: Concepts — Notification row-click navigation. Full pairing matrix: Landlord MCP section cross-reference · Concept cross-reference.

Payment alert to receivables triage

Pair with other Landlord MCP guide sections

MCP debt answers should follow single-booking payment overdue row-click triage — open booking Payment Plan before list-bookings portfolio sweeps. Hub parity: Concepts — Payment alert to receivables triage. Full pairing matrix: Landlord MCP section cross-reference · Concept cross-reference.

Confirmation alert triage

Pair with other Landlord MCP guide sections

Upcoming confirmation alerts on new imports still need UI receipt approval — MCP get-booking does not replace Processing a New Booking — Step 5b. Hub parity: Concepts — Confirmation alert triage. Full pairing matrix: Landlord MCP section cross-reference · Concept cross-reference.

Finance debt receivables triage

Pair with other Landlord MCP guide sections

Landlord MCP portfolio tools surface receivables summaries — verify on Finance → Overview Debt Aging before trusting tool output for month-end sign-off. Hub parity: Concepts — Finance debt receivables triage. Full pairing matrix: Landlord MCP section cross-reference · Concept cross-reference.

Finance Income status drill-down

Pair with other Landlord MCP guide sections

MCP finance reads return booking debt context — Income chart segment clicks still require Finance → Overview for month-scoped payment-line modals. Hub parity: Concepts — Finance Income status drill-down. Full pairing matrix: Landlord MCP section cross-reference · Concept cross-reference.

Cash flow forecast drill-down

Pair with other Landlord MCP guide sections

Month-end MCP reconciliation pairs Cash flow forecast bar-click modals with tool collections output — distinct from Income status segments. Hub parity: Concepts — Cash flow forecast drill-down. Full pairing matrix: Landlord MCP section cross-reference · Concept cross-reference.

Key glossary terms

Pair with other Landlord MCP guide sections

Glossary rows pair with Glossary cluster cross-reference and concept pages that cite the same terms. Full pairing matrix: Landlord MCP section cross-reference · Concept cross-reference.

Module documentation hubs

Pair with other Landlord MCP guide sections