This MCP server exposes Autodesk Platform Services (APS) APIs through the Model Context Protocol with fine-grained access control via Secure Service Accounts. The server is built with Node.js and acts as a bridge that authenticates using a SSA (secure service account) and forwards requests to APS on behalf of clients. You can use standard MCP tooling to interact with it, such as the MCP Inspector, Claude Desktop, and editor integrations, to query and manipulate model-context data across APS resources. The server is designed to be run locally or in your environment where you have APS credentials set in environment variables or a mounted .env file.

Prerequisites:

• Node.js installed on your machine
• Access to an APS Server-to-Server application and provisioned ACC permissions
• A provisioned Secure Service Account (SSA) with a downloaded private key (.pem)

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 install

   or npm install

3. Create a .env file in the project root and set required variables: APS_CLIENT_ID="<your APS client ID>" APS_CLIENT_SECRET="<your APS client secret>" SSA_ID="<serviceAccountId>" SSA_KEY_ID="<kid from SSA key>" SSA_KEY_PATH="/full/path/to/your/ssa-key.pem"
4. Start the server: node server.js

   or use a process manager like pm2 to keep it running

5. Verify the server is running by hitting the MCP endpoint (e.g., http://localhost:3000 or configured port) and using an MCP client (Inspector, Claude, VS Code, etc.).

• Ensure APS_CLIENT_ID and APS_CLIENT_SECRET correspond to a Server-to-Server APS app.
• The SSA must have access to the desired APS resources and ACC projects.
• Keep the private key secure; never commit it to source control. Consider mounting the key via a secure secret store in production.
• If the server cannot authenticate, double-check SSA_ID, SSA_KEY_ID, and SSA_KEY_PATH; verify the .pem file permissions.
• When using Claude Desktop or VS Code MCP integrations, provide the absolute path to server.js or adjust your config accordingly to point to the running server instance.
• You can scale this by running multiple instances behind a reverse proxy and load balancer if needed.