Teamcenter integration for Claude: an MCP server that reads through revision rules and Access Manager, and on into SAP

For manufacturers and energy companies on Siemens Teamcenter who want an agent to answer structure and change questions that do not stop at the edge of the PLM.

Teamcenter integration for Claude and other agents needs a purpose-built MCP server: on 19 September 2026 Siemens shipped an in-product AI BOM agent but no MCP server for Teamcenter data. Pexon builds one on Teamcenter Services with the user's own session, explicit revision rules, named tools such as get_change_impact, and a read path into SAP.

The decision

Siemens is putting agents into Teamcenter. The question is what reaches across its edge.

Teamcenter 2606, released in June 2026, brought an AI BOM agent that Siemens describes as able to understand BOM context, propose changes and act on them with human oversight. That is the right tool for BOM work inside Teamcenter, and nothing on this page argues against using it.

What it does not do is answer the question an operations lead asks on a Tuesday: this change notice is released, so which SAP BOMs, open production orders and supplier documents does it touch? Half of that answer lives outside Teamcenter. An MCP server with a small set of Teamcenter tools and a small set of SAP tools lets Claude, or any agent that speaks the protocol, put both halves together, under the rights of the person asking.

Checked 19 September 2026

What Siemens ships around Teamcenter today, and what is left for an outside agent

Offering	What it covers	What remains
Teamcenter Copilot and AI BOM agent	Assistance and multi-step BOM workflows inside Teamcenter, on models Siemens certifies.	Nothing outside Teamcenter. No MCP interface was mentioned in the 2606 release or on the product page.
Teamcenter Gateway for Enterprise Applications (T4EA)	Siemens' integration product for ERP, MES and CRM, including SAP Business Suite and Oracle E-Business Suite.	System-to-system synchronisation, not questions. It moves data; it does not give an agent named operations.
Siemens developer portal MCP	An MCP set-up that lets an assistant read Siemens product documentation through llms.txt.	Documentation, not your data. It helps write code against Teamcenter; it does not read a BOM.
Teamcenter Services (SOA, JSON REST)	The service layer Active Workspace uses, with Java, C# and C++ bindings and a JSON endpoint.	An interface with documentation gaps the community has raised publicly. A tool list still has to be designed on top.
Community Teamcenter MCP servers	A handful on GitHub. One targets Teamcenter 2412+ with 30+ tools; another is archived and says it is not functional.	Self-declared maturity, small user base. Useful to read, not a base for production.

Why Teamcenter is hard for agents

Three parts of Teamcenter that decide whether an answer is right

Access Manager, project security and export control

Teamcenter decides access through the Access Manager rule tree, object ACLs, project and program membership and, where it applies, ITAR or export-control classification. None of that survives a server that logs in once as a technical user: every answer would carry that user's reach, which in a PLM is usually far wider than any engineer's.

What the server does Opens a Teamcenter session per user and lets Teamcenter answer the access question. It never filters on its own.

Revision rules, variant rules and effectivity

The same item has a working structure, a released structure and a structure valid for a serial range or a date. Asked without a revision rule and a variant rule, a structure query returns something that exists in the database and matches no product that was ever built. In our assessment this is the easiest way for a PLM connector to give a confident wrong answer.

What the server does Makes the revision rule a required input of every structure tool, with the rule your planners use as the default, and returns it with the answer.

A BMIDE data model that is yours, not Siemens'

Most Teamcenter installations extend the data model through BMIDE with company item types, properties and relations. A generic connector sees the standard types; the properties your engineers search by are often custom. Public documentation of the loosely typed services is thin, which the Siemens community has pointed out.

What the server does Maps the custom types and properties in the blueprint, against your deployed template, before the tools are written.

The first tool list

What the agent may read, and what it may only propose

Read, release one

find_items by ID, name or custom property, returning only what the user may see
get_bom with a revision rule and variant rule as required inputs
where_used parent assemblies under the same rules
compare_bom two revisions or two rules, as added, removed and changed lines
get_change_impact affected items of a change, their parents and related datasets
compare_to_sap released structure against the SAP BOM for a plant, through the SAP tools

Propose only, release two

draft_change_request a filled draft the engineer opens and submits in Teamcenter
draft_bom_delta_report the Teamcenter to SAP differences as a document for the change board
never release, revise, delete or change structure on its own; those stay with a person in Teamcenter

