mcp -dotnet-bimengine

This MCP server is a .NET-based implementation of an MCP server designed to work with BIM 360 workflows and the BIM Engine toolset. It provides a lightweight server that can be run locally or in a development environment to simulate an MCP server for testing SDk integrations. The project emphasizes a console-backed approach with a single MCP server that can be extended with additional capabilities. Use the included instructions to build and run the server, then connect client tooling or automation scripts to the MCP API surface exposed by the running server. The repository references a BIM Engine context and includes guidance for integrating with Cloud Desktop workflows, as well as references to local “capture” and “tessdata” resources used for OCR and environment setup during development.

Prerequisites:

• .NET SDK (recommended: .NET 8 or later) installed on your machine
• Visual Studio 2022 (optional for IDE-based workflow) or a text editor/IDE of your choice
• Git

Step-by-step installation:

1. Clone the repository: git clone https://github.com/sergiomauz/mcp-server-dotnet-bimengine.git cd mcp-server-dotnet-bimengine

2. Open the solution or project:

   • If using Visual Studio, open the provided .sln file (if available) or the .csproj file for the MCP server.
   • If using the command line, navigate to the directory containing the MCP project.

3. Restore dependencies: dotnet restore

4. Build the project: dotnet build

5. Run the MCP server: dotnet run --project path/to/your/mcp-dotnet-bimengine.csproj

6. Confirm the server is listening on the expected port and ready to accept MCP client connections. If you have environment-specific configurations, adjust the app settings or environment variables as needed.

Tips and common issues:

• Ensure you have the correct .NET SDK version installed that matches the project requirements.
• If running in a Docker or containerized environment, map the port correctly and expose the necessary volumes for any capture or tessdata resources.
• The repository mentions a local workspace structure with a dedicated captures and tessdata directory. Ensure these folders exist in the expected paths if your workflow relies on OCR or image captures.
• Environment variables such as DOTNET_ENVIRONMENT and MCP_SERVER_PORT can be adjusted to fit your development or production setup.
• If you encounter build errors related to missing assets, verify that referenced resources (e.g., captures, tessdata) are present in your local workspace as described in the README.
• When integrating with Cloud Desktop workflows, you may be instructed to place a configuration JSON into a specific path; follow those steps to enable auto-discovery by the BIM Engine tooling.