🌼 RAPS
Download
Cross-Platform Pain #3

4,078 Apps and Zero Developer Tools: The Autodesk App Store Gap

We audited every app on the Autodesk App Store. Zero CLI tools. Zero auth helpers. Zero MCP integrations. Here's the full analysis.

#autodesk #app-store #developer-experience #research #data-analysis
Dmytro Yemelianov - Author
RAPS Team
Autodesk Expert Elite • APS Developer

TL;DR: We audited all 4,078 apps on the Autodesk App Store. We searched for CLI tools. Authentication helpers. Translation debugging utilities. MCP integrations. Developer productivity tools of any kind. The result: zero. Across every category.

The Data At a Glance

4,078
Apps Audited
0
CLI Tools
0
Auth Helpers
0
MCP Integrations
1
ACC Admin (Web Only)

4,078 apps. Not a single command-line tool. Not a single authentication helper. Not a single MCP integration. One ACC admin tool exists — IMAGINiT ACCelerate — and it is a web UI with no CLI, no scripting capability, and no API access.

Category Gap Analysis

Developer Tool Categories: App Store vs. Reality

CategoryExisting AppsWhat Developers NeedRAPS Coverage
Design Automation CLI0Command-line DA job management230+ commands
Authentication Helpers0Token management, refresh, storageBuilt-in auth system
Translation Debugging0Error diagnosis, retry, status trackingtranslate start/status
ACC Admin Automation1 (web only)CLI + scriptable bulk operationsadmin user add/remove/update
Cross-Platform CLI0Unified interface across APIs16 APIs unified
MCP/AI Integration0AI assistant tooling for APS114 MCP tools

Audit conducted March 2026. “Existing Apps” counts apps on apps.autodesk.com matching each category.

Six categories. Five have zero apps. One has a single web-only tool. That is the state of developer infrastructure on the Autodesk App Store.

What IS on the App Store

App Store Composition: 4,078 Apps by Type

Revit PluginsDominant category
AutoCAD Add-onsSecond largest
Viewer ExtensionsGrowing segment
Desktop Design ToolsVarious CAD tools
Other (Data, Civil 3D, etc.)Long tail

Pattern: All GUI-based. All end-user facing. Zero developer infrastructure. The entire marketplace is built for architects and engineers who click, not developers who script.

Why the Gap Exists

The store was designed for end users

The Autodesk App Store was built for architects, engineers, and construction managers. The submission process, categories, and discovery all optimize for desktop plugin distribution. A CLI tool does not fit this model.

No category for developer tools

The taxonomy itself excludes developer infrastructure. Categories include “Architecture,” “Structure,” “MEP,” “Construction” — but nothing for “Developer Tools,” “API Utilities,” or “Automation.” If there is no shelf, there is no product.

Separate developer ecosystem

Autodesk’s developer community (ADN) is entirely separate from the App Store ecosystem. ADN developers share code on GitHub and Forge blogs. The App Store serves a different audience. The two worlds do not overlap.

Result: a structural blind spot

4,078 apps serving one audience. Zero apps serving the people who build integrations, manage infrastructure, and automate workflows against APS APIs. Not a gap in execution — a gap in the platform’s design.

The Competitive Vacuum

Competitive Landscape: Developer Tools for APS

IMAGINiT ACCelerate
Web UI only. No CLI. No scripting. No API.
Web Only
BIM load
Approximately 5% of RAPS scope. Project setup only.
Narrow Scope
Petr Broz (Community Expert)
Basic MCP server. Educational. Not production tooling.
Community
Generic Consultancies
Custom development. No reusable tooling. No domain expertise.
Services
5 of 6
Categories with zero competition
114
RAPS MCP tools vs. 0 alternatives
16
APIs unified in RAPS vs. 0 elsewhere

What RAPS Fills

Each of the following categories has zero representation on the Autodesk App Store. RAPS covers all of them from a single binary.

Auth Helpers (0 apps exist)

# Login with all required scopes in one command
raps auth login --preset all

# Check token status, expiry, and active scopes
raps auth status

Translation Debugging (0 apps exist)

# Start a model translation with explicit output format
raps translate start "urn:..." --output svf2

# Poll translation status with error details
raps translate status "urn:..."

Bulk Admin Operations (1 web-only app exists)

# Add a user to all projects matching a filter
raps admin user add "$ACCOUNT" "user@company.com" --filter "^2024"

# Remove a departing employee from the entire account
raps admin user remove "$ACCOUNT" "departing@company.com"

MCP/AI Integration (0 apps exist)

# Expose 114 tools to AI assistants via Model Context Protocol
raps mcp serve

One binary. Six empty categories filled.

RAPS ships as a single Rust binary with no runtime dependencies. It covers authentication, data management, design automation, model translation, account administration, and MCP integration — every category the App Store does not serve.

Methodology

Scope: All apps listed on apps.autodesk.com as of March 2026.

Search terms: CLI, command-line, terminal, authentication, OAuth, token, MCP, Model Context Protocol, developer tools, API helper, translation debug, bulk admin, scripting, automation SDK.

Classification: Each app was checked for (a) command-line interface, (b) scriptability, (c) developer-facing functionality. Apps were classified as “developer tools” only if they met at least one of these criteria.

Limitations: This audit covers the public App Store only. Internal Autodesk tools and private enterprise solutions are not included.

What Comes Next

The data makes the case: 4,078 apps and not one of them serves the developer who builds on APS. The App Store has a structural blind spot, and the competitive landscape is empty.

Next in this series: “The API User Advocate: A Role That Doesn’t Exist Yet” — why every platform needs someone whose job is to feel the developer’s pain.

Related: