This MCP server provides a Node.js-based implementation of the Model Context Protocol (MCP) for Autodesk Platform Services (APS). It exposes an MCP server that authenticates with APS using a provisioned service account and enables fine-grained access control via the new Secure Service Accounts feature. The server can be started with Node.js and is intended to be used with tools that support MCP, such as the Inspector, Claude Desktop, Visual Studio Code (Copilot MCP), and Cursor, by pointing them at the running server or by embedding it in development environments. Once running, you can connect to the MCP server to explore model context data and perform operations defined by the APS MCP integration.

Prerequisites:

• Node.js installed on your machine
• APS application credentials (Server-to-Server type)
• Provisioned access to ACC or BIM 360 as required

Setup steps:

1. Clone the repository: git clone https://github.com/your-org/aps-mcp-server-nodejs.git cd aps-mcp-server-nodejs

2. Install dependencies (Yarn is suggested in the repo): yarn install

3. Build the TypeScript code (if applicable): yarn run build

4. Create an environment file with APS credentials (or provide via env vars): APS_CLIENT_ID=your_client_id APS_CLIENT_SECRET=your_client_secret

   Service account credentials will be populated after creating a service account

   APS_SA_ID=your_service_account_id APS_SA_EMAIL=your_service_account_email APS_SA_KEY_ID=your_service_account_key_id APS_SA_PRIVATE_KEY=your_service_account_private_key

5. Run the server: node build/server.js

   Or use a process manager and environment variables as needed

6. Optional: create a service account via the provided utility (as in the README): npx create-service-account <username> <first name> <last name>

   Add the resulting APS_SA_* environment variables to your .env file or process environment

Tips and notes:

• The server expects APS credentials and a provisioned service account; ensure you have both before starting.
• If you modify any environment variables, restart the server to apply changes.
• When integrating with Claude Desktop, VS Code, or Cursor, use absolute paths to the built server.js file in your configuration as shown in the README examples.
• Keep your service account private key secure and do not commit credentials to version control.
• If you run into issues connecting to APS, verify that the service account has the necessary permissions on your ACC/BIM 360 projects and that the APS app is configured for server-to-server access.
• Use a .env file for local development to keep credentials out of source control, and load them via your runtime environment.