home / mcp / acc mcp server

ACC MCP Server

Provides access to Autodesk Platform Services data and actions through a local MCP server with APS credentials.

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "eversedevelopment-aps.mcp": {
      "command": "node",
      "args": [
        "c:/repositories/00-Research/ACC.MCP/dist/index.js"
      ],
      "env": {
        "APS_SCOPE": "data:read",
        "APS_CLIENT_ID": "YOUR_CLIENT_ID",
        "APS_CLIENT_SECRET": "YOUR_CLIENT_SECRET"
      }
    }
  }
}

ACC.MCP exposes Autodesk Platform Services tools as an MCP server, enabling AI assistants to access APS data and actions through a standardized, stdin/stdout interface. This makes it practical to integrate APS capabilities into assistants like Cursor, with secure 2-legged OAuth and simple local deployment.

How to use

You run the MCP server locally and connect to it from an MCP client. The server communicates over the standard input and output streams, so your client starts the server process and talks to it via stdin and stdout. To use it with a client like Cursor, configure the MCP server in your client’s MCP settings, providing the command to run Node and the path to the server’s entry file, along with APS credentials.

Once configured, you can list hubs and projects, browse folders, and fetch item metadata using the tools provided by ACC.MCP. The server handles authentication with APS by using 2-legged OAuth credentials you supply, so you don’t need to manage user tokens directly.

How to install

Prerequisites you must have installed before configuring ACC.MCP:

Node.js 18+

APS Client ID
APS Client Secret

Then follow these steps to install and prepare ACC.MCP on your machine.

npm install
```

cp .env.example .env
# Edit .env to set APS_CLIENT_ID and APS_CLIENT_SECRET

How to run the MCP server locally

Build the server after configuring credentials, then start the server so your MCP client can connect to it.

npm run build

Start the server directly using Node, or through the provided start script. You can also load credentials from an environment file.

npm start
or
node dist/index.js

Cursor configuration

Configure the MCP server in your Cursor client to enable APS access. Use the following example configuration as a template, and adjust the path to match your machine.

{
  "mcpServers": {
    "acc-mcp": {
      "command": "node",
      "args": ["c:/repositories/00-Research/ACC.MCP/dist/index.js"],
      "env": {
        "APS_CLIENT_ID": "your_client_id",
        "APS_CLIENT_SECRET": "your_client_secret",
        "APS_SCOPE": "data:read"
      }
    }
  }
}

Additional configuration and notes

MCP Bundle for one-click installs is supported if you want to distribute ACC.MCP as a packaged bundle. The process builds the server, creates a production bundle, and prepares a zipped MCPB file for compatible clients.

npm run pack

If you pack the bundle, you’ll distribute a .mcpb file that includes the manifest and server runtime, ready for installation in compatible MCP clients. You’ll be prompted for APS credentials when you install the bundle in the target application.

Security and credentials

Keep your APS Client ID and Client Secret secure. Store them in an environment file or your chosen secret manager and load them at startup. The server uses 2-legged OAuth to authenticate with APS, so only the credentials you provide are required for access.

Available tools

aps_list_hubs

List all ACC / BIM 360 hubs with name, id, type, and region.

aps_list_projects

List projects within a hub and return project name, id, platform, and last modification date.

aps_get_top_folders

Retrieve root folders for a selected project (e.g., Project Files, Plans, Shared).

aps_get_folder_contents

Provide a summarized listing of a folder with file-type breakdown, sizes, and version information. Supports filtering and hiding hidden items.

aps_get_item_details

Fetch metadata for a single file, including name, type, size, version, and dates.

aps_get_folder_tree

Return a recursive folder tree with file counts per folder, configurable by depth.

aps_docs

APS quick-reference: common ID formats, workflow, API paths, file extensions, and troubleshooting tips.

aps_get_token

Obtain and verify a 2-legged access token; all other tools handle token management automatically.

aps_dm_request

Call any APS Data Management API endpoint (e.g., hubs, projects, topFolders, folders, contents, items, versions, downloads, jobs, storage, commands). Returns full JSON:API responses.