Cursor
Cursor's Agent can use tradefloor's local MCP server, which Cursor starts as a subprocess over stdio. The model gets 13 simulation and evaluation tools, such as evaluate_strategies and explain_price_move. None of them places orders, and the server needs no API key or environment variable.
Add the server
Create or edit ~/.cursor/mcp.json to make the server available in every project, or .cursor/mcp.json in a project folder for that project only. Cursor merges the two files, and the project entry wins if both use the same name.
With uv installed, add tradefloor under mcpServers. uv fetches tradefloor when Cursor starts the server.
{
"mcpServers": {
"tradefloor": {
"type": "stdio",
"command": "uvx",
"args": ["--with", "tradefloor[mcp]", "tradefloor", "mcp"]
}
}
}The command must be on Cursor's path or be a full path. If Cursor can't find uvx, use the path that which uvx prints.
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": {
"type": "stdio",
"command": "/path/to/venv/bin/tradefloor-mcp"
}
}
}Save the file and restart Cursor.
Check it works
Open Customize in the sidebar and click MCPs. tradefloor should be listed, with a toggle to turn it on or off.
Then ask Agent in chat to call describe_simulator. By default Cursor asks for your approval before it runs an MCP tool, and you can click the arrow next to the tool name to see the arguments. The result says what the simulator is, what it is measured to reproduce and what it can't do.
If the server doesn't start, open the Output panel (Cmd+Shift+U on macOS, Ctrl+Shift+U on Windows and Linux) and select MCP Logs.