How to Use the Brivo MCP in CrewAI

Q: How is sensitive Brivo door status data protected during agent collaboration?

All telemetry and door status logs retrieved via getdoorstatus are processed in memory within your private execution environment. The Vinkius MCP sandbox ensures that no raw access logs or physical security configurations are cached or stored on external servers.

Deploy a team of autonomous agents using CrewAI to monitor, audit, and secure your Brivo facilities.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Brivo MCP to CrewAI

Create your Vinkius account to connect Brivo 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

Setup Brivo with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Coordinate autonomous security agents with CrewAI

The `get_door_status` tool gives your autonomous CrewAI monitoring team real-time telemetry on Brivo physical entry points. When a Brivo anomaly is spotted, the monitoring agent hands the task over to a CrewAI supervisor agent.

Run deep credential audits with specialized agent teams

To clean up your physical access control lists, the `list_users` tool fetches the master Brivo roster so your CrewAI auditing team can cross-reference active credentials. These CrewAI agents work in parallel, sharing context to identify orphan Brivo credentials that no longer match active employees.

Deploy an autonomous response team for your physical doors

The `get_account_info` tool retrieves physical site details to help your CrewAI incident response team locate active Brivo alarms. While that happens, a CrewAI coordination agent pulls up the local Brivo schedules via `list_schedules` to see if the building should be empty.

Setup guide

Set up Brivo MCP in CrewAI

Prerequisites

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

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
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

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

crew.py

from crewai import Agent, Task, Crew

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

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

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

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="Brivo Analyst",
        goal="Access and analyze Brivo data via MCP.",
        backstory="Expert analyst with direct Brivo access.",
        tools=mcp_tools,
    )

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

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

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Brivo. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

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

Connect Brivo now

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 Brivo MCP in CrewAI

The crew utilizes a shared memory system. When one agent pulls logs using `list_access_events`, the other agents in the crew can instantly access that data to verify user details with `get_user`.

Yes, you can use a tool filter to restrict access. For example, you can give your monitoring agent access to `get_door_status` while keeping `unlock_door` restricted to your supervisor agent.

The Vinkius MCP infrastructure queues the incoming tool calls from your crew. Whether three agents call `list_doors` at once or space them out, the server processes them reliably without rate-limiting your agents.

It connects via standard HTTP or SSE transports. You just pass your secure Vinkius URL into the agent's configuration, and the framework automatically discovers all available tools like `list_access_groups`.

All telemetry and door status logs retrieved via `get_door_status` are processed in memory within your private execution environment. The Vinkius MCP sandbox ensures that no raw access logs or physical security configurations are cached or stored on external servers.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript