DE
Contact us

3DEXPERIENCE integration for Claude: an MCP server for ENOVIA data that works in the user's security context and crosses into SAP

For aerospace, automotive and industrial equipment companies on Dassault Systèmes 3DEXPERIENCE who want an agent to answer change and structure questions with the platform's own access rules intact.

3DEXPERIENCE integration for Claude and other agents runs through an MCP server on the platform's REST web services. On 19 September 2026 Dassault Systèmes offered virtual companions inside the platform but no MCP server for ENOVIA data. Pexon builds one that works in the user's own security context, exposes named change and BOM tools, and compares against SAP.

Our position

A virtual companion inside 3DEXPERIENCE answers 3DEXPERIENCE questions well. The expensive questions have their second half in SAP, and that is where an MCP server earns its place.

Checked 19 September 2026

What Dassault and the community offer for agents on 3DEXPERIENCE today

What existsWhat it isWhat it leaves open
Virtual companions AURA, LEO, MARIEDassault's in-platform companions for program management, engineering and science, announced as available in July 2026.They work inside the platform. The announcement names no MCP interface for outside agents.
SysML v2 and MCP in the CATIA MBSE communityA community post showing MCP over the SysML v2 REST API, driving a robot arm and a DELMIA simulation.A demonstration for systems models, not a server for parts, structures and change actions.
3DEXPERIENCE REST web servicesThe platform's supported web-service interface. SOAP web services are no longer supported.An interface, not a tool list. Contexts, rights and operations are still to be designed.
Community ENOVIA MCP serverOne public repository at the time we checked, without stars or a licence.Nothing to build production on.
Community CATIA MCP serversSeveral, driving a CATIA V5 desktop session through COM automation; the most followed has about a hundred stars.Desktop CAD automation. They do not read managed ENOVIA data for many users.

Why 3DEXPERIENCE is hard for agents

The same user sees different data depending on the context they chose

In our reading of the platform, access is not a property of a user alone. A person works under a security context, a role in an organisation within a collaborative space, and the same query returns different objects under different contexts. A server that logs in once, as one technical user in one context, returns that context's view to everyone. For programme-separated aerospace or defence work, that is the failure a security review stops the project on.

Two more parts decide whether an answer is right. Structures and change actions carry maturity states and effectivity, so a question about the current product needs an explicit statement of which maturity counts as current. And which web services are available can differ between the cloud platform and an on-premise installation, which the blueprint checks against your deployment before any tool is promised.

Licensing is the last question. Whether an agent acting for named users needs additional roles or licences is set by your Dassault agreement. We list it for your account team; we do not answer it for them.

What we build

What sits between Claude and your 3DEXPERIENCE platform

Three layers, in the order a call passes through them. The middle one is the reason this connector is different from a Windchill or Teamcenter server.

  1. 01

    Named tools, no free queries

    A short list of operations, each with typed inputs and a documented result: find parts, read a structure at a stated maturity, list open change actions, show what a change action affects, compare with SAP. Claude can call these and nothing else.

    • Model Context Protocol
    • typed tool schema
    • read-only release 1

  2. 02

    Identity and security context, per call

    The asking user's sign-in is carried through to the platform, and the security context is an explicit tool input, defaulting to the user's usual context and written to the log. The platform, not the server, decides what the user may see.

    • 3DPassport
    • your identity provider
    • context per call

  3. 03

    Audit, evaluation and the SAP side

    Every call is logged with user, context, tool and result count. A fixture of real questions with known answers runs on every platform upgrade. The SAP tools needed for the comparison sit in the same server, under the same rules.

    • audit log
    • evaluation fixture
    • SAP OData

Rules that hold across all three layers

  • No super-user account, no stored platform password.
  • No maturity promotion, no change-action completion by the agent.
  • Your code, your repository, deployed in your environment.

The first tool list

Seven operations for the first release

The list the blueprint ends with and the PLM owner signs. Names are adapted to your data model; the security context appears on every call because it changes the answer.

