Developing AI Agents for PLM: A Glimpse into the MCP Model
ByIlan Madjar, xLM Solutions
In this blog, xLM’s Ilan Madjar explores how agentic AI – powered by the MCP model – can move PLM beyond brittle integrations and toward smarter, adaptive workflows that evolve with user needs.

As artificial intelligence continues to evolve, its role in enterprise engineering environments – especially PLM – is becoming more compelling. At xLM Solutions, we’ve begun exploring how AI agents can transform the way users interact with Product Lifecycle Management systems by automating workflows, retrieving data, and making smart, contextual decisions on behalf of users. In a recent video, I showcased how to connect commercial AI large language models (LLM) and chat tools like OpenAI’s ChatGPT and Claude to PLM systems such as 3DEXPERIENCE and SOLIDWORKS PDM. But instead of relying on traditional, brittle API integrations, we used a new approach: Model-Client-Proxy (MCP) – a standardized framework that simplifies how AI agents interface with external systems. Keep reading for a high-level overview of the concepts behind AI agents and the MCP model, and what we demonstrated in the video. A deeper dive, including configuration details and code samples, will be offered in our upcoming webinar.
What Is an AI Agent?
An AI agent is more than a chatbot. It’s an autonomous system that can take actions on a user’s behalf, learn from interactions, adapt to different contexts, and intelligently integrate with external systems. In the PLM world, that means helping engineers and decision-makers:- Retrieve part information or BOMs
- Identify discrepancies across systems
- Support risk and compliance analysis
- Improve supply chain responsiveness
The Problem with Traditional Integrations
Historically, integrating AI models with PLM systems required custom code for each connection – writing and maintaining direct API calls for platforms like SOLIDWORKS PDM, 3DEXPERIENCE, Aras, OpenBOM. Autodesk Vault, Arena (these are just some of the systems we support). This approach has some serious drawbacks:- High maintenance overhead when APIs change
- Security challenges across multiple interfaces
- Scalability issues as systems and use cases expand
Introducing the MCP Model
The Model-Client-Proxy (MCP) framework offers a more scalable, secure, and standardized alternative. Instead of custom-building every integration, MCP acts as a universal adapter – think of it like a USB-C port for software systems. With MCP:- The AI agent connects to a single server
- Requests and responses are handled through a shared protocol
- A discovery and reflection process exposes available MCP server tools to the model
- Contextual prompts allow the agent to intelligently choose which tool to invoke
Claude, ChatGPT, and a Custom Console
In the video, I showcased three different environments where the MCP model was used to connect AI tools to PLM systems:- Claude AI Desktop Application
- Custom Console Application
- ChatGPT Web Interface
What’s Next: Behind the Scenes and Model Building
The goal of this session was to offer a sneak peek at what’s possible. In our upcoming webinar, we’ll go deeper into:- The backend configuration of the MCP client and server
- Code examples to help you build your own AI agent
- Best practices for managing prompts, tool registration, and user permissions
- A high-level introduction to building or fine-tuning AI models, including:
- Data collection and preprocessing
- Training strategies
- Deployment considerations
- Hosting your model securely (vs. using public LLM chatbots like ChatGPT, Claude, etc.)