Bring Access Control
to VS Code Copilot
Learn how to connect Kisi to VS Code Copilot 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 VS Code Copilot?
GitHub Copilot Agent mode brings Kisi data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
Kisi in VS Code Copilot
Kisi and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Kisi to VS Code Copilot 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 VS Code Copilot
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 VS Code Copilot 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 VS Code Copilot
Every tool call from VS Code Copilot 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.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.