There is no official hotelkit MCP server and no self-serve API key. hotelkit runs an Open API, currently version 3.0 with signed requests, but access is reserved for integration partners: you request it by emailing api@hotelkit.net, and the full documentation sits behind a partner login. For a hotel team today, the route that works is moving the data manually: paste or screenshot your handovers, repair order lists, and checklist statistics into a Claude Project and let Claude do the analysis. If you are a software vendor, the partner API is the sanctioned path to a real integration.
What you are connecting, exactly
hotelkit is one of the most widely deployed hotel operations platforms in Europe. According to hotelkit's own site, more than 4,000 hotels and 180,000 users work in it daily, including Radisson Hotel Group across 350 hotels, Ruby Group, InterContinental Vienna, and Estrel Berlin. Its products cover team collaboration (chats, feeds, shift handovers), housekeeping (digital checklists, drag-and-drop room assignment, PMS-synced room status), and facility management (repair orders, preventive maintenance, asset tracking).
That makes it a dense record of how your hotel actually runs. According to hotelkit's housekeeping page, the module claims up to 24 hours of time saved per week and daily room assignments completed 75 percent faster; its maintenance analytics track repairs by location, request type, and processing time from request to completion. Every one of those data points is something Claude can reason about, if you can get it in front of the model. That is the whole question this guide answers.
The three routes, ranked by honesty
Manual bridge: a Claude Project fed with hotelkit data
No API key required. You copy handover entries, repair order lists, and checklist completion numbers out of hotelkit and into a Claude Project, or screenshot the statistics views, since Claude reads images. Ten minutes a week buys you pattern analysis hotelkit does not do natively: recurring handover themes, repair hotspots by room, checklist compliance drift. The walkthrough below sets this up properly.
The hotelkit Open API, wrapped in an MCP server
Technically the real answer, practically gated. hotelkit's Open API page documents version 3.0, request signing, and a Requests resource, and its API documentation wiki states it is for partners of hotelkit, medikit, and teamkit. Access starts with an email to api@hotelkit.net. If you are a vendor building for hotels on hotelkit, this is your path, and once you hold credentials, wrapping the endpoints in an MCP server is the same pattern as our Hospitable and PriceLabs guides. The verified spec surface is below.
An official or community hotelkit MCP server
As of July 2026, there is none. hotelkit publishes no MCP server, and we could not find a community-built one in any registry. The only public hotelkit API code we found anywhere is a single experimental, unofficial PHP client on GitHub with no releases. If hotelkit ships one, this page will be updated; until then, treat any "hotelkit MCP" you find as unverified.
The hotelkit Open API, as publicly documented
Most of the API documentation is behind the partner login, but hotelkit's public Open API landing page shows more than you would expect. Everything in this table appears verbatim on that page; nothing here is inferred.
The visible endpoints center on a Requests resource, which matches how partners like guest engagement platforms push service requests into hotelkit. What is not publicly documented is a read API for handovers, checklists, or repair statistics; whether partners get one is a question for api@hotelkit.net, and we will not pretend to know the answer.
What a hotel ops team asks Claude
These assume Route 1: the data is pasted or screenshotted into a Claude Project. Every prompt below maps to data hotelkit already captures.
Shift handovers
- "Here are four weeks of front office handover entries. What issues keep recurring, and which ones never got a closing note?"
- "Summarize last night's handover for the GM in five bullet points, most urgent first."
- "Which handover items mention the same guest complaint more than once?"
Repair orders
- "This is our repair order list for June. Which rooms and floors generate the most orders, and what categories dominate?"
- "Compare average time from repair request to completion across these three months. What changed?"
- "Draft a preventive maintenance argument for engineering based on these recurring bathroom repairs."
Checklist compliance
- "Here are screenshots of our housekeeping statistics for the last two weeks. Where does completion drop, and on which shifts?"
- "Which checklist items get skipped most often? Propose a shorter checklist that keeps the critical items."
- "Turn this deep-clean checklist into a training one-pager for new room attendants."
SOPs and language
- "Rewrite this turndown SOP at a B1 German reading level, then give me English and Polish versions."
- "Here is our lost-and-found procedure. Find the gaps a night auditor would hit at 3 a.m."
- "Convert these five handbook articles into a one-page laminated quick reference."
Prerequisites
- A hotelkit login with access to the modules you want to analyze: handovers, repairs, housekeeping statistics. Read access is enough; you are only taking data out.
- A Claude account at claude.ai. Projects, which give you a persistent workspace with instructions and files, are available on paid plans. For a hotel or group, Claude for Work adds admin and data controls.
- A data hygiene rule. Strip guest names, room-guest pairings, and any personal data before pasting. Your repair patterns and checklist stats are operational data; guest identities are GDPR territory and do not belong in the paste.
- No Node.js, no code. Unlike our MCP guides for platforms with self-serve APIs, Route 1 is entirely copy, paste, and ask.
Walkthrough: the weekly ops review setup
Create a Claude Project and teach it your hotel
In Claude, create a Project called something like Hotel Ops - hotelkit. In the Project instructions, describe your property once so you never repeat it: floors and room ranges, outlets, team names, shift times, and what "handover", "repair order", and your checklist names mean in your house. Paste two or three representative SOPs from your digital handbook as Project files.
Pull one week of data out of hotelkit
Three sources, ten minutes:
- Handovers: open the week's shift handover entries and copy the text. Plain text is fine; Claude handles the mess.
- Repairs: copy the week's repair order list: room, category, status, dates. hotelkit's maintenance statistics track orders by location, request type, and processing time, so the raw material is already structured.
- Checklists and housekeeping stats: screenshot the statistics views, such as the housekeeping daily overview with cleaned rooms and completed tasks. Claude reads images, so a screenshot of a chart is data, not decoration.
Remember the hygiene rule: guest names out before anything leaves hotelkit.
Run the analysis
Paste it all into one message and ask for the review:
Follow up like you would with an analyst. "Why do you think floor 3 dominates the repair list?" is a legitimate next question, and the answer is often in the handovers you already pasted.
Make it a standing routine
The value compounds. Because Project conversations share context, week six's review can reference week one's baseline. Keep a simple cadence: same paste every Monday, same four questions, and once a month ask for the long view:
When the routine proves out, that is your business case for asking hotelkit about partner API access, or for asking your PMS vendor what hotelkit data flows through their side. hotelkit's two-way PMS interfaces, like Mews room status sync, mean some operational signals may already be reachable through the PMS API you do have keys for.
Troubleshooting
Claude misreads numbers from my statistics screenshots
Zoom the hotelkit view before capturing so each chart fills the frame, and screenshot one view per image rather than a whole dashboard. If a number matters, state it in text alongside the image ("the daily overview shows 142 cleaned rooms") so the model anchors on your figure, not its reading of a small label.
The paste is too long and the conversation gets slow
Attach the raw text as a Project file instead of pasting it into the chat, then keep the message itself short. For recurring weekly data, one file per week ("handovers-w29.txt") keeps the Project tidy and lets you ask cross-week questions later.
I emailed api@hotelkit.net and have not heard back
The API team also lists a phone line on the Open API page (+43 662 238080) and a contact form on the partnership page. Be concrete in the request: name the modules you want to read, whether you are a hotel or a vendor, and the integration you intend to build. Partner APIs move faster for well-specified asks. In the meantime, Route 1 needs nobody's permission.
My data is in German (or Italian, or Polish)
Paste it as is. Claude works across languages, so German handovers in, English GM summary out is a one-line instruction. This mirrors what hotelkit itself does in-app; its housekeeping product includes translation support to bridge language barriers on the team.
Is this compliant for a European hotel?
Operational data with personal details removed is the safe zone, which is why the hygiene rule in the prerequisites is not optional. If you want AI analysis on data that includes guest information, that is a conversation for your DPO and a Claude for Work agreement with appropriate data processing terms, not a copy-paste workflow. When in doubt, leave it out of the paste.
FAQ
Does hotelkit have a public API?
It has an Open API, but not a public one in the self-serve sense. The landing page documents version 3.0, signed requests, and a Requests resource, then directs developers to email api@hotelkit.net. The full documentation is on a Confluence wiki that blocks anonymous access and describes itself as for partners of hotelkit, medikit, and teamkit. There is no key generation inside the product.
Does hotelkit have an MCP server?
No. As of July 2026 there is no official hotelkit MCP server and no community one we could find. The only public hotelkit API code we located is one experimental, unofficial PHP client on GitHub, with no releases. For contrast, Hospitable ships an official MCP server; hotelkit has not made that move yet.
Can Claude connect to hotelkit directly?
Not through a supported connector today. Without self-serve credentials there is nothing for an MCP server to authenticate against. The manual route in this guide works now; the partner API route works if hotelkit accepts you as an integration partner.
Is hotelkit Knowledge AI the same thing?
No, and the distinction matters. Knowledge AI is hotelkit's built-in assistant, described on hotelkit's site as a 24/7 internal AI assistant, answering questions from content inside your workspace. This guide is about the other direction: getting your operational data out in front of a general-purpose model, where you can cross-reference it with your PMS, your budget, or last year's numbers, and draft in your own voice.
My PMS is Mews or apaleo. Does that change anything?
Possibly. hotelkit's directory lists 60+ integrations, and PMS interfaces like Mews sync data two ways, with room status flowing from hotelkit back to the PMS. Data that crosses into your PMS is reachable through the PMS vendor's own developer platform, where self-serve access is far more common. If your goal is room status or housekeeping signals in Claude, check what your PMS API exposes before waiting on hotelkit partnership.
Where this is heading
hotel operations platforms are converging on the same truth: the documentation your teams create during work, such as handover notes, repair photos, and checklist ticks, is an analyzable asset, not an archive. hotelkit's repair orders are logged with photos and its handbook holds photo and video SOPs, which means the visual record of your hotel's condition already exists inside the platform. Reading that record automatically is what we build at RapidEye: AI that inspects room and turnover photos and catches the damages and misses humans skim past. If your team documents rooms visually, in hotelkit or anywhere else, that record can be working harder than it is.
For the broader toolkit, our Claude guides index covers every platform we have mapped, and the RapidEye API is how inspection intelligence plugs into stacks like this one.