Productivity & Project Management · Tidy + Claude
Tidy MCP with Claude: Book, Reschedule and Track Cleaning Services Automatically
The short answer
Claude works with Tidy through the Model Context Protocol, an open standard that lets Claude securely use software with permissions you control. Once connected, Claude can book cleanings, reschedule services, check appointment status and manage properties through natural language requests, with approvals kept in place for important changes.
What is Tidy?
Tidy is an automation platform for booking and managing cleaning services. It helps property managers, landlords, facilities teams and workspace operators schedule cleanings and keep homes, rental units and offices in good order. Instead of phoning providers or chasing confirmations by e-mail, teams can organise upkeep from one place. Tidy suits organisations that look after many properties or recurring service visits.
How Claude connects to Tidy through MCP
The Model Context Protocol, or MCP, is an open standard that acts like a universal adapter between Claude and other software. It lets Claude use a tool in a controlled way, reading information and taking actions only within the permissions you grant. Tidy offers an MCP server and a direct API, and this connection is made using an API key that your team controls.
Once connected, Claude can typically look up properties, check the status of upcoming appointments, book a new cleaning, or move an existing visit to another time. A team member might simply ask Claude to find every rental due for a clean before a weekend changeover and arrange visits for those units. Claude carries out the request inside Tidy rather than leaving staff to switch between screens.
Permissions and approvals keep people in charge. We set up the API key with the narrowest access your workflow needs, for example allowing bookings and status checks but not account-level changes. Consequential actions such as cancelling a recurring service or changing payment details can require a named person to approve before anything happens. Every action is logged so you can see what was done and by whom.
What you can automate
Changeover cleaning for holiday rentals
A property manager checks booking calendars each evening. Claude identifies units with a guest checkout followed by a new arrival the next day and requests cleaning visits in Tidy for those properties. The manager reviews the list in the morning, and any clashes with existing visits are flagged rather than silently changed.
Rescheduling around tenant or guest needs
When a tenant asks to move an inspection-day clean, staff can tell Claude the new preferred time. Claude checks the current appointment in Tidy, proposes alternative slots and reschedules once the change is approved. This saves repeated back-and-forth e-mails and keeps records accurate.
Status updates for facilities and office managers
Office managers often need to know whether the weekly workspace clean has been confirmed. Claude can check appointment status across several sites and summarise which visits are booked, pending or completed. The summary can be shared with the operations lead before the start of each week.
Recurring upkeep for multi-site portfolios
Organisations running many buildings can set up standard upkeep schedules. Claude can review the portfolio, compare it with the agreed schedule, and book any missing recurring visits in Tidy. Staff focus on exceptions, such as a site that needs a deep clean after an event.
Handling new property onboarding
When a new property joins the portfolio, the team can give Claude its details and ask it to add the property in Tidy and arrange an initial clean. Claude follows the organisation's checklist, so no step is missed and the handover to the new site is consistent.
An end-to-end workflow: Weekend changeover cleaning across a rental portfolio
TriggerEach Thursday at 17:00, the booking calendar for the coming weekend is updated.
Claude reads the upcoming check-outs and check-ins from the booking calendar.
Claude identifies properties where a new guest arrives within a day of a checkout.
Claude checks Tidy for existing cleaning appointments on those properties and avoids duplicates.
Claude books the required cleanings in Tidy and records the confirmation details.
The operations lead reviews a summary and approves any unusual or high-cost bookings.
Claude posts the final schedule to the team's shared ticketing queue so cleaners and staff can see it.
OutcomeChangeover cleans are booked consistently before every weekend, fewer properties are missed, and the operations team spends less time on manual scheduling.
How we set it up
Free automation audit
We review how your team currently books and tracks cleanings, and identify the workflows worth automating first. You receive a short written plan with no obligation.
Secure API key connection
We connect Claude to Tidy using an API key, which your team generates and controls. The key is stored securely and can be revoked at any time. We confirm the connection works before building any workflow.
Workflow design and access limits
We design the end-to-end process across Tidy and your other systems, such as Microsoft 365, your CRM or ticketing tool. We set least-privilege access so Claude can only do what the workflow requires, and define which actions need human approval.
Testing and launch with monitoring
We test the workflow against past bookings and real edge cases, such as same-day changeovers and cancellations. After launch we monitor activity and keep audit logs of every action Claude takes in Tidy.
Team training and handover
We train your staff on how to make requests, review approvals and spot exceptions. You receive documentation and a clear escalation route, so the team stays confident and in control after launch.
Who benefits
- Property manager
- Schedules changeover and routine cleans across many units without manual calls or repeated e-mails.
- Operations director
- Gains a clear view of upcoming and completed visits across sites, supporting better planning.
- Facilities manager
- Keeps workspaces consistently cleaned and can quickly reschedule visits when offices change plans.
- IT or systems lead
- Controls access through a single API key with least-privilege settings and full audit logs.
Security and control
- API key access is limited to the actions each workflow needs, and can be revoked at any time.
- Consequential actions such as cancellations or account changes require approval by a named person.
- Every action Claude takes in Tidy is logged so it can be reviewed and audited.
- Workflows are tested against real cases before launch and monitored afterwards to catch errors early.
- Staff are trained on exceptions and on when to step in, so people remain responsible for decisions.
For teams in the US, UK, India and the Middle East
Organisations in the United States and the United Kingdom can host the Claude workflow in the region that suits their data policies. Companies in India must meet the Digital Personal Data Protection Act, 2023, and we set up hosting and access controls accordingly. Businesses in the UAE and Saudi Arabia must follow local data protection laws, so we select hosting regions that meet those requirements. The right hosting region is chosen during design to meet your specific needs.
Learn more about Claude and MCP
Anthropic's AI model and assistant.
Secure links between Claude and business tools.
How engineers build and change software with Claude.
Hosted agents that run multi-step work.
The open standard Claude uses to connect to tools.
Frequently asked questions
What does the Tidy MCP server do?
The Tidy MCP server lets Claude and other AI tools connect to Tidy in a structured, controlled way. Through it, Claude can typically book cleanings, reschedule services, check appointment status and manage properties using natural language. It acts as a secure bridge, so Claude works inside Tidy within the permissions you set.
Is connecting Claude to Tidy secure?
Security depends on how the connection is set up. We use an API key that your team generates and controls, limit its access to what each workflow needs, and require approval for consequential actions. Every action is logged, and the key can be revoked at any time. We confirm these controls with your IT team before launch.
What can Claude do with Tidy once connected?
Typically, Claude can look up properties, check appointment status, book new cleaning visits, reschedule existing ones and help manage upkeep schedules. The exact actions depend on the access granted and the workflow designed. Sensitive changes can be routed to a person for approval before they are made.
How long does setup take?
Timelines vary with the number of properties, the systems involved and how many workflows you want. A focused setup often takes a few weeks, including testing and staff training. Your free automation audit gives a clearer estimate for your organisation.
Which plan or permissions do I need?
You need access to Tidy with the ability to generate an API key, and an account owner or administrator should approve the access level. The exact requirements depend on your Tidy account setup, so we confirm these during the free audit and recommend the least-privilege option for your workflow.