Home / MCP / APS MCP Server

APS MCP Server

Provides local MCP access to Autodesk Platform Services data with fine-grained access control.

typescript

37stars

View on GitHub

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
    "mcpServers": {
        "aps_mcp": {
            "command": "node",
            "args": [
                "/absolute/path/to/aps-mcp-server/build/server.js"
            ],
            "env": {
                "APS_CLIENT_ID": "YOUR_APS_CLIENT_ID",
                "APS_CLIENT_SECRET": "YOUR_APS_CLIENT_SECRET",
                "APS_SA_ID": "YOUR_SA_ID",
                "APS_SA_EMAIL": "YOUR_SA_EMAIL",
                "APS_SA_KEY_ID": "YOUR_SA_KEY_ID",
                "APS_SA_PRIVATE_KEY": "YOUR_SA_PRIVATE_KEY"
            }
        }
    }
}

This MCP server provides an experimental Model Context Protocol implementation for Node.js that lets you access Autodesk Platform Services APIs with fine-grained access control. It runs locally as an MCP server you can connect to from MCP clients, enabling you to explore model context data in your projects.

How to use

You will run the MCP server locally and connect your MCP clients to it. The server is started as a local process and exposed to clients via standard input/output configuration. Use a client that supports MCP to load the server as an endpoint, then execute model context queries or actions through that endpoint. When configured correctly, you can inspect model contexts, query ACC/BIM360 data, and test access control using your service account.

To connect from tooling, reference the local server runtime path and command, and ensure your environment provides the required APS credentials. Typical setups show using a local node process that hosts the MCP server and pointing clients to either a hosted HTTP MCP endpoint or the local stdio server channel.

How to install

Prerequisites you need before installing this MCP server:

Node.js
APS app credentials for a Server-to-Server application
Provisioned access to ACC or BIM360

Step-by-step setup flow you should follow to get a running server locally:

Create a local environment file at the project root named .env and populate your APS credentials later in this file

Create and configure a service account for secure access to APIs. The following command creates a service account and returns environment variables you will store in your .env file.

npx create-service-account <username> <first name> <last name>

Additional setup for APS integration

Register your APS application client ID as a custom integration in Autodesk Construction Cloud. Then invite the newly created service account email to your ACC project(s) to grant access to the relevant data.

Run instructions for local development

Start using the Model Context Protocol Inspector or your preferred MCP client to connect to the local server. The server exposes a local endpoint once started, allowing you to run tests and validate model context queries.

Use with Inspector

Open the inspector tool and point it to the local MCP server. Use the connect action to start the MCP server and establish a connection to the inspector.

Use with Claude Desktop

Configure Claude Desktop to load the local MCP server. Add the absolute path to the server script in the Claude Desktop configuration so you can experiment with prompts against your local data.

Use with Visual Studio Code & Copilot

Enable MCP servers in your editor, then create a workspace configuration that launches the MCP server as a local process. Provide the full path to the server script so Copilot and other tooling can connect.

Use with Cursor

Set up a Cursor project with an MCP server entry that runs the local server script, using the absolute path to the built server file.

Available tools

ServiceAccountCreation

Creates a new service account and returns environment variables needed to run the MCP server, including SA ID, email, key ID, and private key.