Read only
The assistant looks things up, compares and reports. Nothing in Abide.Rent changes. A good start for owners and for landlords who want answers about their own properties.
Connect Abide.Rent to the AI assistant you already use. Ask about your properties in plain English, and let it do the work — logging repairs, chasing certificates, adding tasks — in your account, with your permissions.
Which gas safety records expire before Christmas? Book the renewals with Hartley Heating and tell me what’s left.
list_certificates4 gas safety records expire before 25 Decembercreate_contractor_jobGas safety renewal × 4, with Hartley Heatingsend_contractor_jobJob links sent to the contractorlist_deadlinesChecked the rest of DecemberFour gas safety records expire before Christmas. I’ve raised a renewal job for each with Hartley Heating and sent them; the visit dates will come back through Abide.Rent.
Still for you: 12 Mill Lane has no record that the tenant was given last year’s certificate.
It reads what you can see in Abide.Rent, links every answer to the record, and says when something is missing.
You decide when you connect. Change your mind by removing it and connecting again.
The assistant looks things up, compares and reports. Nothing in Abide.Rent changes. A good start for owners and for landlords who want answers about their own properties.
It can also log repairs, add notes and tasks, record payments, raise contractor jobs and send reminders — only what your role allows, each change recorded under your name, as if you had made it in the app.
Your assistant can use Abide.Rent together with your email, calendar, files and accounts — no integration project, no export and re-import.
Each connector is added and approved separately in your assistant, under that provider’s terms. Which ones are available depends on your assistant and your plan with it.
Every API operation an assistant may use is a tool — 432 of them, in 19 groups — each one calling the same API the app uses, with the same permissions and legal holds. Signing, serving, payments and who has access stay with people in the app.
38 tools · The properties on the account, their tenancies, tenants and occupiers, who on the team looks after each, sales and changes of agent, and read-only share links.
23 tools · The agency's landlord clients, their addresses for notices, the monthly compliance statements written for them, the weekly summary, and a landlord's own portfolio.
25 tools · The records kept on each tenancy - move-in and move-out checklists, inventory and check-out reports, Right to Rent checks, guarantees, agreement to email service of notices, tenants' forwarding addresses, sharers leaving, and incidents kept as possession evidence.
10 tools · What is due across properties and tenancies (certificates, deposits, notices, inspections and more), who answers for each duty, PRS Database readiness, reminders, deadline evidence packs, and legal holds that stop records being deleted.
14 tools · Gas safety records, EICRs, EPCs, licences and other certificates on each property, the tenants' copies, bulk upload, and the business's own memberships and registrations.
8 tools · Property inspections booked with notice and carried out, their reports, and repeating inspection schedules that create tasks.
35 tools · Repairs reported by tenants or staff, the target dates they carry, the account's contractors, the jobs sent to them, and landlord approval for jobs over the maintenance limit.
36 tools · Section 13 rent reviews from pricing to landlord approval, the evidence-based rent range for an area, local market insight, and published First-tier Tribunal rent decisions.
29 tools · Section 13 rent increases (Form 4A) and Section 8 notices (Form 3A) prepared as drafts, served notices recorded and evidenced, what happened after service, possession steps, tenants' notices to quit, and written statements of terms. Signing and serving stay with a person in the app.
33 tools · Tenancy deposits and their protection, prescribed information, proof of payment, holding deposits under the Tenant Fees Act 2019, and settling the deposit at the end of a tenancy (deductions, the tenants' answers, the landlord's approval, scheme disputes and release).
19 tools · Each tenancy's rent account (schedule, payments, running balance and arrears), payments recorded by hand or from a bank CSV, arrears for possession grounds, the agency's rent roll, and the workspace's own Abide.Rent plan and invoices.
8 tools · Tenants' requests to keep a pet (Renters' Rights Act 2025) - submitted by a tenant or recorded for them, further information within the 28-day answer period, a superior landlord's consent, the landlord side's written decision, and withdrawal.
27 tools · Documents drafted from the workspace's templates and sent for signature in order (statements of terms, management agreements, letters), the templates and clause library behind them, emails sent from Abide.Rent, and replies to them routed to the person responsible. Signing itself is done by each signer.
24 tools · Notes on properties, tenancies and other records (internal, or shared with the landlord), mentions and pins, tasks with owners and due dates, moving a person's properties to colleagues, and hiding rows from your own lists.
10 tools · Workspace reports and registers (compliance risk, evidence gaps, arrears, notices, deposits, Right to Rent, voids and more), the dashboard and today's priorities, rent increase opportunities, who was told what and when, and the audit history of any record.
40 tools · The workspace's team and seats, invitations to tenants and landlords, holiday cover, leave, the on-call rota, the team calendar, working hours and closure days, branches, scorecards, joiners' onboarding, and planning a colleague's exit. Giving or changing anyone's access stays with an owner in the app.
21 tools · Exporting the workspace's records, background data jobs (imports and exports), bulk actions over many records at once, saved views of the app's lists, and the filterable fields of each list.
24 tools · Your own profile and notification choices, your in-app notifications, the workspace's business details and logo, its set-up profile and getting-started checklist, and support tickets with Abide.Rent.
5 tools · For a named tenant connected from the tenant portal - their tenancies, the landlord or agent, rent, deposit, notices served on them, pet requests, and the safety certificates given to them.
Whatever access you give it, these are not tools. A person does them in Abide.Rent.
https://mcp.abide.rent/mcp.Assistants sign in as you: Abide.Rent never gives them your password, and API keys do not work here. For an agency or landlord account, only the owner can connect one, on Portfolio or the free trial. Tenants can connect their own tenancy free. What the assistant reads goes to the company that runs it, under its terms: connect only an assistant your business has approved for tenants’ personal data.
The same operations are on the REST API. The OpenAPI 3.1 document is public, keys come from your account on Portfolio, and there is no sales call to get access. Tell us what you need connected and we build it, free.
Yes. Add https://mcp.abide.rent/mcp as a custom connector in Claude, ChatGPT or Cursor and sign in. Every API operation an assistant may use is a tool. The assistant works in one account, with your permissions, read only or read and make changes as you choose. Serving or signing a notice, payments and changing who has access are never tools. Abide.Rent is not listed in connector directories.
You choose when you connect it. Read only lets it look things up and report. Read and make changes lets it also log repairs, add notes and tasks, record payments, raise contractor jobs and send reminders, within what your role allows. Every change is recorded under your name. To switch, remove the connection and connect again.
Yes, if your assistant has those connectors too. Claude or ChatGPT can, for example, read which certificates expire from Abide.Rent and draft the emails in Gmail, or check the rent roll against payments in your accounts software. Each connector is approved separately in the assistant, under that provider’s terms.
No. The MCP server only accepts assistants that sign in as a person, so every action has a named person, their chosen account and their chosen access. API keys are for the REST API, for systems rather than people.
Portfolio or the free trial, for an agency or landlord account; only the account owner can connect one. Tenants can connect an assistant to their own tenancy free.
No. Serving a notice is never available through the API and will never be an MCP tool. A person records service in the product.
Start at /llms.txt, then /llms-full.txt for longer excerpts. The product API is described at /openapi.json and /platform/reference. Nothing here is legal advice. Tribunal figures need the Open Government Licence attribution.
Connect your assistant during the free trial. One-month free trial of every feature. No card needed.