IR
irwinrodriguez.dev
ES EN DE

Free

FoxStack

All your Visual FoxPro tools, for an agent, in one MCP server.

You have several tools for your agent and do not want to set up one MCP server for each. FoxStack is the MCP entry for all of them: every product you install registers in it as a provider, and the agent sees one server with the tools of all of them.

Download for free

for Windows · no account needed · 2.3 MB · v1.1.1

One MCP entry instead of many

Without FoxStack
Claude
  • FoxKit one entry
  • VFP.MCP one entry
  • FoxPack one entry
  • FoxCli one entry
  • FoxService one entry
  • FoxServer one entry
  • other MCP one entry

One entry per tool in the agent's configuration, and one more every time you install something.

With FoxStack
Claude
one entry
FoxStack
FoxKitVFP.MCPFoxPackFoxCliFoxServiceFoxServerother MCP

A single entry. Whatever you install later shows up on its own, and stack_info tells the agent what this machine has.

It does not replace your tools: it brings them together

FoxKit, FoxPack, FoxCli and FoxServer work on their own from the console, without FoxStack. Each one registers its tools in it so that an agent sees them through a single MCP entry. And there is no need to download it separately: these installers put FoxStack on the machine if it is missing or older.

FoxKit
vfp2text, foxproof and foxengine: binaries to text, tests and DBF tables. VFP.MCP comes inside. Free.
VFP.MCP
The official VFP 9 SP2 documentation and what VFP Advanced adds, offline: the agent checks the syntax, the parameters and the errors before it writes the code, instead of trusting its memory. Its tools show up as vfpdocs__lookup, vfpdocs__search and the rest. It comes with FoxKit. Free.
FoxPack
VFP libraries from GitHub at a fixed version. Free.
FoxCli
Creates and builds console applications written in VFP.
FoxService
Creates, builds and installs Windows services written in VFP. It comes with FoxCli.
FoxServer
REST APIs in VFP: projects, endpoints and validation.

What it publishes

This is how another MCP server goes behind FoxStack. foxstack doctor starts it and says whether it answers:

foxstack register --kind mcp --id dbf --family vfp -- C:\tools\dbf.mcp.exe --readonly

Running code is your call

Whatever lets the agent run code or launch a program (foxengine's eval and exec, or choosing which vfp9.exe is used) does not exist in the session unless you turn it on. You turn it on like this, in your .mcp.json:

.mcp.json
{
  "mcpServers": {
    "foxstack": {
      "command": "C:\\Programas\\FoxStack\\foxstack.exe",
      "args": ["--allow-execution"]
    }
  }
}

foxstack setup writes it for you if you add --allow-execution.

Connecting it to your AI client

The installer detects Claude Desktop, Cursor and OpenCode and offers to connect them. To do it later, or with Claude Code, which works per project, there are these commands: foxstack setup tells which clients this machine has, and foxstack setup followed by the client (claude-code, claude-desktop, cursor or opencode) writes the FoxStack entry in its configuration with the full path of the executable, leaving the other entries alone:

foxstack setup
foxstack setup claude-desktop
foxstack setup claude-code

Restart the client so that it reads its configuration, and ask it to call stack_info.

From the console

foxstack is also a console command: it lists the providers, says what is wrong and how to fix it, and registers a CLI of your own built with FoxCli.

foxstack list
foxstack doctor
foxstack register C:\tools\mycli.exe --family stack

FoxStack and FoxCli MCP: what each one does

FoxCli MCP

Turns one specific CLI, built with FoxCli, into MCP tools.

Your CLI → FoxCli MCP → agent

FoxStack

Brings many tools and servers together behind a single MCP entry.

FoxKit, FoxPack, FoxCli, FoxServer → FoxStack → agent

They complement each other. A CLI built with a FoxCli MCP license is served clean under FoxStack; one without it works the same and carries an evaluation note in its results. The FoxKit and FoxPack tools are sealed.

What FoxCli MCP is →

Questions

Do I need FoxStack to use FoxKit?

No. The three FoxKit tools work on their own from the console, and its installer accepts /NOSTACK so that it neither installs FoxStack nor registers anything.

And to use FoxPack?

Neither. From the console FoxPack does not need it; FoxStack only puts its commands in front of an agent.

How is it different from FoxCli MCP?

FoxCli MCP turns a CLI of yours into MCP tools. FoxStack brings that CLI together with all the others behind a single entry. You can use one, the other or both.

Does the agent know VFP syntax?

It looks it up. VFP has many similar commands, and an agent mixes up clauses, parameter order and defaults. With VFP.MCP, which comes in FoxKit, it reads the official VFP 9 documentation before it writes the code, offline and with notes tested on VFP 9 and VFP Advanced.

Does FoxStack replace my tools?

No. Each one is still its own program, with its console and its help. FoxStack publishes them for the agent.

Can I put another MCP server behind it?

Yes. Any MCP server over stdio, with foxstack register --kind mcp. Its tools show up under its prefix.

Can the agent run VFP code?

Only if you turn it on. Without --allow-execution, foxengine's eval and exec, and the option to choose which vfp9.exe is used, do not exist in the session.

How do I turn execution on?

With --allow-execution in the args of the foxstack entry of your .mcp.json, as in the example above, or with foxstack setup <client> --allow-execution.

Can I use FoxStack without Claude?

Yes. It is an MCP server over stdio: any MCP client can use it. foxstack setup knows Claude Code, Claude Desktop, Cursor and OpenCode, and writes their entry.

What if I have many tools installed?

Each project picks its own: foxstack setup claude-code --only foxengine,vfpdocs leaves only those in its .mcp.json, and --exclude drops the ones it does not need. What is left out is neither published nor started, and stack_info says how much the published part weighs.

What it needs

Windows 10 or 11 and the 32-bit .NET 10 runtime, which the installer offers when it is missing. It installs in C:\Programas\FoxStack and goes on the PATH.

The file, in case you want to check it

Digitally signed by:
Irwin Alfredo Rodriguez Gimenez
Version:
1.1.1
Installer · 2.3 MB · SHA-256
33D8F76B6D244B25A4E694CF0BCF0EB852130CEC8EFD5D22E57D1925171DCC9F

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