Point Claude Code, Cursor, Codex, or any coding agent at your local install, over MCP or the CLI, and ask about your positions, your P&L, your risk. Optional, and off by default.
Connect it
The casu CLI registers itself with your agent. Swap claude for cursor or codex, then restart the agent so the tools appear.
Windows (run in Command Prompt):
>%LOCALAPPDATA%\Casu\current\bin\casu.cmd connect claude
Mac:
>~/.casu/current/bin/casu connect claude
Undo is the same command with disconnect. It removes casu from that agent’s config and touches nothing else. And connected or not, quitting Casu is the kill switch: every tool talks to your local engine, so when the engine is off an agent can neither see nor touch anything.
Any other agent
Paste this prompt instead. It teaches the agent where casu lives, how to verify the hookup, and what the ground rules are. Anything that can run a shell command can use the CLI directly, and every command supports --json.
>You now have access to Casu, a trading terminal for 15-minute
prediction markets, running locally on this machine.
The casu command lives at:
Windows: %LOCALAPPDATA%\Casu\current\bin\casu.cmd
macOS: ~/.casu/current/bin/casu
Set it up:
1. Run "casu status" (use the full path). If the engine is not reachable,
stop and ask me to start Casu first.
2. If you are Claude Code, Cursor, or Codex, run "casu connect claude"
(or cursor / codex) with the full path. It registers casu as an MCP
server in your own config. Undo later with "casu disconnect <agent>".
Any other MCP host: the server command is the same casu binary with
the single argument "mcp" (stdio transport). On Windows, wrap it as:
cmd /c "<path-to-casu.cmd>" mcp. MCP hosts spawn without a shell,
so the .cmd needs cmd.exe and %LOCALAPPDATA% needs expanding.
If you don't support MCP, call the CLI directly; every command
supports --json.
3. Run "casu --help" to see what you can do.
Ground rules:
- You can read everything: status, positions, orders, P&L, markets, odds.
- You can reduce risk: close, flatten, cancel, protect (set take-profit
and stop-loss on positions I already hold).
- Opening NEW positions is disabled unless I have explicitly opted in,
and the engine enforces my license and daily loss limit no matter
what you do.
- Never try to change trading environments, credentials, or licensing -
those live in the Casu app, not in your hands.
Or write the config by hand
Claude Code
Windows (run in Command Prompt, or replace the path by hand):
>claude mcp add casu -- cmd /c "%LOCALAPPDATA%\Casu\current\bin\casu.cmd" mcp
Mac:
>claude mcp add casu -- ~/.casu/current/bin/casu mcp
To remove it by hand: claude mcp remove casu for Claude Code, delete the "casu" entry from Cursor’s mcp.json, delete the [mcp_servers.casu] block from Codex’s config.toml. An agent that only got the setup prompt has nothing persistent to remove.
Letting an agent open positions
Off by default, on purpose. If you want your agent to be able to place entries, start the MCP server (or run the CLI) with the environment variable CASU_AGENT_TRADING=1. Before you do: set a daily loss limit in Casu first. The limit lives in the engine, so it binds the agent exactly as it binds you.
Your agent’s orders are your orders. Same account, same money, same losses. Anything the agent reads, including market text, is input that can steer it, so treat an order-placing agent like a fast intern with your car keys. Casu enforces your limits; it does not supervise your agent’s judgment.