Default
Chekin MCP connector
The Chekin connector brings your housings, rooms, reservations, police accounts and stat accounts into Claude, ChatGPT, Cursor, Microsoft Copilot and any MCP client, so your team can ask about properties and guest registration setup in plain language and update them as themselves.
- Connects with an API key
- Free 14-day trial
- No credit card
List every Chekin housing added this month
Working in Chekin with Elaichi
-
Chekin auth get token
-
List all Chekin housings
-
Get single Chekin housing by ID
How to connect Chekin to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Chekin MCP connector for 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.
Chekin MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Chekin MCP connector for 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. The plugin directory lives at chatgpt.com/plugins.
Chekin MCP connector for 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.
Chekin MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
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.
What teams do with Chekin through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Chekin is logged.
-
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”
What connecting Chekin gets you
6 screens from Elaichi, each doing one job for your Chekin account.
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, Cursor or Microsoft Copilot
The agent
Ask about housings, get real answers.
Type a question in plain language and read it straight from live Chekin records.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach Chekin.
One governed MCP endpoint over OAuth, no SDK and no shared API key.
Tool catalog
64 Chekin tools ready to call.
Housings, rooms, reservations and police accounts covered, with no custom code to write.
Toolboxes
Every team gets its own toolbox.
Curate which Chekin tools each team sees, scoped team by team.
Shared connections
Teammates use Chekin without a credential.
See who connected each account and how many teams and members share it.
Audit log
Every Chekin call is on record.
When, who, what happened, type and resource, in an append,only log.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
Chekin digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
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 Jake Morgan
Approve Deny -
Post the digest
Chekin
Queued
Automations
A schedule fires, a digest posts back.
Six steps fetch and group Chekin housings, draft a digest, then wait for approval.
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%
Collections and dashboards
Chekin health, counted on a schedule.
Four metrics, 14 days of records created and a team breakdown, no model involved.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Chekin
All three can connect Chekin to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Chekin tools | Allow or restrict single Chekin tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Chekin call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
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.
Questions, answered
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, Microsoft Copilot, 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 restricting the actions that delete or update housings, rooms, police accounts or stat accounts. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor, Microsoft Copilot or any other client cannot run it, whatever the prompt says.
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, Microsoft Copilot and every other client at the same time.
Does the Chekin MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Chekin is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Chekin?
Yes. Both let Claude, ChatGPT or Cursor use Chekin. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Chekin call.
How is Elaichi different from Composio for Chekin?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Chekin: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Chekin in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot