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 VS Code Copilot 10 tools — connect in under 2 minutes

Name: Brivo
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 10 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

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.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Brivo and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "brivo": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

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.

GitHub Copilot Agent mode brings Brivo data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 tools — Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

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 VS Code Copilot 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 VS Code Copilot via MCP

Follow these steps to integrate the Brivo MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using Brivo

Ask Copilot: "Using Brivo, help me..." — 10 tools available

Why Use VS Code Copilot with the Brivo MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Brivo through the Model Context Protocol.

VS Code is used by over 70% of developers — adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Brivo + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Brivo MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Brivo MCP Tools for VS Code Copilot (10)

These 10 tools become available when you connect Brivo to VS Code Copilot 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 VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot 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 VS Code Copilot

Common issues when connecting Brivo to VS Code Copilot through the Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Brivo + VS Code Copilot FAQ

Common questions about integrating Brivo MCP Server with VS Code Copilot.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.