Claude Desktop
Claude Desktop can run tradefloor's local MCP server as a subprocess over stdio. That gives Claude 19 simulation and evaluation tools, such as evaluate_strategies and explain_price_move. With the session tools it can trade step by step in a simulated market the server keeps open. No order reaches a real broker, and the server needs no API key or environment variable.
The connector directory
tradefloor is in Claude's connector directory. In Claude Desktop, find tradefloor there and install it, and Claude Desktop sets up the same local server with no configuration file to edit. Then go on to Check it works. To add the server by hand instead, follow the steps in the next section.
Add the server
Open the Claude menu in the system menu bar, select Settings..., go to the Developer tab and click Edit Config. That opens the configuration file. If the file doesn't exist, Claude Desktop creates it:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json
If you have uv, add tradefloor under mcpServers. uv fetches tradefloor when Claude Desktop starts the server. If the file already lists other servers, add the tradefloor entry next to them.
{
"mcpServers": {
"tradefloor": {
"command": "uvx",
"args": ["--with", "tradefloor[mcp]", "tradefloor", "mcp"]
}
}
}Claude Desktop doesn't start in your shell, so it may not find uvx. If the server doesn't connect, replace "uvx" with the full path that which uvx prints on macOS, or where uvx on Windows. On Windows, write backslashes in a JSON path as \\.
If you installed the package with pip install "tradefloor[mcp]", use the full path to tradefloor-mcp in that environment and leave out args:
{
"mcpServers": {
"tradefloor": {
"command": "/path/to/venv/bin/tradefloor-mcp"
}
}
}Save the file, then quit Claude Desktop completely and open it again. It reads the file and starts the server when it launches.
Check it works
Click the Add files, connectors, and more button at the bottom left of the message box, hover over Connectors and click Manage connectors. Select tradefloor to see its tools.
Then ask Claude to call describe_simulator. Claude asks for your approval before it runs the tool. The result says what the simulator is, what it's measured to reproduce and what it can't do.
If tradefloor isn't listed, check the logs in ~/Library/Logs/Claude on macOS or %APPDATA%\Claude\logs on Windows. mcp.log records connection failures, and mcp-server-tradefloor.log has the server's stderr output.