FoxAgent
FoxAgent is a local MCP server that lets an AI agent (Claude Desktop, Claude Code or any MCP client) look inside your Visual FoxPro application while it runs: read variables and cursors, see the form on screen, drive it the way the user would, and call business functions you wrote yourself in plain VFP. Your application registers with a local Broker and declares in its own code how far the agent reaches.
No credit card. Verify your email and you get 30 days of a full license (not a cut-down build) for FoxServer, FoxCore, FoxBridge, FoxAgent, FoxCli and FoxCli MCP, installer included, in your portal. One per person and product; after 30 days it expires. With FoxAgent, once the trial expires the Broker still starts: it falls back to the evaluation limits (1 instance and 1 custom tool, with all 55 built-ins uncut) and prints your machineId so you can buy. Nothing has to be deleted, and that mode also works without signing up.
In this section
- Installation: Download, installation and license activation.
- Quick Start: The Broker, the three integration lines and the MCP client.
- Configuration: Custom tools (UDTs), the four role rungs and the license.
What it does
- Registers your VFP instance with the local Broker, with automatic heartbeat and expiry of dead ones
- Live inspection: variables, cursors, data sessions, forms and controls, without pausing the application or stealing the user's focus
- Drives the interface through its own path: clicking, typing, sending keys and refreshing, with your validation and your permissions still in charge
- Custom tools (UDTs): VFP classes you register explicitly with
RegisterTool(). Nothing is scanned from disk, and that is the security model - 55 built-in tools, spread over four role rungs that your application declares in
Connect() - License validated locally, with no telemetry: Developer per development machine, Runtime per company for software houses
AI clients
FoxAgent speaks MCP, which is an open standard. The installer configures Claude Desktop and OpenCode if it finds them, and leaves the block ready to paste into any other. You need one: without an MCP client there is no agent.
Architecture
Three pieces. The Bridge is a COM DLL on .NET Framework 4.8 that lives inside your VFP process. The Broker is a Windows service that keeps the registry of connected instances. The McpHost is the one that speaks MCP to your AI client, over stdio. Broker and McpHost are self-contained binaries: they carry their runtime inside and nothing else has to be installed.
localhost:7400 only. There are no external servers, no ports open to the network and no telemetry. The license is validated locally against a public key embedded in the binary. If what you want is to reach a customer's machine, that is Golem, which is a different product. Requirements
| Component | Requirement |
|---|---|
| Operating system | Windows 10 or 11 (x64), or Windows Server 2016 or later |
| Visual FoxPro | VFP 9 SP2 or VFP Advanced 10 or later for development. On the customer's machine the VFP runtime you already ship is enough |
| .NET Framework 4.8 | Needed by the Bridge because it is COM. It is the only external one, and the only thing the installer checks |
| Broker and McpHost | Nothing to install: they are self-contained and carry .NET 10 inside |
| MCP client | Claude Desktop, Claude Code, Cursor, OpenCode or any other that speaks MCP |