How it runs

From today's set-up to a server you operate

Today
Copilot inside Teamcenter, SAP on its own
Engineers ask Teamcenter questions in Teamcenter and SAP questions in SAP. Cross-system questions go by email to whoever knows both.
where most plants are
Stage 1
Readiness Blueprint
Tool list agreed with PLM and ERP owners, a proof on your test system that a call runs in the asking user's session, the BMIDE mapping, and a costed build plan. All prices are net and exclude VAT.
2 weeks, €4,900
Stage 2
Use-case pilot
The read tools in production for one team, with the audit log, the evaluation questions and the SAP comparison. We need a Teamcenter administrator for about a day a week.
6 to 8 weeks, from €15,000
Stage 3
You run it, or we do
Your code, your repository, your environment, with runbook and tests. If you want us to operate it, monitoring starts at the listed rate; the next system reuses the identity and audit work.
from €3,000 per month

When not to build this

If your questions are about BOMs inside Teamcenter and nobody needs SAP, MES or supplier data next to them, use the Siemens agents and keep one fewer system to operate. A server earns its place when the question crosses a system boundary or when you want the same agent to work across PLM, ERP and maintenance.

Sources: Siemens: Teamcenter 2606 release (12 June 2026) · Siemens: Teamcenter AI · Siemens: Teamcenter Gateway for Enterprise Applications · Siemens developer portal: MCP how-to · Siemens community: loose-typed SOA documentation question · goenninger-b-t/tc-mcp · srgio-es/teamcenter-mcp-server (archived). Read 2026-09-19. Vendor documentation changes; verify against the current release.

MCP servers for industrial systems: 52 systems mapped — where Teamcenter sits among the PLM, ERP and MES systems we checked
Windchill integration for AI agents — the same problem on PTC's PLM, with a different permission model
Claude MCP server development for internal systems — the identity and audit pattern every connector reuses
SAP MCP server: Claude on S/4HANA without a service account — the SAP tools the Teamcenter comparison calls
Industrial MCP server security — why a vendor or community server's default rights are not safe for a plant, and what to restrict

Questions about a Teamcenter MCP server

Does Siemens offer an MCP server for Teamcenter?

Not for Teamcenter data, as of 19 September 2026. Teamcenter 2606 introduced an AI BOM agent inside Teamcenter, and the Siemens developer portal offers an MCP setup that searches product documentation. Neither lets an outside agent such as Claude read your BOMs or change objects. We re-check this quarterly, because Siemens may well add one.

Why not wait for the Teamcenter Copilot and the BOM agent?

Wait if every question your people ask is answered inside Teamcenter. Siemens builds its agents into its own product, which is the right place for BOM work in Teamcenter. The case for a server is the question that crosses a boundary: does the released structure match the SAP BOM, which open production orders a change touches, which supplier documents are affected. An in-product agent does not see the other system.

How do you stop the agent from seeing ITAR or export-controlled parts?

By never giving it more rights than the person asking. Every tool call runs in a Teamcenter session for that user, so Access Manager, project security and your classification rules decide what comes back, exactly as in the rich client. We do not reimplement those rules in the server. Where your set-up only allows a shared technical user, we restrict the tools to unclassified data and write that limit into the blueprint.

What does a Teamcenter MCP server cost?

The two-week Readiness Blueprint is fixed at €4,900: the tool list, a proof on your test system that calls run as the asking user, and a costed build plan. A first production server is usually a use-case pilot from €15,000. Whether agent access needs additional Teamcenter licences depends on your Siemens agreement; check it with Siemens before the pilot. All prices are net and exclude VAT.

Where does a Teamcenter MCP server reach its limits?

It reaches its limits wherever your data model is richer than the tool list. A deeply customised BMIDE model means more mapping work, and we find out how much only in the blueprint. The first release reads and proposes; it never releases or changes structure itself. It does not interpret NX geometry. And we have not yet built a Teamcenter server for a named customer, so the plan rests on the API and your instance, not on a previous project.

Next step

Bring the Teamcenter question that always ends in SAP.

Thirty minutes with the architect who would run the blueprint. We look at your Teamcenter release, your security set-up and the first tools, and tell you plainly whether a server is worth it.