# 3dx-mcp, release 1: read-only, the user's own context on every call
find_parts(query, context)                          # parts the user may see in that context
get_structure(part, maturity="released", context)   # engineering structure at a stated maturity
where_used(part, maturity, context)                 # parents under the same rules
list_change_actions(part, state?, context)          # open and recent change actions
get_change_impact(change_action, context)           # proposed and realised changes, affected items
compare_structures(part, rev_a, rev_b, context)     # added, removed, changed
compare_to_sap(part, plant, context)                # released structure vs SAP BOM, line by line

Run the same where_used call under two contexts. If the answers differ where the platform says they should, the identity layer works; if they are identical, the server is seeing too much.

Start here

What you hold after the two-week Readiness Blueprint, €4,900 fixed

  • Signed tool list the operations above, adapted to your data model and agreed with the PLM owner
  • Context proof a recorded test on your tenant or server that calls run as the asking user in the chosen context
  • Service inventory which web services your deployment exposes, cloud or on-premise, and which tool depends on which
  • SAP mapping how an ENOVIA structure line corresponds to a SAP BOM line in your plants
  • Open questions for Dassault licensing and roles for agent access, written for your account team
  • Costed build plan for a first production server, usually a use-case pilot from €15,000. All prices are net and exclude VAT.

When the companions are enough

If your people only need help inside 3DEXPERIENCE, such as finding a document, summarising a change action or navigating a programme, Dassault's companions are built for that and there is nothing for a separate server to add. Build a server when the question needs SAP, MES or maintenance data next to the platform's, or when you want one agent across several systems instead of one assistant per vendor.

Sources: Dassault Systèmes: new virtual companion skills (July 2026) · CATIA MBSE Cyber Systems community: SysML v2 and MCP · PLM Coach: 3DEXPERIENCE web services guide · daiemon12/catia-v5-mcp-server. Read 2026-09-19. Vendor documentation changes; verify against the current release.

Related

Questions about a 3DEXPERIENCE MCP server

Does Dassault Systèmes offer an MCP server for 3DEXPERIENCE?

Not for ENOVIA data, as of 19 September 2026. Dassault's virtual companions AURA, LEO and MARIE work inside the platform, and their July 2026 announcement does not mention MCP. A post in Dassault's CATIA MBSE community shows MCP over the SysML v2 REST API driving a robot demonstration, which is a demonstration, not a product for PLM data. We re-check this quarterly.

Is this the same as a CATIA MCP server?

No. The CATIA MCP servers on GitHub drive a CATIA V5 desktop session through its COM automation interface, which is useful for modelling tasks on one workstation. A 3DEXPERIENCE server reads the platform's managed data: parts, structures, change actions and their state, for many users, through the platform's web services. The two can coexist, and they solve different problems.

How does the agent respect collaborative spaces and roles?

By running every call as the person asking, in the security context that person would choose in the platform. The server does not hold a super-user login and does not filter results itself; the platform decides what comes back. If a user works in several contexts, the context is an explicit input of the tool, not a hidden default, and it is written to the audit log.

What does a 3DEXPERIENCE MCP server cost?

The two-week Readiness Blueprint is fixed at €4,900: the tool list, a proof that calls run in the user's context on your tenant or server, and a costed build plan. A first production server is usually a use-case pilot from €15,000. Whether agent access needs additional platform licences or roles depends on your Dassault agreement; check it with Dassault or your reseller. All prices are net and exclude VAT.

What are the limits of a 3DEXPERIENCE MCP server?

Its limits are the services your platform exposes. Cloud and on-premise deployments can differ in which web services are available, and we find that out in the blueprint, not before. The first release reads and proposes; it does not promote maturity states or complete change actions. It does not interpret CATIA geometry. And we have not yet built a 3DEXPERIENCE server for a named customer.

Next step

Bring one change question that needs both ENOVIA and SAP.

Thirty minutes with the architect who would run the blueprint. We look at your deployment, cloud or on-premise, your security contexts and the first tools, and say whether a server is worth building.

Contact us