Bring Access Control
to Claude Desktop
Learn how to connect Kisi to Claude Desktop 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 Claude Desktop?
Claude Desktop is the definitive way to connect Kisi to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 10 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
Kisi in Claude Desktop
Kisi and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Kisi to Claude Desktop 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 Claude Desktop
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 Claude Desktop 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 Claude Desktop
Every tool call from Claude Desktop 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 Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.