Why Barvinca MCP Is More Than OpenAPI Connected to an LLM
MCP gives AI a tool interface, but the real safety comes from Barvinca's scoped consent, account binding, bounded reads, approval-bound writes, idempotency, and evidence.
Read articleDesign notes, field-tested patterns, and documentation-backed guidance for ACC and BIM 360 administration.
MCP gives AI a tool interface, but the real safety comes from Barvinca's scoped consent, account binding, bounded reads, approval-bound writes, idempotency, and evidence.
Read articleA practical access-management pattern for adding, removing, and updating users across many Autodesk projects without losing review control.
Read articleBulk writes should not begin with a leap of faith. A dry-run should explain target scope, skipped rows, expected writes, and review risk.
Read articleThe Barvinca CREDS model uses one simple unit: one Autodesk write mutation costs 1 CREDS. Reads, sync, setup checks, and dry-runs cost zero.
Read articleA practical ACC offboarding pattern: inventory first, group the target projects, preview removals, execute in small batches, and keep evidence.
Read article