Claude Desktop

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, and creates it if it doesn't exist:

macOS:   ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json

With uv installed, add tradefloor under mcpServers. uv fetches tradefloor when Claude Desktop starts the server. If the file already lists other servers, add the tradefloor entry beside 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, quit Claude Desktop completely and open it again. It reads the file and starts the server on launch.

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 is measured to reproduce and what it can't do.

If tradefloor isn't listed, check the log files. On macOS they are in ~/Library/Logs/Claude, and on Windows in %APPDATA%\Claude\logs. mcp.log records connection failures, and mcp-server-tradefloor.log has the server's stderr output.