MCP 服务器

Turbo C MCP Server

Gives AI assistants a genuine Borland Turbo C 3.0 toolchain via MCP, enabling compile and run of real 16-bit DOS C programs with diagnostics and classic examples.

README

<a href="https://bbsrguy.github.io/turboc-mcp-server/">🌐 Website</a> · <a href="#-quick-start">🚀 Quick Start</a> · <a href="#-the-toolbox-12-tools">🧰 Tools</a> · <a href="docs/DOSBOX.md">📦 DOSBox Setup</a> · <a href="#-examples">🎮 Examples</a>

💾 What is this?

Turbo C MCP Server hands your AI assistant a genuine Borland Turbo C 3.0 toolchain over the Model Context Protocol. Your LLM doesn't simulate C anymore — it compiles and runs the real thing on the same 16-bit compiler a generation of programmers grew up on, and gets back true output, real Borland diagnostics, and cycle-accurate timing.

Ask Claude to "write a prime sieve in C and run it" — and it actually does, on TCC.EXE. Errors are real. exit 0 is earned.

flowchart LR
    A["🧠 LLM / Claude"] -- MCP stdio --> B["⚙️ turboc-mcp-server"]
    B -- TCC.EXE --> C["📀 Borland Turbo C 3.0"]
    C -- .EXE --> D["🖥️ DOS runtime / DOSBox"]
    D -- stdout · exit code · timing --> B
    B -- structured result --> A
    style A fill:#00c853,stroke:#eafff3,color:#04150d
    style B fill:#0b3d2e,stroke:#00e5ff,color:#eafff3
    style C fill:#ffb300,stroke:#0b0f14,color:#0b0f14
    style D fill:#37474f,stroke:#00e5ff,color:#eafff3

✨ Why it goes further than "run my C"

🛠 It's a studio, not a button

Twelve composable tools: compile-only checks, a static analyzer that runs without a compiler, an error explainer, an assembly disassembler, a benchmark harness, and a self-healing doctor.

🧠 Structured, model-friendly output

Every compile is parsed into error/warning objects with file + line, so your LLM can fix code surgically instead of squinting at raw logs.

</td> <td width="50%" valign="top">

🎮 Batteries + nostalgia included

A built-in library of 12 classic programs — Fibonacci, prime sieve, Towers of Hanoi, BGI graphics, conio colors — exposed as MCP resources.

📦 Runs on modern Windows

16-bit TCC.EXE can't run on 64-bit Windows? The included DOSBox bridge wrappers make compile and run work anywhere. One env var each.

</td> </tr> </table>

🚀 Quick Start

1 · Prerequisites

Node.js ≥ 18
Borland Turbo C 3.0 at C:\TURBOC3 (or set TURBOC_ROOT)
64-bit Windows? Also grab DOSBox → see DOSBox setup

2 · Install & build

git clone https://github.com/BBSRguy/turboc-mcp-server.git
cd turboc-mcp-server
npm install
npm run build

3 · Wire it into your MCP client

<details open> <summary>Claude Desktop — <code>claude_desktop_config.json</code></summary>

{
  "mcpServers": {
    "turboc": {
      "command": "node",
      "args": ["C:/path/to/turboc-mcp-server/build/server.js"],
      "env": {
        "TURBOC_ROOT": "C:\\TURBOC3"
        // On 64-bit Windows, add the DOSBox bridge (see docs/DOSBOX.md):
        // "TCC_COMMAND": "C:\\TURBOC3\\wrappers\\dosbox-tcc.bat",
        // "MCP_C_RUN_COMMAND": "C:\\TURBOC3\\wrappers\\dosbox-run.bat"
      }
    }
  }
}

</details>

<details> <summary>Claude Code — one command</summary>

claude mcp add turboc -- node C:/path/to/turboc-mcp-server/build/server.js

</details>

4 · Say hello

You: "Use turboc to run the hello example." AI: calls run_example → Hello, Turbo C! Compiled on real DOS iron. ✔ exit 0

Not sure it's wired up? Ask it to run environment_doctor — it verifies your whole toolchain and tells you exactly what's missing.

🧰 The toolbox (12 tools)

