pineforge-4pass/pineforge-codegen-mcp

Self-contained stdio MCP server: an AI agent writes PineScript v6, and the
bundled pineforge-release image transpiles it to C++ and backtests it against
an OHLCV CSV (your own, or one fetched from Binance's public API) — all in one
container, in-process. **Fully local** — the image bundles the
pineforge-codegen
transpiler, so Pine → C++ → backtest run with no host Docker daemon. **No API
key.** Your strategy source and CSVs never leave the machine; only the Binance
tools, and check_tradingview_parity when you pass no bars, make outbound requests
(public endpoints).
Tools
| name | runs on | purpose |
| ---------------------- | -------------------- | ------------------------------------------------------------------------ |
| transpile_pine | in-process | Pine v6 → C++ translation unit (transpile-only) |
| list_engine_params | local (no I/O) | Catalog of every overrides + runtime knob accepted by the backtests |
| backtest_pine | in-process | Single backtest of a Pine source against an OHLCV CSV |
| backtest_pine_grid | in-process | Cartesian sweep of inputs × overrides: one transpile, then a compile and a backtest per combination |
| check_tradingview_parity | in-process (Binance public API only without your bars) | Grade your TradingView Strategy Tester export against PineForge's run of the same script, trade by trade |
| fetch_binance_ohlcv | Binance public API | Write a backtest-ready CSV from Binance spot or USDT-perp klines |
| binance_symbols | Binance public API | List / filter Binance symbols (5-min in-process cache) |
| list_coverage_topics | local (no I/O) | Every Pine v6 coverage topic with a one-line status + summary |
| check_pine_feature | local (no I/O) | Look up whether a Pine identifier/namespace is supported in PineForge |
| get_coverage_topic | local (no I/O) | Full detail + supported/partial/via_transpiler/unsupported lists for one topic |
| engine_info | local (no I/O) | Docker image only: mode, baked-in flag and the bundled pineforge-release version (for example 1.0.0) |
The table is the Docker image's tool list (11 tools). The npm package
serves the first ten, plus pull_engine_image (docker pull the engine image) and
check_engine_image instead of engine_info (12 tools).
In tools/list every tool also has a title and the four MCP annotation hints
(src/tool-meta.ts). Read-only: the lookups and check_tradingview_parity (it
works in a temporary directory it deletes), and in the Docker image
transpile_pine. Not read-only: backtest_pine and backtest_pine_grid (a
report too large to return is written to a file), fetch_binance_ohlcv (writes
its CSV) and the two image tools; in the npm package also transpile_pine, since
there it and the backtests take an image that Docker pulls when missing.
Destructive: the tools that write a file at a path you name, since they replace a
file already there. Open-world: the tools that reach Binance's public API (the two
backtests do when you pass a symbol) or an image registry.
Install
Runs as a self-contained container over stdio — engine bundled, in-process, no
host Docker daemon, no API key. Mount the folder that holds your CSVs at /work:
Only requirement: Docker, and outbound network for the Binance fetch tools.
Wire it into your MCP client below.
- **Use absolute /work/... paths** in tool arguments (ohlcv_csv_path,
output_path, report_path). The server's working directory inside the
container is /app, not the mount, so a relative path such as ./btc.csv
points into the container and is lost when it exits (--rm).
- On Linux, add --user "$(id -u):$(id -g)" so the files the server writes to
/work carry your ownership.
- -i is required; never add -t — a TTY corrupts the stdio JSON-RPC stream.
The image's :latest and npm's latest always carry a stable release. A
pineforge-release prerelease (such as 1.0.0-rc.1) produces a prerelease of this
server (X.Y.Z-alpha.N, -beta.N or -rc.N): the image :vX.Y.Z-rc.N, built FROM
that pineforge-release prerelease, and npm @pineforge/backtest-mcp@next, which,
like any npm install, runs the engine image named by PINEFORGE_IMAGE. Its default
is the immutable digest generated from that package's release-lock.json, including
the matching prerelease engine. Prereleases are not listed in the MCP Registry.
The first, 0.9.32-rc.1 on pineforge-release
1.0.0-rc.1, was published on 2026-09-30 (image :v0.9.32-rc.1, npm next).
npm / npx
Needs Node ≥ 20 and a running Docker daemon: each transpile and backtest is a
docker run --rm --network=none of the engine image (PINEFORGE_IMAGE, defaulting