# Cursor

Source: https://docs.tradefloor.dev/cursor.html

> Add tradefloor's local MCP server to Cursor through mcp.json, globally or for one project, then check that Agent can call its 22 tools.

Cursor's Agent can use tradefloor's [local MCP server](https://docs.tradefloor.dev/mcp-local.html). Cursor runs the server as a subprocess over stdio. That gives the model 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.

## 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. If both use the same name, the project entry wins.

If you have [uv](https://docs.astral.sh/uv/), 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. Click the arrow next to the tool name to see the arguments. The result says what the simulator is, what it's 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.
