Flox MCP

What flox-foundation/flox-mcp MCP server does

The flox-foundation/flox-mcp MCP server exposes the FLOX trading framework to AI coding agents through an MCP control plane. It is intended for working with trading strategies, market data, indicators, backtests, and execution workflows from an agent-compatible client.

The package supports the broader FLOX model in which one strategy class can be used for backtesting, paper trading, and live execution. FLOX also provides language bindings for Python, Node.js, Codon, embedded JavaScript, and a C API. The MCP package provides an agent-facing way to discover and use parts of that surface rather than requiring the agent to manually navigate the framework documentation or APIs.

How it works

Install the flox-mcp Python package, then connect it to an MCP-compatible coding client. The server gives the client access to 30 tools covering FLOX-specific development and trading tasks. These include symbol lookups across bindings, strategy scaffolding, indicator and backtest operations, full-text documentation search, lookahead-bias validation, order placement, and PnL queries.

The underlying FLOX framework has a C++23 core and supports multiple strategy-language bindings. Exchange connectivity is provided separately through optional native connectors, including Bybit, Bitget, Hyperliquid, and Polymarket. The provided material does not state that every connector is enabled by the MCP package, so connector availability depends on the FLOX build and setup.

Setup and configuration

Install the server with:

pip install flox-mcp

After installation, configure the package as an MCP server in the client you use for agent development. The repository specifically identifies Cursor, Claude Code, and Cline as supported AI coding-agent environments. The supplied material does not provide a client configuration file, command-line flags, required environment variables, or exchange credential instructions, so those details should be taken from the package README and the relevant FLOX documentation.

The main FLOX project is MIT-licensed. Its documentation also states that the software is provided without warranty and is intended for educational and research purposes; production use and any resulting trading risk remain the operator’s responsibility.

Tools and capabilities

The listed MCP capabilities include:

• Looking up FLOX symbols across supported language bindings.
• Generating starter strategy code.
• Working with indicators and backtests.
• Searching FLOX documentation with full-text queries.
• Checking strategies for lookahead bias.
• Placing orders through available trading workflows.
• Querying profit-and-loss information.

These capabilities make flox-foundation/flox-mcp MCP server relevant for agents that need to move between strategy development, research, validation, and execution-related tasks. It is less suitable if the requirement is a general-purpose market-data server or a standalone exchange connector without the FLOX framework.

Limitations and notes

The server is tied to the FLOX ecosystem and does not replace FLOX’s optional connectors, venue module, or language packages. Native connectors are gated by FLOX build options and are disabled by default in the core project. The supplied material does not document supported exchanges for each MCP operation, authentication handling, paper/live safety controls, or the exact schemas for the 30 tools.

Trading actions can carry financial and operational risk. flox-foundation/flox-mcp MCP server should therefore be evaluated in a controlled research or paper-trading environment before it is used with live execution. FLOX’s own disclaimer places responsibility for production use, trading losses, and system failures on the operator.