How to Use the Brivo MCP in Claude Code

Q: How do I add the Brivo server to Claude Code?

Run claude mcp add in your shell, passing the Brivo server URL and transport flags. The Claude Code CLI will automatically register the ten hardware control tools.

Pipe Brivo access logs and door controls directly into your terminal workflows with Claude Code.

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 Claude Code

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Pipe Brivo event logs to terminal utilities

Run a single command in Claude Code to grab physical Brivo security logs via `list_access_events` and pipe them directly into grep or jq. You can filter for specific Brivo door alarms or unauthorized badge swipes without opening a browser using Claude Code. Because Claude Code runs entirely in your shell, you can combine Brivo's `list_users` with standard command-line tools to quickly generate text-based security reports on the fly.

Claude Code MCP Server automates door triggers

When you need to secure the building fast, use this Claude Code MCP Server to run `get_door_status` across all Brivo locations. If a Brivo entry point is left open, you can immediately trigger `unlock_door` or check permissions using `list_access_groups` directly from your Claude Code terminal. The Claude Code command-line agent handles the Brivo connection directly, letting you script quick checks without writing boilerplate API integration code.

Batch audit Brivo credentials via CLI

Let's be real, cleaning up old keys is a pain, so ask Claude Code to list your current Brivo badges with `list_credentials` and cross-reference them with `list_schedules`. The Claude Code CLI agent will print a clean table of expired or inactive Brivo credentials right in your terminal. If you need to verify a specific person's access, Claude Code queries `get_user` and prints their active Brivo permissions alongside their account metadata from `get_account_info`.

Setup guide

Set up Brivo MCP in Claude Code

Prerequisites

Claude Code CLI installed (npm install -g @anthropic-ai/claude-code)
Active Vinkius subscription with a valid endpoint token

1

Run the add command

Open your terminal and run the command shown on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com. Use --scope user to make it available across all projects.
2

Verify the connection

Start a Claude Code session and type /mcp to list connected servers. You should see brivo-mcp with a green status indicator.
3

Start using tools

Ask Claude Code something like "Check my latest Brivo transactions." It will automatically discover and invoke the available Brivo tools.

Terminal

claude mcp add --transport http brivo-mcp https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Get your connection token →

Prerequisites

Claude Code CLI installed
Active Vinkius subscription with a valid endpoint token

1

Open the config file

Create or edit .mcp.json in your project root for project-level scope, or ~/.claude.json for user-level scope.
2

Add the Brivo MCP

Paste the JSON snippet shown on the right into the mcpServers object. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Restart Claude Code

Start a new Claude Code session. Type /mcp to confirm the server is connected. The tools will be automatically available in your conversation.

.mcp.json

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

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 Claude Code

Yes, Claude Code is built for the terminal, so you can easily pipe Brivo tools like `list_access_events` into shell scripts.

Just ask Claude Code to open the door, and the terminal agent will call `unlock_door` for the specific Brivo door ID you provide. The Claude Code MCP toolset handles the API request instantly.

Run `claude mcp add` in your shell, passing the Brivo server URL and transport flags. The Claude Code CLI will automatically register the ten hardware control tools.

Yes, you can query your physical Brivo controllers by asking the Claude Code terminal agent to pull your core site details using `get_account_info`.

No, your Brivo user details and badge numbers are processed locally in your Claude Code terminal session. The connection is isolated, ensuring your physical security logs never leave your machine.

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