MCP server
Give AI agents (Claude, Copilot, Cursor…) scoped access to your Brivio data via the Model Context Protocol.
Hosted server (recommended)
In Claude (Settings → Connectors → Add custom connector) or ChatGPT (developer mode → Create app), enter https://mcp.brivio.ro/mcp and sign in with Brivio — no key to copy. Ask the Brivio AI assistant with brivio_ask_assistant; anything it proposes waits for your approval in the app. Step-by-step guide: docs.brivio.ro/en/developers/ai-clients.
Clients that only take a token: point them 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_..." }
}
}
}What the agent can do
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.
Safety
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.
Local (stdio)
BRIVIO_API_KEY=brivio_sk_test_... npx @brivio/mcp