Teamcenter Mcp Server — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited Teamcenter Mcp Server (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
This is a Model Context Protocol (MCP) server that integrates with Teamcenter PLM using its REST API. It allows you to interact with Teamcenter data directly through Claude.
The Teamcenter MCP server provides the following capabilities:
teamcenter://item-types - List of available item types in Teamcenterteamcenter://items/{id} - Details of a specific Teamcenter item by IDteamcenter://search/{query} - Search results for items in Teamcentersearch_items - Search for items in Teamcenterget_item - Get details of a specific item by IDcreate_item - Create a new item in Teamcenterupdate_item - Update an existing item in Teamcenterget_item_types - Get available item types in TeamcenterBefore using the Teamcenter MCP server, you need to update the configuration with your Teamcenter credentials. Edit the MCP settings file at:
Replace the placeholder values with your actual Teamcenter credentials:
{
"mcpServers": {
"teamcenter": {
"command": "node",
"args": ["/home/MCP/teamcenter-mcp-server/build/index.js"],
"env": {
"TEAMCENTER_BASE_URL": "YOUR_TEAMCENTER_BASE_URL",
"TEAMCENTER_USERNAME": "YOUR_TEAMCENTER_USERNAME",
"TEAMCENTER_PASSWORD": "YOUR_TEAMCENTER_PASSWORD"
},
"disabled": false,
"autoApprove": []
}
}
}Once configured, you can use the Teamcenter MCP server through Claude. Here are some examples:
use_mcp_tool
server_name: teamcenter
tool_name: search_items
arguments: {
"query": "engine",
"type": "Item",
"limit": 5
}use_mcp_tool
server_name: teamcenter
tool_name: get_item
arguments: {
"id": "ABC123"
}use_mcp_tool
server_name: teamcenter
tool_name: create_item
arguments: {
"type": "Item",
"name": "New Part",
"description": "A new part for the assembly",
"properties": {
"item_id": "PART-001",
"revision": "A"
}
}use_mcp_tool
server_name: teamcenter
tool_name: update_item
arguments: {
"id": "ABC123",
"properties": {
"description": "Updated description",
"status": "Released"
}
}use_mcp_tool
server_name: teamcenter
tool_name: get_item_types
arguments: {}access_mcp_resource
server_name: teamcenter
uri: teamcenter://item-typesaccess_mcp_resource
server_name: teamcenter
uri: teamcenter://items/ABC123access_mcp_resource
server_name: teamcenter
uri: teamcenter://search/enginenpm run buildFor local testing and development, you can use the included .env file to provide your Teamcenter credentials:
.env file in the project root directory:# Teamcenter API Configuration
TEAMCENTER_BASE_URL=https://teamcenter.example.com/api
TEAMCENTER_USERNAME=your_username
TEAMCENTER_PASSWORD=your_passwordnpm run devThis will start the server using ts-node, which allows you to make changes to the TypeScript code without having to rebuild the project each time.
The server will load the environment variables from the .env file and attempt to connect to your Teamcenter instance. You should see output indicating whether the authentication was successful.
If you encounter issues with the Teamcenter MCP server:
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.