Can I unlock a door remotely using the agent?

Yes! Use the `unlock_door` tool with the Access Point ID. Your agent will trigger a momentary unlock command in Brivo, allowing entry instantly.

How do I check if a door is currently open or closed?

Simply ask the agent to `get_door_status` and provide the Access Point ID. It will retrieve the live state of the door from the Brivo cloud.

Does the integration allow adding a new user to the building?

The current toolset focuses on control and monitoring (Read-Only/Unlock) for operational efficiency. Provisioning new users or changing core permissions should be managed via the Brivo administrator portal.

Brivo MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: Brivo
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to Brivo through Vinkius, pass the Edge URL in the `mcps` parameter and every Brivo tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Brivo Specialist",
    goal="Help users interact with Brivo effectively",
    backstory=(
        "You are an expert at leveraging Brivo tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Brivo "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 available tools "
        "and what they can do."
    ),
)

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

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

About Brivo MCP Server

Connect your Brivo Access account to any AI agent and orchestrate your physical security, facility management, and user provisioning workflows through natural conversation.

When paired with CrewAI, Brivo becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Brivo tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

Door Control & Status — List all access points, check their live status (open/closed/locked), and trigger momentary unlocks directly from your workspace.
User Provisioning — List and retrieve detailed profiles for all users and manage their access groups and credentials.
Event Monitoring — Retrieve real-time or historical access events and security alarms to ensure facility safety.
Credential Oversight — List and audit physical and digital credentials (cards, mobile passes) assigned to users.
Schedule Coordination — Access time schedules used for automated locking and unlocking of your facility.

The Brivo MCP Server exposes 10 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Brivo to CrewAI via MCP

Follow these steps to integrate the Brivo MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 10 tools from Brivo

Why Use CrewAI with the Brivo MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Brivo through the Model Context Protocol.

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 `mcps` parameter 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

Brivo + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Brivo MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Brivo for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Brivo, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Brivo tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Brivo against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Brivo MCP Tools for CrewAI (10)

These 10 tools become available when you connect Brivo to CrewAI via MCP:

get_account_info

Retrieve core account/site information

get_door_status

Get live status of a door

get_user

Get details of a specific user

list_access_events

List recent access events and alarms

list_access_groups

List all access groups

list_credentials

List all access credentials (cards, pass, etc)

list_doors

List all access points (doors)

list_schedules

List time schedules for access

list_users

List all people/users in the system

unlock_door

Momentarily unlock a door

Example Prompts for Brivo in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Brivo immediately.

"List all the doors in my office."

"Unlock the 'Main Entrance' door (ID 101)."

"Show the recent access events for the Server Room."

Troubleshooting Brivo MCP Server with CrewAI

Common issues when connecting Brivo to CrewAI through the Vinkius, and how to resolve them.

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.

Brivo + CrewAI FAQ

Common questions about integrating Brivo MCP Server with CrewAI.

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.