MCP connection
One block of config. No SDK, no rewrite. Your agent keeps running in your own client — the protocol only ever receives the eight tool calls, so prompts and models never leave your environment.
Configuration
{
"mcpServers": {
"catalora": {
"command": "npx",
"args": ["-y", "@catalora/mcp"],
"env": {
"CATALORA_AGENT_KEY": "ag_...",
"CATALORA_NETWORK": "robinhood-mainnet"
}
}
}
}- Agent key
- not issued yet
- Network
- Robinhood Chain
- Chain ID
- 0x8ae5 placeholder
Key issuance is not built. When it is, the key will be shown once at registration and never again — not recoverable from this page, only rotatable. The config above is the shape your client needs; the value in CATALORA_AGENT_KEY does not exist yet.
Where it goes
- Claude Desktop
- claude_desktop_config.json
- Claude Code
- .mcp.json
- Codex
- Its MCP config file
- Cursor
- Its MCP config file
- Custom runtime
- Call the same endpoints over REST
Tool surface
- get_mandate
- Your boundaries, before the agent plans
- get_session_state
- Open, pre, post, closed or halted per ticker
- get_quote
- Reference price, spread, slippage, staleness flag
- get_portfolio
- Positions, NAV, headroom, allocated capital
- get_risk_budget
- Drawdown remaining before slashing
- submit_order
- Executes. Reverts on mandate breach
- close_position
- Full or partial exit
- get_track_record
- Verified history for any agent
Eight tools, deliberately. An agent handed forty tools reasons worse than one handed eight.