Bring Access Control
to LangChain
Learn how to connect Kisi to LangChain and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Kisi MCP Server?
Connect your Kisi account to any AI agent and take full control of your facility's physical security and high-fidelity access orchestration through natural conversation.
What you can do
- Lock Portfolio Orchestration — List all cloud-connected locks, retrieve detailed high-fidelity status metadata, and monitor door health programmatically
- Remote Unlock Operations — Programmatically trigger high-fidelity remote unlocks for specific doors directly through your agent for perfectly coordinated visitor access
- Facility Lockdown Architecture — Access high-fidelity emergency lockdown protocols for individual doors or entire places to ensure immediate site security
- Place & Site Discovery — Access your complete directory of high-fidelity physical locations and places to understand and orchestrate your facility infrastructure
- User & Member Monitoring — List organization users and access complete high-fidelity profile metadata to maintain perfect security alignment
- Operational Monitoring — Verify account-level API connectivity and monitor access orchestration volume directly through your agent for perfectly coordinated security scaling
How it works
1. Subscribe to this server
2. Retrieve your API Key from your Kisi dashboard (Settings > API Keys)
3. Start managing your facility security from Claude, Cursor, or any MCP client
No more manual checking of individual door logs or physical keycards. Your AI acts as your dedicated security coordinator and facility architect.
Who is this for?
- Security Managers — instantly retrieve lock statuses and monitor site health using natural language commands without leaving your creative workspace
- Facility Managers — trigger high-fidelity remote unlocks and monitor door activity to ensure healthy and secure operations
- IT Admins — verify technical API logs and user assignments to optimize access control through simple AI queries
Built-in capabilities (10)
Check API Status
Get lock details
Get place details
Get user details
List access groups
List cloud locks
List physical places
List organization users
Lockdown a door
Unlock a door
Why LangChain?
LangChain's ecosystem of 500+ components combines seamlessly with Kisi through native MCP adapters. Connect 10 tools via Vinkius and use ReAct agents, Plan-and-Execute strategies, or custom agent architectures. with LangSmith tracing giving full visibility into every tool call, latency, and token cost.
- —
The largest ecosystem of integrations, chains, and agents. combine Kisi MCP tools with 500+ LangChain components
- —
Agent architecture supports ReAct, Plan-and-Execute, and custom strategies with full MCP tool access at every step
- —
LangSmith tracing gives you complete visibility into tool calls, latencies, and token usage for production debugging
- —
Memory and conversation persistence let agents maintain context across Kisi queries for multi-turn workflows
Kisi in LangChain
Kisi and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Kisi to LangChain through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Kisi in LangChain
The Kisi MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 10 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in LangChain only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Kisi for LangChain
Every tool call from LangChain to the Kisi MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my Kisi API Key?
Log in to your account, navigate to Settings > API Keys, and generate a new high-fidelity API Secret.
Can I unlock a door via AI?
Yes! The unlock_kisi_lock tool allows your agent to trigger a high-fidelity remote unlock for any cloud-connected door in your organization.
How do I list my organization's places?
Use the list_kisi_places tool to retrieve the complete high-fidelity directory of physical locations along with their unique identifiers for precise orchestration.
How does LangChain connect to MCP servers?
Use langchain-mcp-adapters to create an MCP client. LangChain discovers all tools and wraps them as native LangChain tools compatible with any agent type.
Which LangChain agent types work with MCP?
All agent types including ReAct, OpenAI Functions, and custom agents work with MCP tools. The tools appear as standard LangChain tools after the adapter wraps them.
Can I trace MCP tool calls in LangSmith?
Yes. All MCP tool invocations appear as traced steps in LangSmith, showing input parameters, response payloads, latency, and token usage.
MultiServerMCPClient not found
Install: pip install langchain-mcp-adapters