Platform Insights

Deployment facts and release evidence, with sources and observation times.

Preview · shared access pending validation

Open environment status and release notes in Confluence →

Connect Claude web or Desktop

1. Open Customize → Connectors and add the approved MCP URL ending in /mcp.
2. Choose sign-in and “Use your own OAuth client.” Use the client ID supplied by the ALE administrator.
3. Sign in with your approved ALE account. Ask: “Compare QA and Production and show any stale or missing evidence.”

Connect Claude Code

MCP endpoint: https://insights.dev.aletechnologies.com/mcp

Claude Code registration (public client; no secret):

claude mcp add-json ale-insights '{"type":"http","url":"https://insights.dev.aletechnologies.com/mcp","oauth":{"clientId":"080910df-0f83-48c7-925f-e007965a7a3e","callbackPort":38123,"authServerMetadataUrl":"https://login.microsoftonline.com/897e7aa5-19e3-4748-ae54-e713ed2449a7/v2.0/.well-known/openid-configuration","scopes":"https://insights.dev.aletechnologies.com/mcp/DeploymentStatus.Read offline_access"}}'
claude mcp login ale-insights

Add an HTTP MCP server using the approved URL and pre-registered client ID. Use the fixed callback port supplied with the registration, then run claude mcp login ale-insights. A public OAuth client does not need a client secret.

Claude Code connection guide · Claude connector guide

Read the evidence

Home Health runs on AWS. Connect web services and integration jobs run on Azure. Their release procedures differ. Ask for release procedure context before interpreting a version or release branch.

Responses identify cached observations, collection time, missing sources, and stale data. Configured images do not prove a job executed. Deployment does not establish QA acceptance or release approval.