T-FLEX CAD 17 MCP

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

Deployment boundary: GitHub Pages is static hosting and cannot execute the Node.js MCP process. This repository therefore deploys a Pages documentation/diagnostics site, while the MCP runtime is started through stdio, Node.js HTTP, or Docker. The source dataset remains unchanged in T-FLEX-CAD-17-API.

Architecture

flowchart LR
    C[MCP client / AI agent]
    M[T-FLEX-CAD-17-MCP\nstdio or Streamable HTTP]
    A[T-FLEX-CAD-17-API\nGitHub Pages: JSONL, Markdown, XML]
    P[T-FLEX-CAD-17-MCP Pages\ndocs and diagnostics]

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

The MCP server never modifies the API repository and does not accept arbitrary upstream URLs. It reads only the configured base URL and allowlisted documentation paths.

Related MCP server: SolidworksMCP

MCP tools

All tools are declared read-only and idempotent.

Requirements

• Node.js 20.11 or newer; CI uses Node.js 22.

• Network access to the static API layer: https://krickmanc.github.io/T-FLEX-CAD-17-API/.

Local stdio server

npm install
npm run start:stdio

Example MCP client configuration:

{
  "mcpServers": {
    "t-flex-cad-17": {
      "command": "node",
      "args": ["/absolute/path/T-FLEX-CAD-17-MCP/src/stdio.js"],
      "env": {
        "TFLEX_API_BASE_URL": "https://krickmanc.github.io/T-FLEX-CAD-17-API/"
      }
    }
  }
}

Streamable HTTP server

npm install
npm start

Default endpoints:

• MCP: POST/GET/DELETE http://localhost:3000/mcp

• Liveness: GET http://localhost:3000/healthz

• Upstream readiness: GET http://localhost:3000/readyz

• Service metadata: GET http://localhost:3000/

The HTTP implementation maintains MCP sessions in process memory. For horizontal scaling, use sticky sessions or a single replica unless a shared session store is added.

Docker

docker build -t t-flex-cad-17-mcp .
docker run --rm -p 3000:3000 \
  -e TFLEX_API_BASE_URL=https://krickmanc.github.io/T-FLEX-CAD-17-API/ \
  t-flex-cad-17-mcp

Configuration

Verification

npm run check       # JavaScript syntax
npm test            # client, stdio MCP and Streamable HTTP MCP tests
npm run smoke:live  # live manifest, graph, capability and symbol index checks

CI performs all three checks and builds the Docker image. The protocol tests execute tools/list and tools/call over both standard transports against a deterministic fixture API.

GitHub Pages

The Deploy GitHub Pages workflow publishes the site/ directory. The page checks the live API and graph manifests in the browser and can probe /healthz and /readyz on a separately deployed MCP runtime.

Dataset currently expected from the API layer

The canonical manifest generated on 2026-08-17 reports:

• 17 assemblies

• 2,452 types

• 17,929 symbols

• 19,350 CHM/help pages

• 21,558 graph nodes

• 45,821 graph edges

These values are verified dynamically by the live smoke test rather than embedded into server behavior.