Bring Access Control
to CrewAI
Learn how to connect Kisi to CrewAI 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 CrewAI?
When paired with CrewAI, Kisi becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Kisi tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
- —
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the
mcpsparameter and agents auto-discover every available tool at runtime - —
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
- —
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
Kisi in CrewAI
Kisi and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Kisi to CrewAI 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 CrewAI
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 CrewAI 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 CrewAI
Every tool call from CrewAI 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 CrewAI discover and connect to MCP tools?
CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
Can different agents in the same crew use different MCP servers?
Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
What happens when an MCP tool call fails during a crew run?
CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
Can CrewAI agents call multiple MCP tools in parallel?
CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
Can I run CrewAI crews on a schedule (cron)?
Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
Rate limiting or 429 errors
Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.