Skip to main content

Barvinca MCP — Controlled AI Operations for Forma®

TEAM International

Barvinca MCP — Controlled AI Operations for Forma®

TEAM International

Inspect Autodesk® Forma® (ACC) operations and run approval-gated bulk user workflows through a deterministic MCP server.

Free

Barvinca MCP connects authorized AI assistants to Autodesk Forma (Formerly Autodesk Construction Cloud®, ACC) through a fixed catalog of task-oriented tools and a deterministic execution layer.

Teams can inspect authorized accounts and projects, review operational membership data, query bounded Forma (ACC) Issues, RFIs, Assets, Submittals, Forms, and Form-template metadata, capture verifiable evidence, and review bulk-operation history. Write workflows support adding project users, removing project users, and updating project roles.

The server is designed for consequential administration work rather than one-shot raw API calls. Every write begins with a non-mutating, human-reviewable preflight. Execution is bound to the reviewed plan, and replay protection prevents the same approved intention from being silently dispatched twice.

Operational safety and accountability include:

  • OAuth authorization discovery, consent, scoped access, PKCE S256, refresh-token rotation, revocation, and audience-bound access tokens.
  • Fixed tools with bounded schemas and pagination; no arbitrary URL/method tool and no generic Autodesk API passthrough.
  • Server-side user, account, project, ownership, and scope authorization on every tool path.
  • Separate read, review, execution, recovery, and evidence capabilities.
  • Durable operation tracking with explicit handling for partial and uncertain upstream outcomes.
  • Predictable CREDS estimates and accounting for actionable mutations; read-only discovery and preflight do not charge CREDS.
  • Bounded, authenticated evidence for operational review and support.

The primary production execution path runs on Cloudflare Workers and Cloudflare Workflows rather than long-lived application containers. Its execution core is written in Rust, compiled to WebAssembly, and isolated behind a private service boundary. A microkernel-style separation keeps domain and safety semantics in a focused core while the Cloudflare runtime provides orchestration and managed platform capabilities. Containers are reserved for exceptional workloads that genuinely require an operating-system environment; they are not the default MCP or administration executor.

The production server exposes 30 fixed tools. It does not dynamically generate tools from OpenAPI and does not call an AI or LLM provider. Autodesk data is returned only to the user's authorized MCP client; use of that data by the user's chosen client or model is governed by the user's client/provider configuration.

Barvinca is not an Autodesk product. Autodesk, Autodesk Platform Services, Autodesk Forma (ACC), and Autodesk® BIM 360® are trademarks of Autodesk, Inc. Users must have the Autodesk permissions required for the data and operations they request.

Details

Frequently asked questions (FAQs)

Service type: Hosted remote MCP server

Transport: Streamable HTTP

Endpoint: https://mcp.barvinca.com/mcp

Setup documentation: https://barvinca.com/help/mcp

Production version: 0.12.0

Catalog: 30 fixed task-oriented tools

MCP resources: none

MCP prompts: none

AI/LLM providers called by Barvinca: none

Dynamic tool generation: no

Generic Autodesk API passthrough: no

OAuth supports protected-resource and authorization-server discovery, Dynamic Client Registration, S256 PKCE, consent, access-token refresh, revocation, disconnect, and reconnect. Customers do not enter an APS Client ID, APS Client Secret, Autodesk token, static API key, or custom authorization header into the MCP client.

Evidence captures and exports are bounded to 50 records per page. When more data is available, the result supplies a next cursor. Private export URLs are accessible only to the same signed-in Barvinca user and authorized Autodesk account.

Privacy: https://barvinca.com/privacy

Terms: https://barvinca.com/terms

Security: https://barvinca.com/security

Support: https://barvinca.com/support

Subprocessors: https://barvinca.com/subprocessors

Barvinca uses Autodesk APIs only for customer-directed workflows. Access remains subject to Autodesk licensing, user permissions, service availability, and API behavior.

ChatGPT web custom MCP apps are evaluation-only on eligible workspaces with developer mode. Because Barvinca does not advertise the offline_access scope, ChatGPT web may request reauthentication.

Cursor Agent CLI is production verified. Cursor Desktop uses the same MCP configuration but has not been independently tested.

Local-only clients and clients requiring API keys, bearer tokens, manually provisioned client secrets, or OAuth without discovery, Dynamic Client Registration, S256 PKCE, and refresh support are not supported.

Evidence capture and export are limited to 50 records per page; use the returned next cursor for additional pages. MCP tools do not create full-project archives.

Results depend on Autodesk service availability and the signed-in user's Autodesk licenses and permissions. Writes require barvinca.write, a current preflight, and explicit approval.

Documentation: https://barvinca.com/help/mcp

Support: https://barvinca.com/support

Support email: support@barvinca.com

Security: https://barvinca.com/security

Security email: security@barvinca.com

Privacy/deletion: privacy@barvinca.com

When requesting support, include the Barvinca operation ID or OP-XXXXXXXX slug, approximate timestamp, MCP client name/version, and a description of the requested workflow. Never send access tokens, refresh tokens, APS client secrets, or other credentials by email.

Found an issue?

Report a problem