T-FLEX CAD 17 MCP
Read-only MCP server providing search and retrieval of T-FLEX CAD 17 API symbols, documentation, and capabilities via a static API layer.
README
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
| Tool | Purpose |
|---|---|
tflex_manifest |
Return the dataset and graph manifests. |
tflex_search_symbols |
Search API symbols with optional assembly and kind filters. |
tflex_get_symbol |
Resolve an exact symbol identifier/name, then fall back to the best match. |
tflex_search_docs |
Search normalized CHM/help topic records. |
tflex_search_capabilities |
Search the curated capability-to-symbol/topic seed. |
tflex_get_document |
Read an allowlisted Markdown, CHM mirror, XML API, graph or manifest file. |
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/healthzhealth check.railway.toml— Railway Docker deployment with/healthzhealth check and restart policy.compose.yaml— VPS/on-premises Docker Compose deployment..github/workflows/container.yml— publishesghcr.io/krickmanc/t-flex-cad-17-mcp:latestand 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
| Variable | Default | Meaning |
|---|---|---|
TFLEX_API_BASE_URL |
raw T-FLEX-CAD-17-API/main |
Canonical read-only upstream. |
TFLEX_FETCH_TIMEOUT_MS |
45000 |
Upstream request timeout. |
TFLEX_CACHE_TTL_MS |
300000 |
In-memory dataset cache lifetime. |
TFLEX_MAX_DATASET_BYTES |
67108864 |
Maximum index response size. |
TFLEX_MAX_DOCUMENT_BYTES |
2097152 |
Maximum single document size. |
MCP_MAX_TOOL_OUTPUT_CHARS |
120000 |
Maximum serialized tool result. |
MCP_HOST |
0.0.0.0 |
HTTP bind address. |
MCP_PORT |
3000 |
HTTP port. |
PORT |
unset | Hosting-platform port fallback. |
MCP_ALLOWED_ORIGINS |
* |
Comma-separated CORS origins. |
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
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.
E2B
Using MCP to run code via e2b.