4,500+ servers built on MCP Fusion
Vinkius
Kisi logo
Vinkius
CrewAI logo

How to Use the Kisi MCP in CrewAI

Deploy autonomous security teams in CrewAI to monitor and control your Kisi physical access infrastructure.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

Kisi MCP on Cursor AI Code Editor MCP Client Kisi MCP on Claude Desktop App MCP Integration Kisi MCP on OpenAI Agents SDK MCP Compatible Kisi MCP on Visual Studio Code MCP Extension Client Kisi MCP on GitHub Copilot AI Agent MCP Integration Kisi MCP on Google Gemini AI MCP Integration Kisi MCP on Lovable AI Development MCP Client Kisi MCP on Mistral AI Agents MCP Compatible Kisi MCP on Amazon AWS Bedrock MCP Support
MCP Servers - Free for Subscribers
CrewAI

Connect Kisi MCP to CrewAI

Create your Vinkius account to connect Kisi to CrewAI and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Monitor Security Autonomously

A dedicated watcher agent uses `list_kisi_locks` to constantly poll your building hardware. It looks for doors propped open or offline controllers without needing human supervision. When it finds an anomaly, the agent fires `get_kisi_lock` to pull the exact hardware state. It cross-references this with `check_kisi_status` to determine if the issue is a physical breach or just a cloud API outage.

Audit Distributed Credentials

You assign an auditor agent the `list_kisi_users` and `list_kisi_groups` tools. This agent spends its time cross-checking your HR database against actual active mobile credentials. If it spots a discrepancy, it passes the target ID to an investigator agent. The investigator runs `get_kisi_user` to pull the full profile and writes a report. The MCP Server handles the data extraction while your crew handles the logic.

Respond to Emergencies

The `lockdown_kisi_lock` tool allows your responder agents to secure physical zones during hierarchical execution. A manager agent receives a threat alert and orders a responder to lock down the affected area. Once the threat clears, the manager coordinates with a local admin agent. They use `get_kisi_place` to verify the building is clear, then carefully run `unlock_kisi_lock` to restore normal operations.

Setup guide

Set up Kisi MCP in CrewAI

Prerequisites

  • Python 3.10+ installed
  • crewai package (pip install crewai)
  • Active Vinkius subscription with a valid endpoint token
  1. 1

    Install CrewAI

    Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.

  2. 2

    Add the MCP URL to your agent

    Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.

  3. 3

    Kick off your crew

    Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke Kisi tools as needed.

crew.py
from crewai import Agent, Task, Crew

agent = Agent(
    role="Kisi Analyst",
    goal="Access and analyze Kisi data via MCP.",
    backstory="Expert analyst with direct Kisi access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent Kisi transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Kisi MCP in CrewAI

Install crewai[tools]. You can pass the HTTP endpoint directly into your agent's mcps array, or use MCPServerHTTP for deeper configuration.
Yes. Use the tool_filter parameter when setting up the server connection. Give the monitoring agent read-only tools and restrict the unlock tools to your moderator agent.
CrewAI uses shared memory. If Agent A pulls a list of users, Agent B can reference those exact user IDs in its next task without hitting the API twice.
The framework supports stdio, SSE, and Streamable HTTP transports natively. You just configure the transport type in the connection object.
Your agents are ingesting raw physical movement records and personal identity profiles. You must run this crew in a secure environment because the agents store these entry logs in their short-term memory during execution.

Start using the Kisi MCP today

We host it, we monitor it, we maintain it. You just paste one token.

Built & Managed by Vinkius 30s setup 10 tools

We've already built the connector for Kisi. Just plug in your AI agents and start using Vinkius.

No hosting. No infrastructure. No complex setup.
All 10 tools are live and waiting. You're up and running in seconds.

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
+ other MCP clients

Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.

Zero hosting required Full MCP catalog included Enterprise-grade security Auto-updated by Vinkius

Built, hosted, and secured by Vinkius. You just connect and go.