Devcon MCP Workshop 2026
MCP server integrating Autodesk Platform Services, exposing tools for LLM clients like VS Code Copilot, with OAuth authentication and agentic workflow support.
README
š MCP Server with Autodesk Platform Services (APS)
š Overview
This project implements a Model Context Protocol (MCP) server with support for:
- Tool exposure for LLM clients (e.g., VS Code Copilot)
- External API integration
- Autodesk Platform Services (APS) connectivity
- Authentication flows (2-legged & 3-legged OAuth)
- Custom client + agent architecture
It represents a production-oriented agentic AI backend system.
š§ Architecture
š· High-Level Flow
+------------------------+
| LLM Client (VSCode) |
| Copilot / Chat UI |
+-----------+------------+
|
v
+------------------------+
| MCP Server |
| (server.js / aps) |
+-----------+------------+
|
------------------------------------------------
| | |
v v v
+-------------+ +-------------+ +----------------+
| External | | APS APIs | | Custom Logic |
| APIs | | (OAuth) | | / Tools |
+-------------+ +-------------+ +----------------+
š· Agent Flow
User Prompt
ā
LLM decides tool
ā
MCP Server executes tool
ā
External API / APS call
ā
Structured response ā LLM ā User
š Project Structure
āāā .vscode/
ā āāā mcp.json # MCP configuration for VS Code client
ā
āāā node_modules/ # Installed dependencies
ā
āāā .env # Environment variables (API keys, secrets)
āāā .gitignore # Git ignored files
ā
āāā agent.js # Agent logic (tool orchestration)
āāā aps-server.js # APS integration server (OAuth + APIs)
āāā client.js # Custom MCP client implementation
āāā server.js # Core MCP server (tool definitions)
ā
āāā package.json # Project metadata & dependencies
āāā package-lock.json # Dependency lock file
āļø Tech Stack
- Node.js (ES Modules)
- Model Context Protocol (MCP SDK)
- Zod (schema validation)
- HTTP Streaming Transport
- Autodesk Platform Services (APS)
š Key Components
1. server.js
- Core MCP server
- Registers tools
- Handles client requests
2. aps-server.js
- Integrates Autodesk APIs
- Handles OAuth (2L + 3L)
- Secure API communication
3. agent.js
- Implements agentic behavior
- Decides which tools to call
- Enables multi-step workflows
4. client.js
- Custom MCP client
- Can simulate or replace VS Code client
5. .vscode/mcp.json
- Connects VS Code ā MCP server
š Getting Started
1ļøā£ Install Dependencies
npm install
2ļøā£ Setup Environment
Create .env file:
PORT=3000
# APS Credentials
APS_CLIENT_ID=your_client_id
APS_CLIENT_SECRET=your_client_secret
# External APIs
GEMINI_API_KEY=your_key
3ļøā£ Run Server
node server.js
Expected output:
MCP server running at http://localhost:3000/mcp
4ļøā£ Configure VS Code
Create:
.vscode/mcp.json
{
"servers": {
"devcon-workshop": {
"type": "http",
"url": "http://localhost:3000/mcp"
},
"devcon-aps": {
"type": "http",
"url": "http://localhost:3001/mcp"
}
}
}
5ļøā£ Test Tools
In Copilot Chat:
#add 10 and 20
#greet John in spanish
What's the weather in London?
š§© Tool Design Pattern
server.registerTool(
"tool_name",
{
description: "Tool description",
inputSchema: {
param: z.string()
}
},
async ({ param }) => ({
content: [{ type: "text", text: "Result" }]
})
);
š Authentication
ā 2-Legged OAuth
Server-to-server
No user interaction
ā 3-Legged OAuth
User consent required
Fine-grained permissions
Recommended for production
šļø Production Considerations
š¹ Scalability
Stateless architecture
Horizontal scaling possible
š¹ Security
Use .env for secrets
Prefer 3LO for user data
š¹ Reliability
Input validation (Zod)
Structured responses
š¹ Observability Add logging for tool execution
Monitor API failures
šÆ Features
ā MCP-compliant server
ā External API integration
ā APS connectivity
ā Agent-based execution
ā Custom client support
š® Future Enhancements
Dockerize the application
Deploy on Azure / AWS
Add database-backed tools
Implement caching layer
š License
MIT License
š Acknowledgements
-
Autodesk Platform Services (APS)
https://autodesk-platform-services.github.io/mcp-devcon2026/ -
Model Context Protocol (MCP)
-
OpenAI / LLM ecosystem
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.