Run Latchel by asking.
Latchel's official MCP connector puts your work orders, tasks, properties and residents inside Claude. Ask a question in plain English and get an answer from live Latchel data — or open a work order, add a task and close one out without switching tabs.
get_properties get_work_orders get_work_order_logsThree work orders are open at 412 Maple St:
- Water heater, no hot water — vendor accepted, visit booked Thursday 9am.
- Dishwasher leak — sent to a vendor 8 days ago, still unaccepted.
- Garage door — work complete, awaiting invoice.
The dishwasher is the one that's stuck. Want me to add a follow-up task and assign it to your maintenance coordinator?
Illustrative example. Claude answers from your own Latchel data.
Your portfolio, in plain English.
No dashboard filters, no saved views, no exports. Ask the question you actually have, and Claude pulls what it needs from Latchel to answer it.
"What's open right now, and what's overdue?"
Claude reads your live work orders and their activity history, then tells you which jobs have stopped moving — rather than handing you another list to sort.
Work order tracking"Open a plumbing work order for the water heater pilot light in 3B."
Claude asks the few things it needs — which resident, permission to enter — creates the work order in Latchel and hands you back a link straight to it.
"Close out the tasks my team finished yesterday."
Resolve tasks one by one or in a batch, without clicking through each work order to find them.
"Push this follow-up to Monday."
Defer a task to a new date in the same breath as the conversation that made you want to move it.
"Which of my properties had the most emergency work last quarter?"
Claude works across properties, residents and work orders at once, so a question that would have meant three reports becomes one answer.
Reporting and analytics"Draft an owner update on 412 Maple."
Because the data arrives inside your assistant, the next step — the email, the summary, the board update — happens in the same conversation.
Fourteen tools. Read and write.
Most integrations stop at reading. Latchel's connector lets your assistant open work, move it forward and close it out — the same actions your team takes in Latchel every day.
See and start work
Everything from a portfolio-wide sweep down to the full history behind one job.
get_work_ordersList work orders across your portfolio.get_work_order_detailsFull detail on one job, including its open tasks.get_work_order_logsThe activity history — what happened, and when.create_work_orderOpen a new work order against a property and resident.
Move work forward
The follow-ups that hang off a work order, handled without opening it.
get_tasksList tasks, filtered to a work order if you want.get_task_detailsFull detail on a single task.create_taskAdd a task to a work order.resolve_taskMark a task complete.defer_taskReschedule a task to a later date.
Look things up
The records everything else hangs off — so Claude can name a property or a person instead of an ID.
get_propertiesThe properties your company manages.get_residentsThe residents at a property.get_company_usersThe people on your team.get_company_user_groupsHow your team is grouped.
Know who's asking
The connector is never anonymous. Every call runs as a specific Latchel user at a specific company.
who_am_iConfirms which Latchel user is connected, so the assistant knows whose portfolio it is looking at — and so does everything it does next.
Connect it once.
Latchel is listed in Claude's own connector directory, so there is no config file to edit and no key to generate. It takes about a minute.
Find Latchel in Claude
Open Latchel's listing in Claude's connector directory, or search for Latchel under Connectors in your Claude settings.
Sign in with the Latchel account you already have
Claude sends you to Latchel to log in. Nothing new to provision — the connector runs as you, with the access your Latchel user already has.
Approve the connection
You'll see what the connector can reach before you allow it. Approve, and the fourteen tools are available in your next conversation.
Ask it something
Start with "what work orders are open right now?" and go from there. Step-by-step instructions and the current setup screens live in the Help Center.
Scoped to your company, and to you.
Your company's data only
Every tool is scoped to the property management company on your account. The connector cannot reach another company's properties, residents or work orders.
Your login, your permissions
You connect with your own Latchel account rather than a shared key, so what the assistant can see and do matches what you can see and do in Latchel.
Nothing happens off the record
A work order opened through Claude is an ordinary Latchel work order — visible to your team, on the same activity history as everything else.
Questions.
What is MCP?
MCP stands for Model Context Protocol — an open standard for connecting AI assistants to the systems that hold real data. Latchel runs an MCP server; Claude is an MCP client. The connector is what joins the two, so the assistant works from your live Latchel records instead of whatever you paste into the chat.
Is this an official connector?
Yes. Latchel's MCP server was submitted to Anthropic, reviewed, and approved as a community connector. It is listed in Claude's own connector directory, which is where you add it from.
Can it change things, or only read them?
Both. Ten of the fourteen tools read — work orders, tasks, properties, residents, team members and activity history. Four of them act: create a work order, create a task, resolve a task and defer a task. The assistant confirms the details with you before it writes anything.
Does it work with AI assistants other than Claude?
MCP is an open standard, so any assistant that supports remote MCP connectors can connect to the same Latchel server. Claude is where Latchel is officially listed today, and it is the setup our Help Center documents.
Who at my company can use it?
Anyone who can sign in to Latchel. Each person connects with their own account, and the connector inherits that user's access — so it is not something you set up once for the whole company and then have to police. If you don't see the Latchel connector in Claude, your Latchel contact or the Help Center can sort it out.
Do I still need the Latchel app?
Yes — the connector is a second way in, not a replacement. It is at its best for the questions and quick actions that would otherwise mean stopping what you're doing and going hunting. Anything visual, or anything your team works in all day, still belongs in Latchel.
The connector, in ten seconds.
Ten seconds each. A leaking sink, an owner asking questions, a tech on the freeway — three moments when stopping to open a laptop isn't an option, and the work gets done anyway.
Create work orders with your voice
A leak under the kitchen sink in 4B, reported and auto-assigned to the preferred plumbing vendor before the towels come out.
Answer an owner without leaving the table
An owner asks what's happening at his property. The answer comes off the phone lying on the café table, mid-conversation.
Hands-free from the work van
A tech on the freeway, both eyes on the road, working his open jobs by voice alone.
These spots were filmed with ChatGPT. MCP is an open standard, so the same connector works the same way there — Claude is where Latchel is officially listed.
Put Latchel in your assistant.
Add the connector in about a minute, or let us show you the rest of the platform first.