Kisi MCP connector
The Kisi connector brings your Kisi cards, card assignments, cameras and calendar summaries to Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, so each person can look up and manage building access inside their own permissions.
- Connects with an API key
- Free 14-day trial
- No credit card
Which Kisi cards are still active for contractors who left in March?
Working in Kisi with Elaichi
-
List all Kisi calendar summaries
-
List all Kisi cameras
-
Get single Kisi camera by ID
How to connect Kisi to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Kisi 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.
Kisi 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.
Kisi 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.
Kisi 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.
Kisi 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 Kisi 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 Kisi through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Kisi is logged.
-
Security
Check which cards are active right now
Ask for every active Kisi card and who it is assigned to, then spot the contractor badge that should have been switched off weeks ago.
-
Facilities
Issue a card to a new contractor
Create the Kisi card, assign it to the contractor and activate it in one conversation, without opening the Kisi dashboard between calls.
-
IT
Deactivate a lost card before lunch
When someone reports a badge missing, deactivate that Kisi card on the spot and confirm the assignment is off before the person reaches the door.
-
HR
Pull a card back when someone leaves
On a last day, deassign the person's Kisi card and deactivate it as part of the offboarding checklist, with the change named in the log.
-
Operations
Grab the camera link for an incident
Find the right Kisi camera by name and fetch its video link while the report is still being written, instead of hunting through a camera list.
-
Workplace
Review calendar summaries before a site visit
Read the Kisi calendar summaries for a location to see what access is scheduled, then update a camera's details if the room layout has changed.
Try asking
- “Which Kisi cards are still active for contractors who left in March?”
- “Deactivate the card assigned to Priya Nair and confirm it is off.”
- “Give me the video link for the lobby camera from this morning.”
What connecting Kisi gets you
6 screens from Elaichi, each doing one job for your Kisi account.
Ask Elaichi to work across your apps.
Which Kisi cards are still active for contractors who left in March?
Deactivate the card assigned to Priya Nair and confirm it is off.
Give me the video link for the lobby camera from this morning.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask who holds which card, in plain words.
Live answers from Kisi cards, assignments and cameras, no dashboard digging.
Copy the endpoint
AI apps
One Kisi endpoint for Claude, ChatGPT, Cursor and Microsoft Copilot.
Connect Kisi once and every MCP client works through one governed endpoint, no shared API key.
Tool catalog
229 Kisi tools, no code to write.
Cards, card assignments, cameras and calendar summaries, covered without a line of custom code.
Toolboxes
Every team gets its own Kisi toolbox.
Security, Facilities and IT each work from a toolbox scoped to their job.
Shared connections
Share Kisi access without sharing the API key.
One person connects Kisi, teammates work through it and never see a credential.
Audit log
Every card change in Kisi is on record.
When, who, what happened and which card or camera, in one 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. Workflows, collections and live dashboards come with the Black plan.
Kisi digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch cards
Kisi
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
Kisi
Queued
Workflows
A schedule issues the weekly access digest.
New Kisi card assignments are fetched, grouped, drafted into a digest, approved, then posted back.
Kisi health
Refreshed 4 minutes ago · every 15 minutes · from the cards collection
Cards
1,284 ↓ 12%
Card assignments
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Cards created
Last 14 days
By team
Share of activity
HQ Security 34%
Facilities 27%
IT Helpdesk 21%
People Ops 18%
Collections and dashboards
Kisi access health, computed without a model.
Four metrics, 14 days of cards created and a breakdown by team, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Kisi
All three can connect Kisi 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 Kisi tools | Allow or restrict single Kisi 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 Kisi 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.
Kisi tools for your AI agents
229 tools are ready to call through Elaichi's MCP endpoint the moment you connect Kisi, 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 Kisi to Claude?
In Elaichi, pick Kisi from the catalog and paste in your Kisi API key, which you copy from your Kisi account. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. There is no OAuth application to register and no client ID or secret to generate for Kisi.
Does Kisi work with ChatGPT and Cursor as well as Claude?
Yes. Once Kisi 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 Kisi once and every client picks it up.
What can an AI agent actually do with my Kisi data?
An agent can list your Kisi cards and card assignments, see who holds which card, create or update an assignment, and activate or deactivate a card. It can also list Kisi cameras, create or update one, fetch a camera's video link, and read calendar summaries. Short, concrete asks such as deactivate card 4471 work better than long paragraphs.
Does connecting Kisi give the AI every card, camera and door?
No. The connection carries the Kisi access of the person who connected it, so the agent sees the cards, cameras and calendar summaries that Kisi account is allowed to see, and nothing beyond that. Elaichi can narrow that access further for any team, and it can never widen it.
Can I stop an agent from deleting or changing things in Kisi?
Yes. Restrictions in Elaichi work per action, so you can allow reading Kisi cards and cameras while restricting delete, deactivate or update. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.
What happens to a Kisi connection when someone leaves?
Offboarding a person in Elaichi ends their access to Kisi through every client at once. If they connected Kisi and shared it with a team, the shared connection keeps working for everyone else. Disconnecting Kisi once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client together.
Does the Kisi MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Kisi 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 Kisi?
Yes. Both let Claude, ChatGPT or Cursor use Kisi. 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 Kisi call.
How is Elaichi different from Composio for Kisi?
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 Kisi: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Kisi 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