#	Tool	What it does
1	🟢 `compile_and_run`	Compile with `TCC.EXE` and run the DOS `.EXE`; capture stdout/stderr, exit code, timing, diagnostics
2	🔎 `compile_check`	Compile-only syntax/semantic check — fast, no execution
3	🧪 `analyze_code`	Static analysis without compiling: `gets()`, `scanf` `&`, `=` in `if`, brace balance, missing `main`, `malloc` checks, float-I/O traps
4	📖 `explain_error`	Plain-English cause + fix for any Turbo C compiler / linker / runtime message
5	⚙️ `generate_asm`	Emit the 16-bit x86 assembly listing (`TCC -S`) for any snippet
6	📚 `list_examples`	Browse the classic-program library (filter by category)
7	📄 `get_example`	Fetch the full source of any example
8	▶️ `run_example`	Compile and run an example in one shot
9	⏱️ `benchmark`	Run the program N times; report min / avg / max ms
10	🎨 `format_code`	Re-indent by brace depth, tidy whitespace — zero deps
11	🩺 `environment_doctor`	Verify `TCC`, `INCLUDE`, `LIB`, `BGI`, workspace — with fix hints
12	🧹 `clean_workspace`	Sweep old scratch sessions; keep the N most recent

Plus MCP resources (turboc://environment, turboc://examples/*) and prompts (debug-c-error, optimize-c, explain-program).

🎮 Examples

The bundled library (list_examples) covers every corner of the DOS C world:

Category	Programs
🟩 basics	`hello`, `fibonacci`
🧮 algorithms	`prime-sieve`, `bubble-sort`, `hanoi`, `matrix-multiply`
🎨 graphics	`bgi-graphics` (concentric circles via `EGAVGA.BGI`)
💽 dos	`file-io`, `conio-colors`
🗂 data	`student-records` (structs)
🕹 fun	`pascal-triangle`, `number-guess`

▶  run_example { "id": "prime-sieve" }

Compile: ✓ success  (312 ms, exit 0)
=== Run phase ===
Result: ✓ exit 0  (44 ms)
--- program stdout ---
Primes up to 100:
2 3 5 7 11 13 17 19 23 29 31 37 41 43 47 53 59 61 67 71 73 79 83 89 97

⚙️ Configuration

Everything is environment-driven, so one build works on every setup.

Variable	Default	Purpose
`TURBOC_ROOT`	`C:\TURBOC3`	Turbo C install root
`TCC_COMMAND`	`…\BIN\TCC.EXE`	Compiler entry point (or a DOSBox `.bat`)
`MCP_C_RUN_COMMAND`	(unset)	Wrapper to launch the compiled `.EXE` (DOSBox bridge)
`TURBOC_INCLUDE`	`…\INCLUDE`	Header search path
`TURBOC_LIB`	`…\LIB`	Library search path
`TURBOC_BGI`	`…\BGI`	BGI graphics drivers
`MCP_C_WORKROOT`	`…\mcp_work`	Scratch directory for sessions
`MCP_C_TIMEOUT_MS`	`5000`	Per-run execution timeout
`MCP_C_COMPILE_TIMEOUT_MS`	`10000`	Per-compile timeout
`MCP_C_MAX_OUTPUT_BYTES`	`65536`	Output cap returned to the model

🏗 Architecture

graph TD
    S[server.ts<br/>tools · resources · prompts] --> T[turboc.ts<br/>compile · run · asm · doctor]
    S --> A[analyze.ts<br/>heuristic linter]
    S --> E[errors-db.ts<br/>error knowledge base]
    S --> X[examples.ts<br/>classic programs]
    S --> F[format.ts<br/>C reformatter]
    T --> D[diagnostics.ts<br/>parse TCC output]
    T --> U[util.ts<br/>spawn · timeout · shell bridge]
    T --> C[config.ts<br/>env-driven paths]
    style S fill:#00c853,stroke:#04150d,color:#04150d
    style T fill:#0b3d2e,stroke:#00e5ff,color:#eafff3

Clean, single-responsibility modules — easy to read, easy to extend.

🗺 Roadmap

[ ] Multi-file / project compilation
[ ] BGI graphics → PNG capture via DOSBox screenshots
[ ] Turbo Assembler (TASM) round-trip
[ ] Memory-model presets (tiny/small/large) as first-class options
[ ] npm one-line install (npx turboc-mcp-server)
[ ] Watch mode + hot examples gallery on the website

Ideas welcome — open an issue or PR.

🤝 Contributing

PRs are warmly welcome. Fork → branch → npm run build → PR. New examples and error-DB entries are especially appreciated; see CONTRIBUTING.md.

⭐ Star history

If this brought a little 1992 magic to your AI, drop a ⭐ — it genuinely helps.

👤 Author

BBSRguy · @BBSRguy · rasran90@yahoo.com

Built for everyone who still hears the clrscr() flicker in their dreams. 🕹️