Model Context ProtocolBimefy is a construction site intelligence platform. It connects BIM, construction planning, cameras, reality capture and site data so teams can compare what was planned with what is actually happening on site.
The Model Context Protocol (MCP) is an open standard for connecting AI assistants to external tools and data. Instead of each assistant needing a bespoke connector, a system exposes an MCP endpoint that describes the tools it offers, and a supported client connects to it.
Bimefy provides an MCP endpoint for its projects. Rather than opening the database to a model, it exposes a defined set of tools: specific, named operations such as retrieving current project progress, listing tasks, checking milestone status, summarising safety events or reading 4D view data. An assistant can call those tools and nothing else.
Access is controlled the same way as the rest of the Bimefy integration API. A project administrator issues a token, chooses the scopes it carries, and can revoke it. A token is bound to the project it was issued for, and the tools an assistant can see depend on the scopes granted. Requests are logged.
This is a deliberately narrow design. Bimefy does not hand an external AI system open access to project information, and the integration does not act on its own: an assistant answers questions using the tools you have approved, within the project you approved them for.
What the MCP endpoint offers, and how it is contained.
MCP is an open standard, so supported assistants connect without a bespoke integration being written for each one.
Bimefy exposes named operations covering project progress, tasks and milestones, safety and security events, site conditions, camera status and 4D data.
Each token is bound to one project and carries only the scopes granted to it. The tools an assistant can see follow from those scopes.
Calls made with an integration token are logged, so it is possible to review what was requested.
Bimefy provides the endpoint and a configuration snippet for supported MCP clients.
Grouped by the kind of question they answer. Availability depends on the scopes on the token.
Current project details, overall progress, tasks with filters for status and due date, milestone status including overdue milestones, and how model components changed over a chosen window.
A current safety score with a daily trend, safety events including missing PPE, after-hours intrusion and person-detection events, grouped hazard detections, camera status, and IFC validation results.
The 4D views on a project, the catalogue of tasks within them, and the model elements those tasks relate to.
Issue a token, point a client at the endpoint, ask questions.
A project administrator issues a token in Bimefy's integration settings and selects the scopes it should carry.
Point a supported MCP client at the Bimefy endpoint using that token.
The assistant calls the Bimefy tools that its scopes allow.
The answer is based on what those tools returned for that project, not on a general impression.
Questions an assistant can answer from live project data.
Get the state of a project without opening a dashboard and reading it manually.
Pull safety events for a window and let the assistant summarise what came up.
Ask which milestones have passed their date and what the current status is.
Ask about the tasks in a 4D view and the model elements they relate to.
Building a separate connector for every assistant does not scale, and each one becomes its own security review.
MCP moves that problem to a standard. Bimefy exposes one endpoint with a defined set of tools, and supported clients connect to it. The tools are explicit, so what an assistant can reach is a list rather than a guess.
It also keeps control where it belongs. Tokens are issued per project, carry only the scopes you grant, can be revoked, and are logged. Approved access, not open access.
Roles that get the most out of this integration.
Other systems Bimefy connects with
Connect your own cameras, capture pipelines and sensor systems to Bimefy with scoped API tokens.
View integrationBring Autodesk models, folders and file versions into Bimefy, and compare them with captured site reality.
View integrationConnect construction schedules with BIM and captured site progress, and compare the programme with what the site shows.
View integrationSee how Bimefy can connect your existing construction systems and turn site data into project intelligence.
Trusted by innovation driven companies