Free

FoxKit

Three console tools for Visual FoxPro and its documentation for an agent, in one installer.

vfp2text, foxproof and foxengine, with the VFP 9 runtime inside: for tables and for turning binaries into text you do not need Visual FoxPro installed. Building a project does need it. Since 1.1.0 it also brings vfpdocs, the official VFP 9 documentation for an agent to look up through MCP.

What it brings

vfp2text

Turns VFP binaries (.scx, .vcx, .frx, .lbx, .mnx, .pjx, .dbc, .dbf) into text and back, with FoxBin2Prg. To review changes in git, and so that an agent can read a form.

foxproof

Lists and runs the FoxProof tests of a .prg. Failing tests are a result, with their report, not a failure of the tool.

foxengine

Reads and changes DBF tables (queries, inserts, deletes, indexes, columns), creates and builds projects, and runs VFP code.

vfpdocs

The official Visual FoxPro 9 SP2 help (VFPX's 1.08, under the CC BY 3.0 license) and what VFP Advanced adds, as an offline MCP server: the agent checks the syntax, the parameters and the errors before it writes the code, instead of trusting its memory. The agent uses it through FoxStack; it has no console commands.

In a console

vfp2text bin2prg C:\app\forms\customer.scx
foxproof run --prg tests\CustomerTests.prg
foxengine table-query --path data\customers.dbf --limit 10

Each one explains its commands in its own help, and its describe command gives them all as JSON Schema. The manuals are installed with the kit, in C:\Programas\FoxKit\docs.

With an agent, if you want

You do not need FoxStack to use FoxKit: the three work on their own from the console. FoxStack is what puts them in front of an agent. The installer also puts FoxStack, our local MCP server, on the machine if it is missing or older, and registers the three tools and vfpdocs in it. An agent such as Claude then has them as tools (foxengine_table_query, vfp2text_bin2prg, foxproof_run…) with a single entry in its configuration, which the installer offers to write if it detects Claude Desktop, Cursor or OpenCode. They are sealed with FoxCli MCP, so they are served clean. Whatever runs code (foxengine's eval and exec) only exists if you turn it on.

Want Claude to see these tools through a single MCP entry? Meet FoxStack →

Just the tools

If you do not want FoxStack, the kit installs without it and registers nothing:

FoxKit-Setup-1.1.2.exe /NOSTACK

What it needs

Windows 10 or 11. It installs in C:\Programas\FoxKit and goes on the PATH, so it works from any console. It registers nothing in COM: each tool finds its DLL through its manifest. FoxStack and vfpdocs also need the 32-bit .NET 10 runtime, which the installer offers when it is missing.

The file, in case you want to check it

Digitally signed by:

Irwin Alfredo Rodriguez Gimenez

Version:

1.1.2

Installer · 16.8 MB · SHA-256

5DC73C499E29736A3EDE9EFB6158C190C7C506208E2F6E52754284215D108B37

If something does not add up, write to me: soporte@irwinrodriguez.dev