MCP required.
The Rentvine MCP Cookbook.
Sixteen copy-paste recipes for running your portfolio in plain English, once Claude is connected directly to your Rentvine account. Reads run free. Writes wait for your go-ahead. Money never moves without a human.
16
Recipes
3 courses
10
Minutes
to connect
0
Spreadsheets
or exports needed
Setup.
Three steps, ten minutes.
Once you're connected, every recipe below is a prompt away. Nothing here needs an engineer.
-
Connect Claude to Rentvine.
Follow the MCP Setup Guide (your onboarding contact can send it). You'll need the Claude Desktop app, a Rentvine API access key and secret, and your account ID.
-
Verify the connection.
In Claude Desktop, Settings → Developer should show rentvine running, and a new chat will list Rentvine tools.
-
Know the safety model.
Reads run freely within your permissions. Money movement isn't available through the MCP by design. Before anything is created or changed, the AI shows you exactly what it intends to submit and waits.
This is your live account.
Reads are harmless. Writes, like work orders, notes, prospects, and inspections, are real once you confirm them. Every recipe flags the steps that write with a writes · confirmed badge.
The mental model.
Everything hangs off one spine.
A five-minute mental model that makes every recipe easier to adapt.
- Portfolio
- Property
- Unit
- Lease
Portfolios are the ownership and accounting boundary. Properties are physical addresses. Units are rentable spaces. Leases carry tenants, terms, charges, and payments. Work orders and inspections attach to a property. Notes and files attach to almost any record. Transactions live on lease ledgers. This is why "the lease at 118 Maple" works as a prompt on its own.
Reads
list_*, get_*, run_report
- Balances, leases, work orders, vendors, reports
- Run freely, as often as needed to answer a question
- Zero risk, nothing changes in your account
Writes
create_*, update_*, and similar
- Work orders, inspections, notes, prospects, appliances
- Always previewed and confirmed with you first
- Real changes to your live account, after you confirm
What's deliberately absent: nothing in the MCP can move money. No tools record payments, issue refunds or credits, pay or approve bills, or send owner distributions. Financial visibility is rich. Financial movement stays with humans, in the Rentvine app.
How MCP handles your data.
How to use it safely.
Before you start typing.
Prompting tips that apply everywhere.
- Anchor on an address or name. "The lease at 118 Maple" works, the AI resolves addresses to properties, units, and leases on its own.
- Ask for the plan first. Add "tell me what you're going to look up before you do it" when trying something new.
- Scope your timeframes. "This month," "next 90 days," "since June 1" all translate cleanly into filters.
- Writes are a two-step. The AI shows you exactly what it intends to submit and waits for your go-ahead, every time.
- Big portfolios paginate. Asking for "the totals" or "the top 10" is faster than asking to enumerate 500 properties.
Sixteen recipes, three courses.
Pick your course.
Starters Five-minute wins you can run today.
Who it's for
Property managers and ops leads doing a daily or weekly sweep.
What you'll get
A prioritized brief with amounts, addresses, and links into Rentvine.
Writes to your account
None, this is a pure read.
The prompt
Give me a morning triage of my portfolio:
1. Leases with a balance due, top 10 by amount, with tenant name and address
2. Open work orders, grouped by status, flagging anything older than 14 days
3. Leases ending in the next 60 days and where their renewals stand
Keep it tight, amounts, addresses, and links. End with the three things you'd handle first today and why.
| What Claude does under the hood | |
|---|---|
| Tools | Why |
| list_leases | Pull active leases (paginated, with totals) |
| get_lease_balance_due | Check outstanding charges on leases with balances |
| list_work_orders, list_work_order_statuses | Open maintenance, mapped to your account's actual status names |
| list_lease_renewals, list_leases | Upcoming expirations and any renewal already in motion |
Variations
- Scope it down: "...for the [Lakeview] portfolio only"
- Change the cadence: weekly version, include new prospects and inspections completed this week
- Make it a habit: same format every time so you can compare day to day
- Turn a finding into action: "create a work order for #2 on that list"
Tips
- On large portfolios, ask for "top 10 by amount" instead of a full delinquency dump
- "Older than 14 days" works because work orders carry creation dates, adjust to your SLA
- If your statuses are customized, the AI reads your actual status list first
Who it's for
Anyone who knows the question but not which report answers it, and report power users.
What you'll get
The right report, run with sensible filters, plus a plain-English readout of trends and outliers.
Writes to your account
None, this is a pure read.
The prompt
I want to dig into [topic, e.g. receivables, vacancy, owner payouts] for [scope, e.g. my whole portfolio / the [Lakeview] portfolio / last month].
1. Show me which built-in reports cover this and what each one is for
2. For the best fit, tell me what filters and columns it supports, then run it with the ones that matter
3. Give me the results as a tight table, sorted by [what matters most, e.g. amount owed]
Finish with a three-sentence readout: the headline number, the biggest outlier, and the one thing you'd act on first. Include links into Rentvine where you can.
| What Claude does under the hood | |
|---|---|
| Tools | Why |
| list_report_types | Browse the full catalog and match your topic to real report names |
| get_report_meta | See which columns and filters that report supports |
| run_report | Execute with chosen columns, filters, sorting, and grouping |
| list_saved_reports, run_saved_report | Reuse reports your team already configured |
Variations
- Discovery only: which reports cover a topic, then pick one to run
- Month-over-month: same report, same format, differences called out
- Skip straight to a saved report
- Feed one report into another flow, e.g. a vacancy report into open work orders
Tips
- Always give a timeframe or filter to keep it fast
- Ask by outcome, not report name
- Totals reflect the full result set even when only the first page shows
- If your team already built the report, run the saved version
Who it's for
Property managers and leasing coordinators keeping units filled.
What you'll get
An availability board, vacant now, vacating soon, and prospect interest per unit, with links into Rentvine.
Writes to your account
None, this is a pure read.
The prompt
Build me an availability board for [my whole portfolio]:
1. Vacant now, every unit with no active lease, with address, unit details, and the most recent lease's end date
2. Vacating soon, leases with a move-out pending or notice given in the next [45] days, with the expected move-out date
3. Prospect interest, for each unit above, any prospects who've inquired, with source and date
One table per section, links into Rentvine, and flag any vacant unit with zero prospects, that's your marketing gap.
| What Claude does under the hood | |
|---|---|
| Tools | Why |
| list_properties, list_property_units | Enumerate every rentable unit |
| list_leases, list_lease_statuses | Map units to active leases |
| list_prospects | Match prospect inquiries against each vacant or soon-to-be-vacant unit |
Variations
- One portfolio at a time
- Marketing-gap view: vacant units with zero prospect interest
- Run alongside the lease renewal pipeline for the full occupancy horizon
- Make it a weekly habit to spot days-vacant trends
Tips
- "Vacating soon" leans on your account's actual lease status names
- Dedupe prospects by name or email so interest counts aren't inflated
- On large portfolios, scope to one portfolio or property group
- Lots of prospects but no showings is a follow-up problem, not a marketing one
Who it's for
Anyone who answers the phone, PMs, assistants, front desk.
What you'll get
A 5-line whisper brief with balance, open work orders, and the last note on file.
Writes to your account
None, this is a pure read.
The prompt
[Maria Delgado] is on hold, I'm picking up in 20 seconds. Give me a 5-line whisper brief:
1. Who: name, unit, lease status and end date
2. Balance: what they owe right now, if anything
3. Maintenance: open work orders on their unit
4. Last touch: most recent note about them or their lease
5. Watch out: one thing I should know before I say hello
One line each, links where you have them. Go.
| What Claude does under the hood | |
|---|---|
| Tools | Why |
| list_tenants, get_tenant | Resolve the caller by name |
| get_lease | Their lease, its status, and end date |
| get_lease_balance_due | Itemized unpaid charges, totaled |
| list_work_orders | Anything open on their unit |
| list_notes | The last few notes, so you know what was already said |
Variations
- If it's an owner instead of a tenant, jump to owner call prep
- Log the call afterwards with a note
- Ask "what did we last promise this tenant?"
- If it turns into a repair request, hand off to maintenance dispatch
Tips
- Tenant lookups default to current tenants, say "including past tenants" to widen
- An address alone works too, the AI resolves the property and lease
- Two tenants with the same name is common, the AI will ask which one
- Balance is an itemized list, ask to "break that balance down"
No recipes match your search.
Mains Day-to-day workflows that save hours every week.
Who it's for
Property managers and maintenance coordinators handling incoming tenant issues.
What you'll get
A verified work order on the right unit, the right vendors asked for bids, and links to everything.
Writes to your account
Yes, every write is previewed and confirmed before anything is saved.
The prompt
A tenant just reported: "[dishwasher leaking under the sink]" at [412 Oak Ave], unit [B].
1. Confirm the property, unit, and active lease, and that the reporter is actually a tenant on it
2. Pull the appliance record for the [dishwasher], brand, model, and whether it's under warranty
3. Check open work orders on this unit and property so we don't create a duplicate
4. If it's new, draft a [high]-priority work order with a clear description, show me exactly what you'll create before saving
5. Then suggest 2 to 3 [plumbing] vendors we actually use and request estimates due by [Friday], preview that too before anything goes out
End with links to the work order and the lease.
| What Claude does under the hood | |
|---|---|
| Tools | Why |
| list_properties, list_property_units | Resolve address + unit to the real property and unit |
| list_leases, list_lease_tenants | Find the active lease and verify the reporter lives there |
| list_unit_appliances | Brand, model, and warranty status |
| list_work_orders | Duplicate check before creating anything |
| list_work_order_statuses, create_work_order | Draft using your account's actual statuses, confirmed before creating |
| list_vendor_trades, suggest_vendors_for_trade | Map the issue to a trade and surface vendors you've used |
| request_work_order_estimates | Send estimate requests with a due date, confirmed first |
| list_work_order_estimates, record_work_order_estimate, select_work_order_estimate | Compare bids, log a phoned-in quote, approve the winner |
Variations
- Chronic offender: set up a recurring quarterly plumbing check instead
- Attach the evidence: upload tenant photos to the work order
- Leave a trail: add a note about access details
- Keep it in-house: assign to an internal tech instead of a vendor
Tips
- The duplicate check is where this saves real time, multifamily tenants often report the same leak
- Vendor quotes by phone or email just need you to tell the AI the amount
- Selecting an estimate approves the bid, it doesn't pay anyone
- Dispatched work orders surface automatically in the next morning triage
Who it's for
Property managers running collections at the start of the month.
What you'll get
A sorted delinquency table with itemized balances and deposit context, plus a personalized reminder draft per tenant.
Writes to your account
None, this is a pure read. Reminder drafts live in chat until you send them yourself.
The prompt
It's the start of the month, run my delinquency review:
1. Find every active lease with an overdue balance and pull the exact amount due
2. Itemize what's outstanding on each, rent vs. late fees vs. everything else, and note the date of the oldest unpaid charge
3. Show any deposits held on the lease, for context next to the balance
4. List the tenants on each lease with their contact info
Give me one table sorted by amount owed (largest first): tenant, address, total due, breakdown, oldest unpaid charge, deposit held, and a link into Rentvine.
Then draft a [friendly but firm] payment reminder for each tenant, personalized with their name and exact balance, asking for payment by [the 5th], signed from [your name, your company]. I'll review and send them myself.
| What Claude does under the hood | |
|---|---|
| Tools | Why |
| list_leases | Pull active leases flagged with an overdue balance |
| get_lease_balance_due | Exact amount outstanding on each delinquent lease |
| list_lease_charges | Itemize unpaid charges with dates for aging |
| list_lease_deposit_balances | Deposits held, for context |
| list_lease_tenants | Who's on the lease and how to reach them |
Variations
- One portfolio at a time
- Aging buckets: 0-30, 31-60, 61+ days with subtotals
- Export as raw markdown for your team wiki
- Late-fee cross-check against your configured policy
Tips
- Balance due is the itemized list of unpaid charges, totaled for you, voided charges skipped
- Run this right after rent posts and after your grace period ends
- Deposit held is context only, applying one happens in Rentvine itself
- Set the drafts' voice once and the AI carries it through every message
Who it's for
Property managers and portfolio leads planning the next renewal cycle.
What you'll get
A pipeline view, expiring leases, renewal status, current rent, and any red flags, with links into Rentvine.
Writes to your account
None, this is a pure read.
The prompt
Build me a lease renewal pipeline for the next [90] days:
1. Every lease expiring in that window, address, unit, current rent, and end date
2. For each one: is a renewal already in motion? If so, where does it stand (offered, accepted, pending)?
3. Flag any tenant with an outstanding balance, I want to know before we send an offer
4. Flag any lease that's already month-to-month
Sort by end date, soonest first. End with the renewals I should start this week and the ones that need a conversation instead of an offer.
| What Claude does under the hood | |
|---|---|
| Tools | Why |
| list_leases | Find leases ending inside the window |
| list_lease_renewals | Check whether a renewal is already in motion |
| get_lease_renewal | Detail on each in-flight renewal |
| get_unit, get_property | Context for weighing terms |
| get_lease_balance_due | Flag delinquent tenants before an offer goes out |
Variations
- Tighten the window, or run 30/60/90 side by side
- Group by portfolio with a subtotal of expiring rent
- Add a rent-roll style summary table
- Chase the holdovers: month-to-month leases, oldest first
Tips
- Renewals live on individual leases, narrow to one portfolio on large windows
- Run at the start of each quarter and again mid-quarter
- The balance check means no renewal offer goes to a tenant who's behind
- Ask for the same layout every quarter to compare easily
Who it's for
Property managers and portfolio leads who own the owner relationship.
What you'll get
A structured brief, portfolio health, money picture, maintenance status, and talking points, with links into Rentvine.
Writes to your account
None, this is a pure read.
The prompt
[Owner name] is calling me in 20 minutes. Build me a one-page brief:
1. Portfolio health: their portfolio(s), every property and unit, and what's occupied vs. vacant, with current rents
2. Money picture: activity on their properties over the last [90] days, rent collected, bills recorded, anything unusual, plus current ledger balances
3. Maintenance: open work orders on their properties with status, age, and cost so far, flag anything expensive or stalled
4. Anything I should remember: notes on their account or properties, especially pinned ones or anything owner-facing
Format it in that order, tight enough to fit one page, with links into Rentvine on every line item. End with 3 to 5 talking points in plain English, lead with good news, and don't let me get surprised by anything on this list.
| What Claude does under the hood | |
|---|---|
| Tools | Why |
| list_owners, get_owner | Resolve the caller to their owner record |
| list_portfolios, get_portfolio | Find the portfolio(s) tied to that owner |
| list_properties, list_property_units | Every property and unit under those portfolios |
| list_leases | Active leases per property |
| list_transactions, list_ledgers | Money activity and account balances |
| list_work_orders | Open maintenance, with status and age |
| list_notes | Account and property notes worth remembering |
Variations
- Make it monthly, a recurring owner update
- Zoom into one property with full detail
- Prep for a hard conversation on a large repair bill
- Bolt on renewal context if a lease ends soon
Tips
- Ledger lookups are name-based, give the owner's exact name
- If the owner has a common name, add one distinguishing detail
- A 90-day money window keeps the brief fast
- "Lead with good news" sets a very different tone
Who it's for
Property managers and inspection coordinators closing the loop after route days.
What you'll get
A work order per actionable finding, notes tying everything together, and the next inspection scheduled.
Writes to your account
Yes, every write is previewed and confirmed. Work orders use a batch-confirm: you see the full list, approve once, then they're created.
The prompt
Inspections were completed this week, help me turn the findings into tracked maintenance:
1. Pull inspections completed in the last [7] days for [the Lakeview portfolio / all properties] and summarize the findings from each
2. For every actionable finding, propose a work order: property, unit, description, priority, and the likely trade
3. Show me all proposed work orders in one table so I can approve them in a single go, then create them
4. Add a note to each inspection listing the work orders that came out of it
5. Schedule the next [routine] inspection for each of these units [6 months] out, run the dates by me first
Format: one section per property, with links to each inspection and each new work order. Flag anything you weren't sure deserved a work order so I can decide.
| What Claude does under the hood | |
|---|---|
| Tools | Why |
| list_inspections | Recent completed inspections |
| get_inspection | Full detail per inspection |
| create_work_order | One per finding, shown as a full list before creating |
| create_note | A note tying findings to work orders on each inspection |
| create_inspection | The next inspection, previewed and confirmed |
Variations
- Move-out inspections: show deposit held alongside each finding
- Seasonal findings: set up a recurring work order instead of a one-off
- Appliance findings: update the condition and serial number on the record
- Hand off to vendors for estimates once work orders exist
Tips
- Make the proposal table carry everything you'd check by hand
- Tell the AI your threshold up front for what needs a work order
- Name your inspection types and statuses if they're customized
- Decide one work order per unit vs. combined up front
Who it's for
Leasing agents and property managers who own the prospect pipeline.
What you'll get
A funnel health snapshot, a one-table cleanup batch you approve in a single go, and a paper trail.
Writes to your account
Yes, every write is previewed and confirmed. The cleanup uses a batch-confirm.
The prompt
My leasing funnel needs a tune-up:
1. Pull all my prospects and prospect sources, and give me the state of the funnel: total count, how many are older than [30/60/90] days with no movement, how many are duplicates (same email or phone), and the count per source
2. Propose a cleanup batch: archive the stale leads past [60] days and the duplicate copies (keep the most complete record of each person), and fix the keepers that just need an edit, missing source, wrong status, typo'd contact info
3. Show me the whole batch in one table, every archive and every edit, with a reason for each, so I can approve it in one go, then run it
4. On each record that absorbed duplicates, add a note listing what was archived into it and why
Keep it tight: names, ages, sources, and links to each prospect. End with the funnel's before-and-after counts.
| What Claude does under the hood | |
|---|---|
| Tools | Why |
| list_prospects | The full funnel, page by page |
| list_prospect_sources | Map source IDs to real names |
| get_prospect | Spot-check borderline records before proposing anything |
| archive_prospect | Stale and duplicate leads, approved once, then archived |
| update_prospect | Fixable keepers, shown in the batch before saving |
| create_note | A note documenting duplicates folded into each survivor |
Variations
- Source performance: which sources actually produce applicants
- Weekly cadence: flag new duplicates, only propose archives
- New-lead intake: add a prospect from a phone call
- Scope down to prospects interested in one portfolio
Tips
- Duplicate emails are normal, treat matching email or phone as one person
- Archive, don't delete, it stays reversible
- Pick a staleness window that matches your market
- Ask for summary numbers first, cleanup proposal second
Who it's for
Property managers and maintenance coordinators who suspect their appliance data has drifted.
What you'll get
A gap report per unit, cleaned-up appliance records, and a warranty-expiry watchlist you can act on.
Writes to your account
Yes, every write is previewed and confirmed. Record fixes use a batch-confirm.
The prompt
Audit my appliance registry:
1. Go through [all my properties / the [Lakeview] portfolio], unit by unit, and list every appliance on record
2. Flag anything missing a brand, model, or serial number
3. Flag any warranty that's already expired or expires in the next [90] days
4. Propose fixes for the records where I can tell you the missing details, show me the full list of proposed changes in one table so I can approve them in a single go
Format: one section per property, worst gaps first, with links to each unit and appliance. End with the warranty watchlist sorted by expiry date.
| What Claude does under the hood | |
|---|---|
| Tools | Why |
| list_properties, list_property_units | Walk the portfolio, unit by unit |
| list_unit_appliances | Appliances per unit |
| update_appliance | Fill in missing details or correct warranty dates, batch previewed |
| create_appliance | Add appliances that never made it into Rentvine |
| upload_appliance_file | Attach a manual, receipt, or warranty doc, confirmed before upload |
Variations
- Big portfolio: go property by property
- Make the watchlist a recurring habit
- A finding needs a repair, hop into maintenance dispatch
- Pair with inspections photographing data plates on route days
Tips
- Serial numbers are what warranty claims hinge on, prioritize those
- Set the expiry window to match your procurement lead time
- Attach the purchase receipt the day you create a record
- The audit only fixes what you can tell it, expect a "needs a site visit" list at first
Who it's for
Property managers running turns who want every step tracked, not remembered.
What you'll get
A per-lease runbook, inspection scheduled, deposit context, turn work orders opened, and a status note tying it together.
Writes to your account
Yes, every write is previewed and confirmed. Inspections and turn work orders use a batch-confirm.
The prompt
Run my move-out runbook:
1. Pull leases flagged pending move-out, plus any ending in the next [30] days, tenant names and addresses included
2. For each one, schedule the move-out inspection for [the last day of the lease], show me the full list of proposed inspections and dates in one table, get my go-ahead, then create them
3. Show the security deposit held on each lease alongside it, just the numbers, I'll handle deposit decisions in Rentvine
4. Pre-create the standard turn work orders for each unit: [rekey, carpet clean, paint touch-up], one proposal table, one approval
5. Add a note to each lease summarizing where its runbook stands: inspection date, deposit on file, work orders opened
Format: one section per lease with links to the lease, the inspection, and each work order. End with anything that still needs a decision from me.
| What Claude does under the hood | |
|---|---|
| Tools | Why |
| list_leases, list_lease_tenants | Leases pending move-out or ending soon |
| create_inspection | A move-out inspection per lease, proposed then confirmed |
| list_lease_deposit_balances | The deposit held, read-only |
| create_work_order | Standard turn items, batch-proposed |
| create_note | A runbook note on each lease |
Variations
- Single move-out deep dive with balance owed included
- Weekly sweep, skip leases that already have an inspection scheduled
- Feed completed inspections into the inspection follow-up recipe
- Twenty units at once, graduate to the turn-season command center
Tips
- Deposit and credit decisions stay human on purpose
- Lease status names vary by account, the AI reads your actual list
- Decide your standard turn scope once and reuse it
- The lease note makes the weekly re-run cheap to compare
No recipes match your search.
Chef's table Advanced moves for power users and ops leads.
Who it's for
Owners of the business, leadership, regional managers, anyone accountable for more than one portfolio.
What you'll get
A ranked scorecard with sub-scores per pillar, a cross-check against your own reports, and a narrative on the biggest mover.
Writes to your account
None, this is a pure read.
The prompt
Build me a portfolio health scorecard across [all my portfolios / the Lakeview, Summit, and Harborview portfolios]. Score each portfolio 0 to 100 using exactly this rubric, so runs stay comparable:
Occupancy (30 pts): 30 x occupied units / rentable units
Delinquency (30 pts): 30 x (1 - total overdue balance / monthly scheduled rent), floored at 0
Maintenance (20 pts): 20 x share of open work orders that are 30 days old or younger
Renewal coverage (20 pts): of leases ending in the next [90] days, 20 x share with a renewal already in motion
Cross-check the occupancy and rent inputs against a rent-roll report filtered to each portfolio, and tell me if anything doesn't reconcile. Flag any accounting diagnostics that would make me distrust the numbers.
Output every run: a ranked table (rank, portfolio, total score, four sub-scores, one-line watch item), a short narrative on the biggest mover, and links into Rentvine for anything scoring under [70].
| What Claude does under the hood | |
|---|---|
| Tools | Why |
| list_portfolios | Enumerate the portfolios to score |
| list_properties, list_property_units, list_leases | Rentable units vs. active leases for the occupancy pillar |
| get_lease_balance_due | Overdue amounts, totaled |
| list_work_orders | Open maintenance, aged against the 30-day line |
| list_leases, list_lease_renewals | Renewal status, lease by lease |
| run_report | Independent cross-check against a rent-roll report |
| get_accounting_diagnostics | Optional sanity pass for bookkeeping red flags |
Variations
- Make it a trendline, re-run monthly with the identical prompt
- Single-portfolio deep dive to the property level
- Hand the story behind a score to owner call prep
- A low delinquency score hands off to delinquency review
Tips
- Keep the rubric verbatim between runs or the trendline stops being comparable
- Renewals are looked up per lease, keep the window at 90 days for speed
- Always give the report a portfolio filter and a timeframe
- Treat a bad score as a to-do list, not a button
Who it's for
Property managers and maintenance coordinators deciding who gets dispatched.
What you'll get
A per-vendor scorecard table plus a clear bucket for each vendor: give more work, watch, or have a conversation.
Writes to your account
None, this is a pure read.
The prompt
Build me a vendor scorecard covering [the last 12 months]:
1. Start with my full vendor roster and the trades each vendor covers
2. For each active vendor, pull their work order history: total jobs, how many are open right now, and the average age of those open ones
3. Then their estimate behavior: estimates requested vs. submitted vs. selected, give me a submit rate and a win rate, always with the underlying counts, not just percentages
4. Finish with one table, sorted by win rate: vendor, trade(s), jobs, submit rate, win rate, average open age, with a link to each vendor in Rentvine
5. Under the table, bucket every vendor into "give more work," "watch," or "have a conversation," with one line of reasoning each
Flag any trade where I'm leaning on a single vendor, and call out anyone with open work orders older than [30] days.
| What Claude does under the hood | |
|---|---|
| Tools | Why |
| list_vendors, list_vendor_trades | The roster mapped to trades |
| get_vendor | Profile detail on each vendor in scope |
| list_work_orders | Job volume and age of anything still open |
| list_work_order_estimates | Estimate activity grouped per vendor |
| suggest_vendors_for_trade | Who's configured and recently used per trade |
Variations
- Single-trade shootout, e.g. just your plumbers head-to-head
- Estimate-turnaround focus, who's slow to bid
- Coverage audit, does the go-to vendor match who's earning the work
- Dispatch the next job to the winner via maintenance dispatch
Tips
- Suggested vendors reflect who's configured, not who's best, that's what the scorecard adds
- Watch sample sizes, 2 jobs at 100% isn't better than 40 jobs at 70%
- Rates only count what's logged in Rentvine
- An old open work order isn't automatically the vendor's fault, investigate first
Who it's for
Property managers and ops leads staring down a peak move-out season.
What you'll get
A complete turn board, who's leaving, what each unit still needs, everything missing created in one confirmed batch, and a capacity view.
Writes to your account
Yes, every write is previewed and confirmed. This recipe uses the batch pattern.
The prompt
It's turn season, build me a turn command center:
1. The turn list. Every lease ending in the next [45] days with no renewal in motion, plus anyone already pending move-out. Group by property, with tenant, unit, and end/move-out date.
2. Readiness check, per unit. Does a move-out inspection already exist? Are turn work orders already open ([paint, deep clean, carpet, rekey])? Mark each unit ready, partial, or nothing scheduled.
3. Batch setup. For everything missing, propose it all as ONE batch: a move-out inspection per unit, our standard turn work orders, and estimate requests to our usual [painting/cleaning/flooring] vendors. Show me the complete list first, I'll approve once, then create everything.
4. Capacity view. Finish with a week-by-week picture of the next [8] weeks: move-outs, inspections, and turns landing each week, and which week is overloaded.
Tight format, one table per section, links to every lease, unit, and work order, and end with the three units most likely to slip and why.
| What Claude does under the hood | |
|---|---|
| Tools | Why |
| list_leases, list_lease_statuses | Leases ending in the window plus pending move-outs |
| list_lease_renewals | Renewals checked lease by lease |
| list_inspections, list_work_orders | Per unit, what's already on the books |
| suggest_vendors_for_trade | Line up a vendor per trade |
| (batch preview) | Every proposed inspection, work order, and estimate request laid out as one list |
| create_inspection, create_work_order, request_work_order_estimates | Created only after your go-ahead |
Variations
- Weekly re-run, diff only, show what changed
- Make it seasonal with a recurring HVAC or gutter work order
- Zoom in mid-crunch on one property
- The unit-level checklist for a single departure lives in the move-out runbook
Tips
- The renewal check runs lease by lease, scope to one portfolio to keep it fast
- Size the window honestly, 45 days catches the wave early, 30 keeps the batch reviewable
- Decide your standard turn scope once and reuse the wording every run
- Deposit dispositions and money movement stay with you, in Rentvine
Who it's for
PMs and accounting staff answering "why do I owe this," especially when the conversation has gotten tense.
What you'll get
A dated timeline, a reconciled total with the math shown, source documents, and a draft explanation letter ready for your review.
Writes to your account
None, this is a pure read.
The prompt
[Tenant name] at [address] is disputing their balance, they say they owe [nothing / $X], the ledger says [$Y]. Build me an evidence pack I could hand to anyone:
1. Itemized balance, every unpaid charge with date, description, and amount. Note any voided charges separately and leave them out of the total.
2. Money timeline, every transaction on this lease (charges, payments, credits) in date order, oldest first. Pull the full detail on the contested entries, e.g. the March late fees, so we can see exactly what happened and when.
3. Policy check, do the late fees on the ledger match our configured late-fee policy (amount, grace period)? Flag any that don't.
4. Paper trail, notes on this lease that touch the dispute, plus the signed lease and any move-in docs from the attachments. Download the lease so we can check the charged amounts against what the contract actually says.
Then give me: a dated timeline table, a reconciled total with your math shown line by line, a discrepancies section (be honest, if the tenant is right about anything, say so plainly), and a DRAFT explanation letter in calm, plain English that I'll review and send myself. Links into Rentvine throughout.
| What Claude does under the hood | |
|---|---|
| Tools | Why |
| list_leases, list_lease_tenants | Resolve the tenant and the exact lease |
| get_lease_balance_due, list_lease_charges | Itemized unpaid charges, voided ones flagged and excluded |
| list_transactions, get_transaction | Full money timeline, line-level detail on contested entries |
| get_lease_credit | Full detail on any credits referenced |
| list_late_fee_settings | Your configured policy, compared against what was charged |
| list_notes, list_attachments, download_file | Dispute context, signed lease, move-in docs |
Variations
- Deposit dispute flavor, show what's held vs. what's being claimed
- Escalation memo, formal tone for an owner or attorney
- Plain-English rewrite, explain it like the tenant would understand
- If it's a pattern across the portfolio, zoom out to delinquency review
Tips
- If the AI reports no attachments, double-check it resolved the right lease first
- Name contested entries as precisely as possible for full transaction detail
- Keep voided charges in the timeline even though they're out of the total
- The honesty clause is the whole point, a pack that concedes an error is more defensible
No recipes match your search.
Sixteen recipes. One connected assistant.
Copy a prompt, edit the brackets, and run your portfolio in plain English. Reads run free, writes wait for your go-ahead, and money never moves without a human.
Screenshots throughout this cookbook are illustrative, with sample data. The Rentvine MCP is in active development and recipes are verified against a live account, but tool availability may change. Find a prompt that works great, or one that falls flat? Tell the AI "send this to Rentvine as feedback."