Connect your portfolio to ChatGPT and Claude
Most property software asks you to come to it. You open the system, find the screen, run the report, and read the answer there. That is fine when the question is one the software anticipated. It is poor when the question is the one you actually have — “which of the Kensington properties has a gas certificate expiring before the tenancy ends, and which of those has a tenant who has already refused access once?”
Tekniti ships an MCP connector. You connect your Tekniti account to ChatGPT or Claude the same way you would connect any other app, and then you ask the assistant you already have open. It queries your portfolio directly and answers from your data rather than from anything general it read about UK lettings.
What it can see
Properties, tenancies, contacts, compliance obligations, certificates, maintenance tickets, rent and arrears, notices, documents and the audit trail — all scoped to your organisation, and to your branch if your access is limited to one. It is your account’s view, not a wider one.
Questions it answers well
What happens when you ask it to do something
This is the part worth reading carefully, because it is where most “AI can take actions” claims get uncomfortable.
The connector can act — record a rent payment, close an obligation, decide a pet request, serve a notice. But no tool call performs the action. Asking for one produces a proposal: a description of exactly what would happen, carried in a short-lived signed token that stamps the organisation, the user and the whole payload. Confirming takes that token and nothing else.
01
You ask
“Record £1,200 received against September rent for 14 Alma Road”
02
It proposes
The full action, described back to you, signed. Nothing has changed
03
You confirm
The action runs exactly as described, or not at all
04
It is logged
Written to the hash-chained audit trail with the actor attached
The design constraint that makes this trustworthy is a small one, and it is deliberate: the confirmation call accepts only the token. It has no amount parameter, no property parameter, no override. A model cannot describe £600, obtain your agreement, and then run £6,000, because there is nowhere for the second figure to go and it cannot re-sign the first. The absence of a parameter is the guarantee.
Read-only means read-only
Read access and write access are separate grants, chosen on the consent screen when you connect and checked on every single call. A read-only connection is genuinely read-only — not “read-only because we did not offer it the other tools”, which is a policy rather than a control.
You can see every connected client under Settings → Connected apps, including whether each one can act or only read, and revoke any of them there. A connection that has expired says so rather than appearing active.
Why we think this matters more than a chatbot
There is a chat assistant inside Tekniti too, and it is good. But it lives inside Tekniti, which means it only helps once you have decided the question is a Tekniti question. A great deal of property management does not announce itself that way. You are drafting a reply to an owner, or preparing for a call, or working through a list in a document, and the portfolio question arrives in the middle of something else.
Being reachable from the assistant already open on your screen is a different kind of useful. It also means the integration surface is not ours to define — anything that speaks MCP can connect, so what you build around it is your decision rather than a queue item on our roadmap.
What it is not
Setup is in the app under Settings → Connected apps, and takes about a minute. If you want to see it against your own book before committing to anything, write to hello@tekniti.ai and we will walk through it.
If you manage rental properties and want to see how Tekniti handles this automatically, get in touch at hello@tekniti.ai.