How to Use the Brivo MCP in Mastra AI

Build resilient, self-healing physical security workflows with Mastra AI and the Brivo MCP Server.

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 Mastra AI

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Build self-healing security loops with Mastra AI

The `get_door_status` tool lets your Mastra AI agent monitor Brivo physical entry points and trigger conditional recovery workflows. If the initial Brivo check fails, Mastra's workflow engine retries the call to fetch the status with exponential backoff.

Automate user onboarding with human-in-the-loop approvals

To automate your onboarding, the `list_access_groups` tool provides the necessary Brivo security tier data to automate Mastra AI user provisioning workflows. Before executing the final Brivo assignment, Mastra's tool approval feature pauses the workflow to get manual admin verification.

Run scheduled security audits across your facilities

By using the `list_schedules` tool, your Mastra AI agent can pull Brivo facility hours and compare them against actual access patterns. The workflow flags Brivo anomalies by cross-referencing Mastra schedule data with `list_credentials` to spot unauthorized after-hours attempts.

Setup guide

Set up Brivo MCP in Mastra AI

Prerequisites

Node.js 18+ and a TypeScript project
@mastra/mcp + @mastra/core packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run npm install @mastra/mcp @mastra/core plus your preferred model provider (e.g. @ai-sdk/openai).
2

Configure the MCPClient
Create an MCPClient with your Vinkius endpoint as a URL object. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com.
3

Discover and inject tools
Call mcpClient.listTools() and spread the result into your agent's tools object. All Brivo tools become native Mastra tools.
4

Run with any model
Swap openai("gpt-4o") for any AI SDK-compatible provider. Call agent.generate() and the agent routes tool calls through MCP automatically.

agent.ts

import { MCPClient } from "@mastra/mcp";
import { Agent } from "@mastra/core/agent";
import { openai } from "@ai-sdk/openai";

const mcpClient = new MCPClient({
  id: "brivo-mcp-client",
  servers: {
    "brivo-mcp": {
      url: new URL(
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
      ),
    },
  },
});

const agent = new Agent({
  name: "Brivo Agent",
  model: openai("gpt-4o"),
  instructions: "You have access to Brivo tools.",
  tools: {
    ...(await mcpClient.listTools()),
  },
});

const result = await agent.generate(
  "List recent Brivo transactions"
);
console.log(result.text);

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 Mastra AI

The framework uses built-in exponential backoff to retry failed calls to `get_door_status` or `list_doors`. If the physical controller is offline, your workflow won't crash; it will wait and try again.

Yes, you can configure the agent to require manual approval for high-risk tools like `unlock_door`. The workflow pauses and waits for a human signature before sending the release command to the panel.

Instantiate the MCP client using your Vinkius endpoint URL and pass the registered tools directly into your agent configuration. Mastra automatically maps tools like `list_users` so your workflows can call them immediately.

Absolutely. You can chain actions together, like pulling a list of inactive profiles with `list_users` and then checking their last scan times using `list_access_events` to clean up old permissions.

Your Brivo API credentials reside inside the secure Vinkius vault, not in your Mastra deployment environment. Every time your agent calls `list_credentials`, the request goes through an encrypted, ephemeral sandbox that handles the authentication handshake safely.

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