Give AI agents (Claude, Copilot, Cursor…) scoped access to your Brivio data via the Model Context Protocol.
Point any Streamable-HTTP MCP client at https://mcp.brivio.ro/mcp with your API key as a Bearer token:
{
"mcpServers": {
"brivio": {
"url": "https://mcp.brivio.ro/mcp",
"headers": { "Authorization": "Bearer brivio_sk_live_..." }
}
}
}60 tools covering contacts, invoices (create, record payments, e-Factura status/submission), expenses, banking (read-only), subscriptions, fixed assets, VAT rates, document series, projects, quotes, inventory, HR, company registry search, DNS and domains. The tool list is filtered by your key's scopes — an agent with a read-only key never even sees write tools, and the API enforces scopes on every call regardless.
Irreversible operations (e-Factura submission, deletions) are annotated as destructive so MCP clients ask for confirmation. Use a brivio_sk_test_… key to let agents work against your isolated sandbox organization instead of production data.
BRIVIO_API_KEY=brivio_sk_test_... npx @brivio/mcp