Default
Chekin MCP connector
The Chekin connector brings your housings, rooms, reservations, police accounts and stat accounts into Claude, ChatGPT, Cursor and any MCP client, so your team can ask about properties and guest registration setup in plain language and update them as themselves.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Chekin to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Chekin once
-
Open Connections, choose Add connection, and pick Chekin.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Chekin API key. One person generates a token in Chekin and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect Chekin to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Connect Chekin to ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Connect Chekin to Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Chekin to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Chekin through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Operations
Set up a new property in minutes
Create the housing for a new listing, add its rooms in one go, and attach the police and stat accounts it reports through, all from a conversation.
-
Front desk
Check today's reservations before guests arrive
Ask which reservations are coming up across your housings and see the details you need before the first guest walks in.
-
Compliance
Confirm every property reports to the authorities
List your housings alongside their police accounts and stat accounts to spot any property that is missing a registration or statistics setup.
-
Property management
Keep housing details current
After an owner changes an address, a name or a room layout, catch the Chekin housing and its rooms up without opening the dashboard.
-
Onboarding
Bring a portfolio of rooms in at once
Hand over a list of rooms for a housing and have them created in bulk instead of adding them one at a time.
-
Operations
Retire and restore properties safely
Remove a housing you no longer manage, and if the contract comes back, restore it rather than rebuilding it from scratch.
Try asking
- “List every Chekin housing added this month”
- “Which Chekin rooms have no reservations next week?”
- “Show police accounts linked to our Madrid housings”
AI tools
Chekin tools for your AI agents
64 tools are ready to call through Elaichi's MCP endpoint the moment you connect Chekin, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Chekin gets you
6 screens from the product, each doing one job for your Chekin account.
The agent
Ask about housings, get real answers.
Type a question in plain language and read it straight from live Chekin records.
- housings
- rooms
- reservations
- police accounts
Ask Elaichi to work across your apps.
List every Chekin housing added this month
Which Chekin rooms have no reservations next week?
Show police accounts linked to our Madrid housings
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor reach Chekin.
One governed MCP endpoint over OAuth, no SDK and no shared API key.
Copy the endpoint
Tool catalog
64 Chekin tools ready to call.
Housings, rooms, reservations and police accounts covered, with no custom code to write.
- Chekin auth get token
- List all Chekin housings
- Get single Chekin housing by ID
- Create a Chekin housing
Toolboxes
Every team gets its own toolbox.
Curate which Chekin tools each team sees, scoped team by team.
- Operations
- Front desk
- Compliance
- Revenue
Shared connections
Teammates use Chekin without a credential.
See who connected each account and how many teams and members share it.
- Madrid portfolio
- Barcelona portfolio
- Compliance EU
- Front desk
Audit log
Every Chekin call is on record.
When, who, what happened, type and resource, in an append,only log.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule fires, a digest posts back.
Six steps fetch and group Chekin housings, draft a digest, then wait for approval.
Chekin digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch housings
Chekin
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Chekin
Queued
Collections and dashboards
Chekin health, counted on a schedule.
Four metrics, 14 days of records created and a team breakdown, no model involved.
Chekin health
Refreshed 4 minutes ago · every 15 minutes · from the housings collection
Housings
1,284 ↓ 12%
Rooms
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Housings created
Last 14 days
By team
Share of activity
Madrid portfolio 34%
Barcelona portfolio 27%
Compliance EU 21%
Front desk 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Chekin to Claude?
Connect Chekin in Elaichi first, then open Claude and go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Chekin connects with an API key, so the sign-in step is pasting the key from your Chekin account into Elaichi. There is no OAuth application to register and no client ID or secret to generate.
Does Chekin work with ChatGPT and Cursor as well as Claude?
Yes. Once Chekin is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Chekin once and every client you use picks it up.
What can an AI agent actually do with my Chekin data?
With Chekin connected, an agent can list and look up your housings, rooms, reservations, police accounts and stat accounts, create and update housings and rooms, add rooms in bulk, and set up or change the police and stat accounts a property reports through. It can also remove a housing and restore one that was removed. Because Chekin has a large number of actions, short concrete asks such as "list rooms for the Lisbon apartment" work better than long paragraphs.
Does connecting Chekin give the AI access to every property in my account?
Connecting Chekin gives an agent only what the person who signed in can already reach in Chekin. The Chekin API key you connect with defines the outer limit, and Elaichi can narrow that further with roles and restrictions, but it can never widen it. Nothing the AI does in Chekin goes beyond that person's own access.
Can I stop an agent from deleting or changing things in Chekin?
Yes. Restrictions in Elaichi work per action, so you can allow reading housings and reservations while blocking the actions that delete or update housings, rooms, police accounts or stat accounts. A blocked action is never advertised to Claude, ChatGPT, Cursor or any other client, so no prompt can reach it.
What happens to a Chekin connection when someone leaves?
When you offboard someone in Elaichi, their access to Chekin through every client ends at once. If they had shared a Chekin connection with a team, it keeps working for everyone else. If you want to remove Chekin entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client at the same time.
Put Chekin in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.