Barvinca MCP is now available at https://mcp.barvinca.com/mcp for compatible remote Streamable HTTP MCP clients.

The first production catalog contains thirty focused tools for connection checks, authorized ACC account and project discovery, member and role lookup, live domain evidence, operation inspection, approval-bound project membership changes, cancellation, and recovery.

Designed for least privilege

Clients connect through Barvinca OAuth using authorization code, Dynamic Client Registration, and S256 PKCE. Seven independent scopes separate general reads, five ACC data domains, and write access. Autodesk secrets and tokens are not returned to the AI client.

Writes remain human-directed

Supported writes require a preflight, review of the exact immutable plan, and its unexpired SHA-256 approval digest. Execution is idempotent, capped at fifty items, and recorded as a durable operation with per-item outcomes, CREDS reconciliation, evidence, and recovery status.

Start with read-only access

New connections should request only the scopes needed for the current job. There is no generic HTTP passthrough or arbitrary Autodesk endpoint tool in the hosted catalog. Account and project checks are enforced by Barvinca before supported requests reach ACC.

Get started: Read why Barvinca MCP differs from a plain OpenAPI connection, then use the connection guide for Claude, Codex, ChatGPT, Cursor, and other compatible clients.