Autodesk Platform Services MCP Server

Created By
Guidogla year ago
Autodesk Platform Services MCP server
Overview

what is Autodesk MCP?

Autodesk MCP is a Model Context Protocol server that facilitates interaction with Autodesk Platform Services, particularly focusing on the Model Derivative API.

how to use Autodesk MCP?

To use Autodesk MCP, run the server using the command npx -y @autodesk/dev-mcp@latest and configure it with Cursor or Claude Desktop as per the provided documentation.

key features of Autodesk MCP?

  • Integration with Autodesk Platform Services APIs
  • Tools for searching APS documentation
  • Access to Model Derivative API information

use cases of Autodesk MCP?

  1. Searching Autodesk Platform Services documentation.
  2. Accessing and utilizing Model Derivative API for model data.
  3. Implementing workflows with Autodesk Platform Services.

FAQ from Autodesk MCP?

  • What is the Model Context Protocol?

The Model Context Protocol is a standard for interacting with Autodesk APIs, enabling developers to build applications that can leverage Autodesk's powerful tools.

  • Is there a guide for setting up Autodesk MCP?

Yes! Detailed setup instructions are available in the Cursor MCP documentation and Claude Desktop MCP guide.

  • What programming language is Autodesk MCP built with?

Autodesk MCP is built using TypeScript.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Guidogl
Star
0
Language
TypeScript
License
ISC license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago