PLMTrace

MCP URL not configured

NEXT_PUBLIC_MCP_URL is not set, so the address below is a placeholder and will not work. Set it in the portal deployment before sharing this configuration.

Choose your client

Pick the client, copy the configuration and follow the steps.

Copy the configuration

Authorize through the OAuth flow on the first tool call. No API key is required for interactive clients.

MCP URL

https://mcp.plmtrace.example.com/mcp

{
  "type": "remote",
  "url": "https://mcp.plmtrace.example.com/mcp",
  "auth": "oauth2",
  "transport": "https"
}

Set up Codex

Open Codex settings → MCP Servers
Choose Add Remote MCP Server
Enter the PLMTrace HTTPS MCP URL
Authorize through the OAuth flow and verify the tools list

Try a diagnostic in natural language

Describe the problem normally. The MCP client selects the tool and fills in the arguments.

Diagnose AWC unavailability

Analyze why AWC was unavailable in the last two hours. Show the likely layer, the evidence, the coverage and the next safe tests.

Check WebTier logs

Look up WebTier errors and failures in the last 24 hours, limit to 50 events and show the most recent first.

Check SQL Server

Run the SQL Server inventory pack with the default limits and explain any authorization block.

Connection and trust boundary

How clients reach PLMTrace and what is kept.

Endpoint: https://mcp.plmtrace.example.com/mcp
Transport: HTTPS / remote MCP
Identity: OAuth 2.1 + PKCE
Customer payload retention: Transient

Programmatic access

API keys are only for programmatic connections that cannot use OAuth. They are not part of the certified client flow.

Manage API keys