T-FLEX CAD 17 MCP

Read-only Model Context Protocol server over the canonical T-FLEX-CAD-17-API knowledge/API layer.

GitHub Pages publishes only the static project dashboard. The executable MCP runtime is the Node.js/Docker service from this repository and must run on a compute host.

Architecture

flowchart LR
    C[MCP client / AI agent]
    M[T-FLEX-CAD-17-MCP\nstdio or Streamable HTTP]
    A[T-FLEX-CAD-17-API\nraw GitHub content]
    P[T-FLEX-CAD-17-MCP Pages\ndocs and diagnostics]

    C -->|MCP tools| M
    M -->|read-only HTTPS| A
    P -->|manifest diagnostics| A
    P -.->|health/readiness check| M

The runtime never modifies T-FLEX-CAD-17-API. It reads only the configured upstream base URL and allowlisted documentation paths.

MCP tools

All tools are declared read-only and idempotent.

Runtime endpoints

When npm start or the Docker image is running:

• MCP: POST/GET/DELETE /mcp

• Liveness: GET /healthz

• Upstream readiness: GET /readyz

• Service metadata: GET /

The HTTP transport maintains MCP sessions in process memory and returns MCP-Session-Id after initialization.

Local stdio

npm install
npm run start:stdio

Example client configuration:

{
  "mcpServers": {
    "t-flex-cad-17": {
      "command": "node",
      "args": ["/absolute/path/T-FLEX-CAD-17-MCP/src/stdio.js"]
    }
  }
}

Local Streamable HTTP

npm install
npm start

Default endpoint:

http://localhost:3000/mcp

The runtime also accepts platform-provided PORT; MCP_PORT takes precedence.

Docker

docker build -t t-flex-cad-17-mcp .
docker run --rm -p 3000:3000 t-flex-cad-17-mcp

Or:

docker compose up -d --build

Deploy to a public runtime

Deployment descriptors are included in the repository:

• render.yaml — Render Blueprint using the Docker runtime and /healthz health check.

• railway.toml — Railway Docker deployment with /healthz health check and restart policy.

• compose.yaml — VPS/on-premises Docker Compose deployment.

• .github/workflows/container.yml — publishes ghcr.io/krickmanc/t-flex-cad-17-mcp:latest and an immutable SHA tag.

After deployment, point the MCP client to:

https://<runtime-host>/mcp

The GitHub Pages address is not the MCP endpoint.

Configuration

Verification

npm run check
npm test
npm run smoke:live

CI checks JavaScript syntax, stdio MCP, Streamable HTTP MCP, the live knowledge/API layer, and the Docker image.

GitHub Pages

Deploy GitHub Pages publishes the site/ directory. The page reads the live manifests directly from T-FLEX-CAD-17-API and can probe /healthz and /readyz of a separately deployed runtime.

Current canonical dataset

The current T-FLEX-CAD-17-API manifests report:

• 4 API assemblies

• 2,452 generated type pages

• 17,929 symbols

• 19,350 CHM/help pages

• 38,051 graph nodes

• 51,105 graph edges