4,500+ servers built on MCP Fusion
Vinkius

Brivo MCP. Control doors and audit physical access events.

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

Brivo MCP on Cursor AI Code Editor MCP Client Brivo MCP on Claude Desktop App MCP Integration Brivo MCP on OpenAI Agents SDK MCP Compatible Brivo MCP on Visual Studio Code MCP Extension Client Brivo MCP on GitHub Copilot AI Agent MCP Integration Brivo MCP on Google Gemini AI MCP Integration Brivo MCP on Lovable AI Development MCP Client Brivo MCP on Mistral AI Agents MCP Compatible Brivo MCP on Amazon AWS Bedrock MCP Support

Just plug in your AI agents and start using Vinkius.

Brivo MCP Server manages physical access and facility security. Your AI agent uses this server to list doors, check live door status, retrieve user profiles, and monitor access events.

You can orchestrate facility operations—like unlocking a server room door or auditing credentials—all from a natural language prompt.

What your AI agents can do

Get account info

Retrieves core account and site details for the Brivo installation.

Get door status

Gets the live, current status (open, closed, locked) of a specific door.

Get user

Retrieves detailed information for a single specified user profile.

+ 7 more capabilities included
Get live door status

The agent checks and reports the current status (open, closed, locked) of any specified access point.

List all facility doors

The agent retrieves a list of every access point and its identifying information.

Unlock a door remotely

The agent executes a momentary unlock command on a specified door, granting temporary physical access.

Retrieve user details

The agent pulls a specific user's profile data, including roles and contact information.

Audit access events

The agent fetches a log of recent or historical access attempts and triggered security alarms.

Manage credentials and groups

The agent lists all assigned physical and digital credentials, or manages the user's access groups.

Supported MCP Clients

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

Waiting for input…

AI Agent

get019d7563

get account info

Retrieves core account and site details for the Brivo installation.

get019d7563

get door status

Gets the live, current status (open, closed, locked) of a specific door.

get019d7563

get user

Retrieves detailed information for a single specified user profile.

list019d7563

list access events

Lists recent or historical access events and security alarms for auditing.

list019d7563

list access groups

Lists all defined access groups used to manage user permissions.

list019d7563

list credentials

Lists all physical and digital credentials (cards, mobile passes) assigned to users.

list019d7563

list doors

Lists every physical access point (door) connected to the system.

list019d7563

list schedules

Lists the time schedules that govern automated door locking and unlocking.

list019d7563

list users

Lists every user account in the Brivo system.

unlock019d7563

unlock door

Momentarily unlocks a specified door, allowing temporary physical passage.

Choose How to Get Started

Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.

Build Your Own

Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.

  • Import from OpenAPI, Swagger, or YAML specs
  • Create Agent Skills with progressive disclosure
  • Deploy to edge with MCPFusion framework
  • Built in DLP, auth, and compliance on every call
  • Real time usage dashboard and cost metering
  • Publish to catalog or keep private
Start building

Make Your AI Do More

Start with Brivo, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.

  • Use this MCP plus 4,700+ others, all in one place
  • Add new capabilities to your AI anytime you want
  • Every connection is secured and compliant automatically
  • Track usage and costs across all your servers
  • Works with Claude, ChatGPT, Cursor, and more
  • New servers added to the catalog every week

What you can do with this MCP connector

Your AI agent controls your facility's physical access and security system with this server. You can list every door, check its live status, and even unlock it remotely. You'll also pull detailed user profiles, audit access events, and manage all the credentials and groups assigned to staff. You can check core account and site details with get_account_info, list every user with list_users, get a specific person's profile with get_user, list all doors with list_doors, check a door's current status with get_door_status, and temporarily unlock a door using unlock_door.

You can audit security by getting a log of recent access events and alarms using list_access_events. You'll manage user permissions by listing all access groups with list_access_groups and listing all credentials assigned to users with list_credentials. The system also lets you see all time schedules that run automated door locks and unlocks with list_schedules.

How Brivo MCP Works

  1. 1 Subscribe to the Brivo server and provide your Brivo API credentials (Key, Username, Password).
  2. 2 Your AI agent executes a command, such as 'Show the status of the main entrance door.'
  3. 3 The server runs the get_door_status tool and returns the real-time status to your agent.

The bottom line is, your AI agent runs security commands against Brivo and brings the results back to your current workspace.

Who Is Brivo MCP For?

Security Operations Center (SOC) staff and Facility Managers use this when they need to react quickly to physical incidents. IT Admins use it when they need to provision or audit user access in a workflow. It's for anyone who can't afford to spend time switching between a dashboard and a text editor.

Facility Manager

Checks the status of all doors, unlocks emergency exits, and monitors access events during an incident.

IT Administrator

Retrieves user access profiles, audits credentials, and manages user access groups for onboarding/offboarding.

Security Analyst

Runs list_access_events to check historical logs and audit physical access attempts after an alarm.

What Changes When You Connect

  • Check the live status of any door instantly. Use get_door_status to see if the server room door is currently locked or open, eliminating manual dashboard checks.
  • Audit user access and credentials quickly. Running list_credentials lets you see every card or mobile pass assigned to a user without deep diving into the portal.
  • Manage the entire facility roster. list_users gives you a full directory of people, and get_user pulls their specific profile details in one call.
  • Track incidents without delay. Use list_access_events to pull a chronological log of who entered and when, or to check for active alarms.
  • Control physical entry points. unlock_door allows your agent to temporarily unlock a specific door when a visitor needs access, all from your chat window.
  • Know the rules of the facility. list_schedules shows the automated time rules—when doors are supposed to lock—helping you troubleshoot access failures.

