IR
irwinrodriguez.dev
ES EN DE
CM Perpetual license · One-time payment

Your FoxCli CLI works in the console, and you want Claude to use it without having to explain the command line.

The same Visual FoxPro CLI, as tools for Claude.

You build as always and <cli>.mcp.exe shows up in dist\. You add one line to the agent's configuration, and Claude discovers your commands and calls them. You write no new code, and the logic runs on the agent's machine.

Who it is for
  • Anyone who already has a CLI built with FoxCli
  • Claude Code and Claude Desktop
  • Read-only commands, with @readonly
Buy license Try free for 30 days

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.

Features

No new code

The commands, their parameters and their descriptions are the ones you already wrote in the *!* blocks. The code that runs is your CLI's own main.prg.

The agent discovers and calls

When it connects, the agent gets every command with its description and its parameters as JSON Schema, the same ones describe gives. Nobody has to explain your command line to it.

@readonly

One line in the block of a command that only looks, and the agent knows: a client that honors the mark lets it run without asking you every time. The ones that write still ask.

One process for the whole session

The server starts once and handles the calls in order. After each one, the failed ones too, FoxCli closes whatever the command left open with AfterCommand.

Errors like in the console

A VFP error reaches the agent with its message, file and line, just as you would see it in the console. Never a dialog waiting for somebody.

Installed with FoxCli

It comes with FoxForge 0.4.0 or later. On the agent's machine it only needs the 32-bit .NET 10 runtime, which the FoxCli installer offers to download.

How it works

  1. 1
    Build as always

    Ctrl+F7 in your FoxCli project. In dist\ you have your CLI and, next to it, its MCP server, and pack.ps1 puts both in the zip.

  2. 2
    One line in the configuration

    In Claude Code's .mcp.json or in Claude Desktop's configuration, your CLI's name and the path to its .mcp.exe. There is nothing else to configure.

  3. 3
    Ask the agent for something

    “Put the customers in a CSV”: the agent finds the command, fills in its parameters, runs it and tells you the result.

Pricing

The programmer is licensed, as with FoxCli, and it requires FoxCli. One-time payment with 12 months of new versions, then 15 € a year if you want to keep getting them. The MCP servers you build are yours to hand out, free and without limit.

1 seat
99 €
1 programmer, on their machine
Optional renewal: 15 € a year
Buy
MOST POPULAR
4 seats
149 €
Up to 4 programmers
Optional renewal: 15 € a year
Buy
8 seats
199 €
Up to 8 programmers
Optional renewal: 15 € a year
Buy

FoxCli + FoxCli MCP, both together

If you do not have FoxCli yet, take both for 20 % less than separately. It is one purchase and two licenses, with the four downloads in My licenses. The tiers are the same, and the 1-seat tier binds both licenses to the same machine. What FoxCli is.

1 seat
238 €
Optional renewal: 40 € a year
Buy both
4 seats
358 €
Optional renewal: 40 € a year
Buy both
8 seats
478 €
Optional renewal: 40 € a year
Buy both

No patron discount: the bundle already is the discount.

Frequently asked questions

Which is which: FoxAgent, FoxCli MCP or FoxServer?
All three speak MCP and each one is for something else. FoxAgent connects an agent to an open VFP application: it sees its forms, its data and its state while you use it. FoxCli MCP is your VFP logic, packaged as tools, on the same machine as the agent. FoxServer puts your VFP logic on a server, so it can be called from another machine.
Do I need FoxCli?
Yes. FoxCli MCP is the MCP server of the CLIs you make with FoxCli, and FoxForge 0.4.0 or later builds it next to each one. Without the FoxCli license the CLI comes out in evaluation, and without the FoxCli MCP one, its server. If you do not have it, the bundle above brings both.
What happens if I build without a license?
It works the same, with no expiry date. The difference is that every answer to the agent ends with a line saying it was built with FoxCli MCP in evaluation, and the server also tells the agent when it connects. With the license, the line goes away and the server says who it is licensed to.
What does the license do, then?
With it, FoxForge seals the MCP server of every CLI it builds with your name. It is two files, foxcli-mcp.lic and foxcli-mcp.seal, loaded in FoxForge > FoxCli license. If you have the FoxCli ones in the same folder, they load together.
What does the agent's machine need?
Windows 10 or 11 and the 32-bit .NET 10 runtime, which the FoxCli installer looks for and, if it is missing, offers to download from Microsoft. No Visual FoxPro needed.
And to program?
Visual FoxPro 9 or VFP Advanced, and FoxForge 0.4.0 or later, which is installed with FoxCli. The 1-seat license is bound to the machine where you program; the 4 and 8 seat ones are company licenses, bound to no machine.
What happens when maintenance ends?
What you already built stays sealed for good. What you lose is the right to FoxCli MCP versions released afterwards: if you build with a later one, those servers come out in evaluation until you renew.
Is there a tutorial?
Yes: Your CLI, served to an agent takes the CLI from the first FoxCli tutorial and hands it to Claude, from the build to the first request.

Does your CLI already do something you would ask an agent for?

Try it for 30 days with the full license, or without a license and without a date: the server works the same.

Buy now