Skip to content

Kisi MCP connector

The Kisi connector brings your Kisi cards, card assignments, cameras and calendar summaries to Claude, ChatGPT, Cursor and the Elaichi Agent, so each person can look up and manage building access inside their own permissions.

  • 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 Kisi to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Kisi once

  1. Open Connections, choose Add connection, and pick Kisi.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Paste a Kisi API key. One person generates a token in Kisi 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.

kisi
Kisi
Censys
Herd Security
Infisical
Intruder
Orca Security
2

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.

Kisi MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 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 ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Kisi MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 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 Kisi to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 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 Kisi through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • 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.”

See all 229 Kisi tools below

Compare

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.

Elaichi compared with Zapier MCP and Composio for Kisi, by what to check
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 $15 per user per month. 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.

AI tools

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.

See it in Elaichi

What connecting Kisi gets you

6 screens from the product, each doing one job for your Kisi account.

The agent

Ask who holds which card, in plain words.

Live answers from Kisi cards, assignments and cameras, no dashboard digging.

  • cards
  • card assignments
  • cameras
  • calendar summaries

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 or Cursor

MCP clients

One Kisi endpoint for Claude, ChatGPT and Cursor.

Connect Kisi once and every MCP client works through one governed endpoint, no shared API key.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

Tool catalog

229 Kisi tools, no code to write.

Cards, card assignments, cameras and calendar summaries, covered without a line of custom code.

  • List all Kisi calendar summaries
  • List all Kisi cameras
  • Create a Kisi camera
  • Get single Kisi camera by ID
ElaichiTools
Tool Action Description
List all Kisi calendar summaries List Get a summary of a Kisi scheduleable's calendar events for a time window. Returns: events, exceptions, schedules_by_day. Duration-only around values are not supported. Required: around, consequence.
List all Kisi cameras List List Kisi cameras. Returns camera objects including id, name, description, status, enabled, place_id, lock_id, and snapshot/clip settings. Supports filtering and name-based sorting.
Create a Kisi camera Create Create a Kisi camera. Returns the created camera object including id, resource_type, name, description, enabled, status, created_at, place_id, and lock_id. Required: camera.
Get single Kisi camera by ID Get Get a Kisi camera by id. Returns the full camera object including id, name, description, status, enabled, place_id, and lock_id, plus integration details for Rhombus Systems cameras. Required: id.
Update a Kisi camera by ID Update Update a Kisi camera by id, changing attributes such as name, description, enabled state, lock assignment, or snapshot and clip settings. Returns an empty 204 response on success. Required: id, camera.

Toolboxes

Every team gets its own Kisi toolbox.

Security, Facilities and IT each work from a toolbox scoped to their job.

  • Security
  • Facilities
  • IT
  • HR
ElaichiToolboxes
Name Source template Tools Created

Security toolbox

Kisi · cards and camera footage

Kisi starter 18 Mar 4, 2026

Facilities toolbox

Kisi · card assignments and cameras

— 9 Mar 2, 2026

IT toolbox

Kisi · card activation and deactivation

— 24 Feb 27, 2026

HR toolbox

Kisi · onboarding and offboarding cards

Kisi starter 6 Feb 19, 2026

Operations toolbox

Kisi · calendar summaries and site access

— 31 Jan 30, 2026

Reception toolbox

Kisi · visitor and contractor cards

— 12 Jan 22, 2026

Shared connections

Share Kisi access without sharing the API key.

One person connects Kisi, teammates work through it and never see a credential.

  • HQ Security
  • Facilities
  • IT Helpdesk
  • People Ops
ElaichiConnections
Connection Scope Status Access
KI

Kisi (HQ Security)

Connected by Emily Carter

Personal • Active 1 team · 6 members
KI

Kisi (Facilities)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
KI

Kisi (IT Helpdesk)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
KI

Kisi (People Ops)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
KI

Kisi (Reception)

Connected by Ryan Hayes

Personal • Active Not shared
KI

Kisi (Warehouse)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Audit log

Every card change in Kisi is on record.

When, who, what happened and which card or camera, in one append-only log.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

[email protected]

Kisi Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

Kisi Cards Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

Kisi Cards List Toolbox

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 issues the weekly access digest.

New Kisi card assignments are fetched, grouped, drafted into a digest, approved, then posted back.

Kisi digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch cards

    Kisi

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. Post the digest

    Kisi

    Queued

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.

Kisi health

Refreshed 4 minutes ago · every 15 minutes · from the cards collection

Live

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%

FAQ

Frequently asked questions

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, 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 my team share one Kisi connection?

Yes. One person connects Kisi with the API key and shares the connection with a team, and nobody else ever handles the key. Each teammate still signs in to Elaichi as themselves, so every card activation or camera change in Kisi is logged under their own name.

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 blocking delete, deactivate or update. A restricted action is never advertised to Claude, ChatGPT or Cursor at all, so no prompt can reach it.

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 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, 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 on Gold, no credit card. Connect it once and pick what each team can call.

Works with
Claude ChatGPT Cursor and any other MCP client, or the Elaichi Agent.
When the trial ends
Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.