Real-World Use Cases

01

Handling a Guest Entry

A visitor arrives and needs access to the main office. Instead of calling facilities, the agent runs list_doors to find the main entrance ID, then uses unlock_door to temporarily open it. The problem is solved in three prompts.

02

Auditing Employee Access Changes

An employee is leaving. The agent runs get_user to pull their current profile, then list_credentials to confirm all access cards are deactivated and their access groups are removed before offboarding.

03

Investigating a Security Alarm

The security analyst receives an alarm notification. They immediately run list_access_events to see the last 10 entries around the alarm time, pinpointing the exact user and time of the incident.

04

Pre-Shift Facility Check

The facility manager starts the day by running list_doors and get_door_status for all critical points. This confirms every door is in its expected locked state before operations begin.

The Tradeoffs

Treating the server like a simple data query.

Just asking the agent, 'What are the doors and users?' This gives a list, but doesn't help you act on the data or know if anything is wrong.

Run a sequence. First, use list_doors to get the IDs. Then, use get_door_status with the IDs. Finally, use list_access_events to check the logs for that time frame. This gives a complete picture.

Forgetting to check schedules.

Assuming a door is locked at 10 PM because it should be. You don't know if the scheduled time changed or if a manual override is needed.

Always check list_schedules first. This confirms the automated locking policy before you trust the door's current status or make a manual change using unlock_door.

Relying on a single user profile.

Getting only the basic user info with get_user and thinking you know their full access rights. You might miss their access groups or credentials.

Combine calls. Use get_user to get the person, then run list_access_groups and list_credentials to audit their full scope of access.

When It Fits, When It Doesn't

Use this server if your job involves physical security, facility management, or IT access auditing. You need to know what the physical status is (e.g., is the door locked?) and who was there (e.g., who accessed the server room?). If you only need a simple database lookup (like finding a contact email), use a standard CRM API. But if the action involves physical world state—like unlocking a door or checking a real-time alarm—you need Brivo. Don't try to model a 'risk score' using this; it only reports current status and history. For predictive threat modeling, you need a specialized graph database tool.

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.

VINKIUS INFRASTRUCTURE

Cloud Hosted

Managed infra

V8 Isolated

Sandboxed per request

Zero-Trust Proxy

No stored credentials

DLP Enforced

Policy on every call

GDPR Compliant

EU data residency

Token Compression

~60% cost reduction

How we secure it →

Works with Claude, ChatGPT, Cursor, and more

The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.

This server provides 10 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.

Available Capabilities

get_account_info get_door_status get_user list_access_events list_access_groups list_credentials list_doors list_schedules list_users unlock_door

Checking facility access requires switching between five different dashboards.

Today, checking the status of a critical door means logging into the Brivo portal, navigating to the 'Doors' tab, finding the correct door ID, checking the status, and then maybe opening a second tab to check the 'Access Events' log. If you need to check a user's credentials, you log in again, go to 'Users,' and manually cross-reference the data.

With Brivo MCP Server, you just ask your agent. Ask it to 'Check the status of the server room and list the last 5 entries.' It runs the necessary tools (`get_door_status`, `list_access_events`) and gives you one clean answer in your workspace. No logins, no tabs.

Brivo MCP Server: Control physical access and audit events.

You no longer have to manually trigger an unlock sequence, find the correct door ID, and then manually log the temporary access in a ticketing system. You simply ask the agent to 'Unlock the main entrance for the maintenance team.' The server handles the API call and reports success immediately.

This isn't just about convenience. It's about making physical security actions—like temporary door unlocks or user provisioning checks—a native part of your daily workflow. It's direct, immediate, and verifiable.

Common Questions About Brivo MCP

How do I check the status of a door using the `get_door_status` tool? +

You need to specify the door ID or name. The agent runs get_door_status and reports if the door is open, closed, or locked. It's the fastest way to verify physical state.

What is the difference between `list_access_events` and `get_user`? +

These track different things. list_access_events shows what happened (who entered, when, and if there were alarms). get_user gives you who the person is (their name, details, and profile data).

Can I unlock a door using the `unlock_door` tool? +

Yes, the unlock_door tool performs a momentary unlock on a specified door. Remember, it only unlocks for a configured time period.

Do I need to run `list_users` before running `get_user`? +

No. While list_users gives you a full roster, you can directly use get_user if you already know the specific user's ID or name.

How do I use `list_credentials` to find all active access cards? +

It lists every physical and digital credential assigned to users. This helps you audit which cards or mobile passes are currently in use across the facility.

When should I use `list_schedules` compared to checking door status? +

Use list_schedules to see the programmed times for automated door locking. get_door_status tells you the door's current, live state right now.

If I get an error with `get_user`, what information should I check? +

Check the user's ID or name for typos. The error usually means the user profile doesn't exist or you lack the necessary permissions to view it.

How do I list all possible doors with `list_doors`? +

This tool returns a list of every access point ID and name on the site. You need this list to target specific doors for status checks or unlocks.

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.

More in this category

You might also like

Built & Managed by Vinkius 30s setup 10 tools

We've already built the connector for Brivo. 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.