# C16 Developer Tools

Developer tools I built for vectorsoft’s conzept 16: a c16-cli, Git for local procedure versions, an MCP server for AI assistants, and a debugger solution developed through reverse engineering.

Classification: OWNER_BUILT_PRIVATE

Stack: conzept 16, c16-cli, MCP, TypeScript, PowerShell, VS Code, Git, Reverse Engineering

## My contribution

I built developer tools for my work with conzept 16: the c16-cli, an MCP server, Git integration for local procedure versions and a debugger solution based on reverse engineering. The tools connect the specialist C16 environment to VS Code, scripts and AI assistants.

## Problem

An established C16 application contains substantial domain knowledge. That knowledge remains valuable as software development tools change. I wanted to edit procedures in a modern editor, compare changes in Git and give AI assistants access to concrete development functions through MCP. I extended access to the existing environment so that improving everyday development did not require rewriting the application.

## Workflow

1. Read C16 procedures through the custom CLI
2. Edit local working copies in VS Code
3. Compare and version changes with Git
4. Write back, compile and debug procedures
5. Use development functions as MCP tools

## Engineering

### A custom CLI for access to C16

The c16-cli exposes C16 functions to scripts. Procedures can be read, edited as local files, written back and compiled. The documented implementation also handles text encoding and structured results. Individual manual operations become repeatable workflows that other tools can invoke. The CLI is a separate component and remains useful outside an AI chat.

### Work with procedures in Git

Local procedure copies make changes visible to Git. Diffs show what changed, while history and checkpoints preserve earlier versions. The VS Code integration connects this view to opening, comparing, uploading and compiling procedures. A local commit and a version actually written back to C16 remain distinct states, an important distinction when working on an existing application.

### Add a debugger and MCP

I used reverse engineering to build the debugger solution. Editor integration includes connecting the debugger and function breakpoints. Alongside it, the MCP server exposes development functions as tools for AI assistants. An assistant can access the procedure and diagnostic functions also used by people and scripts. Read-only access and actions that change the application are handled separately.

## Decisions

- Keep the existing application and extend its developer tools. Preserve domain logic while changing how development is done.
- Design CLI, editor and MCP as connected entry points so people, scripts and AI assistants can use the same functions.
- Distinguish the local version, the procedure written back and the compiler result. Git records a change; it does not replace checking it in the target environment.

## Evidence and boundaries

- The owner confirmed the custom CLI, Git/MCP integration and debugger solution for this public description on 26 October 2026.
- Local tool documentation describes procedure access, compilation, Git history, editor commands and function breakpoints.
- An existing integration report records an MCP handshake and a non-mutating tool call.

This case study describes my own tools. It includes no employer or customer code and publishes neither connection details nor private procedures. It does not claim an official partnership with vectorsoft or compatibility with every C16 version.

[conzept 16 · vectorsoft](https://conzept16.vectorsoft.de/docs/)

https://docs.mk1.rocks/en/references/c16-developer-tooling/

Marvin Kamp · 25.10.2026