@backtest Kit MCP

What @backtest-kit/mcp MCP server does

@backtest-kit/mcp MCP server connects an LLM agent to the live trading portfolio managed through backtest-kit. Its stated purpose is to let the agent observe portfolio state and perform position actions through guarded tools.

This places the package in the 💰 Finance & Fintech category. It is relevant when an AI workflow needs awareness of an active trading account and a constrained way to request position changes, rather than only producing analysis or signals.

The underlying backtest-kit project is a Node.js trading engine intended for backtesting, paper trading, and live trading. The MCP listing specifically describes the server in terms of the live portfolio and position operations; the supplied material does not document the complete set of data exposed to an agent.

Tools and capabilities

The documented capabilities are:

• Observe the live trading portfolio.
• Open positions through guarded tools.
• Close positions through guarded tools.

The word “guarded” indicates that opening and closing are not presented as unrestricted agent actions. However, the available documentation does not explain the guard conditions, approval model, validation rules, supported order parameters, or error responses. It also does not provide exact MCP tool names or schemas, so those details should be checked in the package or its implementation before integration.

How it works

An LLM agent communicates with the MCP server and uses its exposed tools to request portfolio observation or position actions. The server acts as the MCP-facing layer for backtest-kit rather than as a separate strategy engine described in the supplied listing.

The backtest-kit project supports a shared trading engine across backtest, paper, and live modes, but the provided MCP information only establishes the live-portfolio use case. It does not state whether the MCP server can start backtests, read historical candles, submit orders to a particular exchange, or manage strategies directly.

Limitations and notes

@backtest-kit/mcp MCP server should be evaluated against the required execution and safety model before it is connected to a live account. The available material does not specify installation steps, configuration variables, supported MCP clients, transport type, authentication, exchange integrations, or the exact safeguards applied to position changes.

The server is therefore best treated as an interface for the three documented capabilities: viewing the live portfolio, opening positions, and closing positions. Confirm the tool schemas and operational protections from the repository before allowing an agent to perform live trading actions.

For developers comparing entries in the 💰 Finance & Fintech category, the key fit question is whether guarded portfolio access is sufficient. No evidence in the supplied material supports assuming broader account administration, market-data access, automated strategy execution, or client-specific compatibility.