Article - CS476171
Connecting Claude Desktop to a Windchill AI Assistant MCP Endpoint
Modified: 27-Jul-2026
Applies To
- Windchill PDMLink 13.0.2.11
- Windchill PDMLink 13.1.3.0
- Windchill PDMLink 12.1.2.23
Description
- This article describes an approach for bridging the gap: a small local MCP server, packaged as a Claude Desktop extension, that authenticates to Windchill and relays MCP traffic to the Windchill MCP endpoint.
- This article documents the motivation, the Windchill authentication model, and the key implementation techniques, so that the approach can be reproduced and adapted.
-
This article describes the recommended approach for connecting an MCP (Model Context Protocol) client to an SSO-protected Windchill environment when end users access the system through Claude Desktop
- When to use this approach: This method is appropriate when the end user connects to Windchill through Claude Desktop
-
What It provides: A packaged, installable extension (.mcpb) - Build extension once, distribute to all users, install locally and input data for authentication using Windchill User; the password is stored in the OS keychain.
-
Audience: End users, once the company has built and provided the extension. Specific to Claude Desktop.
- When to use this approach: This method is appropriate when the end user connects to Windchill through Claude Desktop
- Important: PTC does not ship a ready-made extension. The article provides illustrative code snippets only; the customer is responsible for building the .mcpb extension potentially using the below article's guidance and then distribute/install it internally.
- The key factor in selecting an MCP integration strategy is the level of control you have over the MCP client - Depending on the client environment and deployment constraints, refer other approaches in Knowledge Base articles below:
This is a printer-friendly version of Article 476171 and may be out of date. For the latest version click CS476171