teamcenter-mcp-server

MCP (Model Context Protocol) server that exposes Teamcenter-related capabilities to AI agents via MCP tools. Used to let an agent query or act on Teamcenter data/workflows through a standardized MCP interface.

Evaluated Apr 04, 2026 (20d ago)
Homepage ↗ Repo ↗ Infrastructure mcp teamcenter ai-agents integration enterprise-software plm
⚙ Agent Friendliness
36
/ 100
Can an agent use this?
🔒 Security
38
/ 100
Is it safe for agents?
⚡ Reliability
24
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
55
Documentation
35
Error Messages
0
Auth Simplicity
40
Rate Limits
0

🔒 Security

TLS Enforcement
50
Auth Strength
30
Scope Granularity
20
Dep. Hygiene
40
Secret Handling
50

Specific security implementation details (TLS enforcement, auth model, secret handling, and dependency status) are not present in the provided prompt. Treat this as an unverified connector; ensure you run it behind a trusted network boundary and add your own secret management/log redaction if needed.

⚡ Reliability

Uptime/SLA
0
Version Stability
40
Breaking Changes
30
Error Recovery
25
AF Security Reliability

Use Cases

  • Building agent workflows that need access to Teamcenter data (e.g., parts, BOMs, datasets)
  • Automating engineering/admin tasks in Teamcenter with an AI agent
  • Integrating Teamcenter operations into chat/agent systems that support MCP

Not For

  • Direct end-user web interactions
  • Public, internet-facing use without additional network/security controls
  • Use cases requiring guaranteed idempotency or transactional semantics unless explicitly documented

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

Methods: Unknown (not provided in prompt)
OAuth: No Scopes: No

The provided information does not include authentication details (e.g., API keys, OAuth, basic auth, Teamcenter credentials model, or how MCP server auth is handled).

Pricing

Free tier: No
Requires CC: No

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • Without documented pagination, agents may miss results when tool responses are truncated.
  • If tool calls are not idempotent, agent retries on transient failures can cause duplicate actions.
  • If authentication/credentials are not clearly scoped, the agent may be encouraged to request broader access than necessary.

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for teamcenter-mcp-server.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-04-04.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
Community Powered