aps-aecdm-mcp-dotnet
About
.NET MCP Server to connect with Claude Desktop and AEC Data Model API
Details
- License
- MIT
Explore
- Obtain a PKCE token for APS API requests.
- Retrieve hubs using the AEC Data Model API.
- Retrieve projects using the AEC Data Model API.
- Retrieve element groups by project.
- Retrieve elements filtered by category from an element group.
- Render a design with the Autodesk Viewer.
- Highlight elements in the Viewer.
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
aps-aecdm-mcp-dotnetCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
To make this work, you'll need to:
- Download and Install Claude Desktop
- Clone or download this repo
- Build this project
- Add a reference to the .csproj in the Claude configuration file (developers resource)
Clone this project or download it. It's recommended to install GitHub desktop. To clone it via command line, use the following (Terminal on MacOSX/Linux, Git Shell on Windows):
git clone https://github.com/joaomartins-callmejohn/aps-aecdm-mcp-dotnet
Visual Studio (Windows):
Replace client_id with your own key (Single Page application).
You can do it directly in the 'Properties/lauchSettings.json' file or through Visual Studio UI under the debug properties.
You'll need to add a reference to your MCP server in the claude_desktop_congif.json file
{
"mcpServers": {
"aecdm": {
"command": "dotnet",
"args": [
"run",
"--project",
"C:\\Users\\...mcp-server-aecdm.csproj",
"--no-build"
]
}
}
}
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"aps-aecdm-mcp-dotnet": {
"aecdm": {
"command": "dotnet",
"args": [
"run",
"--project",
"C:\\Users\\...mcp-server-aecdm.csproj",
"--no-build"
]
}
}
}
}McpServers
{
"aecdm": {
"command": "dotnet",
"args": [
"run",
"--project",
"C:\\Users\\...mcp-server-aecdm.csproj",
"--no-build"
]
}
}Introduction
This sample started as an experiment with the new Model Context Protocol brought as a challenge during one of our Autodesk Platform Accelerators. Special thanks to Mirco Bianchini for bringing this challenge and contributing to get to the solutions presented in this repo.
Prerequisites
To make this work, you'll need to:
- Download and Install Claude Desktop
- Clone or download this repo
- Build this project
- Add a reference to the .csproj in the Claude configuration file (developers resource)
DEMO VIDEO HERE
How it works
This sample creates an MCP server using the ModelContextProtocol .NET SDK.
In this scope we added 4 main tools to our server:
1. GetToken to obtain a PKCE token that is used in the APS API requests.
2. GetHubs to retrieve the hubs using the AEC Data Model API
3. GetProjects to retrieve the projects using the AEC Data Model API
4. GetElementGroupsByProject to retrieve the ElementGroups using the AEC Data Model API
5. GetElementsByElementGroupWithCategoryFilter to retrieve the elements from one ElementGroup using a category filter.
6. RenderModel to render one design with the Viewer
7. HighLightElements to highlight elements in the Viewer.
With these tools, you can use natural language to query the data from your elementgroups using the AEC Data Model API.
This is a first experiment with this new protocol. Feel free to submit suggestions and collaborate to this repo so we can improve its functionalities.
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
