Use QuanterLab in ChatGPT and Claude

Ask in a chat, and the assistant reads QuanterLab's published research and your own saved work, and runs backtests, walk-forwards and scans on your account. You need a QuanterLab account, and a free one works: it reads everything on every plan and runs three a day on the Free plan (what each plan runs). Sign up for free.

ChatGPT

QuanterLab in ChatGPT

QuanterLab is in ChatGPT's plugin directory, free ChatGPT accounts included. Setup in three steps.

  1. Open QuanterLab in ChatGPT, or search for QuanterLab under Plugins in ChatGPT, and install it.
  2. Click Sign in with QuanterLab, sign in with your QuanterLab email and password (a free account works), then approve.
  3. In a chat, type @QuanterLab and ask. Try: What did QuanterLab find about dividend capture? Give the headline numbers and the link to the paper.

To add it by hand instead, in ChatGPT's Developer mode, the server URL is https://quanterlab.com/mcp, with OAuth.

How it connects

ChatGPT calls an MCP server a plugin. It connects through OAuth, which this server speaks (dynamic client registration, PKCE), so the same URL connects. It also asks every plugin for two tools of its own, search and fetch, which here cover the published research library: a search returns papers with their public URLs, a fetch returns a paper's text, so ChatGPT can cite a QuanterLab paper by its page. Your own work stays behind the list tools below, under your login.

Claude

QuanterLab in Claude

QuanterLab is in Claude's plugin directory, for claude.ai, the Claude desktop app, Cowork and Claude Code. The plugin brings this connector and the skills that tell Claude how to use it. Plugins come with Claude's paid plans (Pro, Max, Team and Enterprise); on Claude's Free plan, add the connector by hand instead (below). Setup in three steps.

Open QuanterLab in Claude
Opens claude.ai: sign in to Claude there first
  1. Click the button above, or in Claude open Customize, then Plugins, then Discover, and search for QuanterLab. Click Add.
  2. When Claude asks you to connect QuanterLab, a QuanterLab page opens: if you are signed in on quanterlab.com in that browser it knows you, otherwise sign in with your email and password or with Google. Approve.
  3. In a chat, ask. Try: What did QuanterLab find about Buffett's “be greedy when others are fearful”? Give the headline numbers and the link to the paper.
Add the connector by hand instead

This route works on every Claude plan, Free included (Claude's Free plan allows one custom connector; on Team and Enterprise an Owner adds it for the organisation). In claude.ai's connector settings, use this URL:

  1. Click Open the claude.ai connector setup. claude.ai opens its Add custom connector dialog with the name and https://quanterlab.com/mcp filled in (the URL is on your clipboard too); confirm it.
  2. Click Connect. A QuanterLab page opens: if you are signed in on quanterlab.com in that browser it knows you, otherwise sign in with your email and password or with Google.
  3. Approve. The page lists what the connector may do.
  4. Back in claude.ai the connector shows as connected. Try: What did QuanterLab find about Buffett's “be greedy when others are fearful”? Give the headline numbers and the link to the paper.

In either assistant

What to ask, and what a run needs

Once connected, ask things like

  • Backtest RSI(14) below 30 to buy and above 70 to sell on SPY over ten years of daily bars, then summarise the result.
  • Run a walk-forward on that strategy over five years: the RSI length from 7 to 21 and the buy level from 20 to 40.
  • What did QuanterLab find about dividend capture? Give the headline result and the link to the paper.
  • List my saved canvas projects, run the newest one and tell me how it did.
  • Which momentum indicators does QuanterLab support, and what are RSI's usual settings?

What each plan runs.

FreePractitionerResearch
Read the studies and your saved workYesYesYes
Runs a day3 in allEach kind up to its capEach kind up to its cap
Runs at the same time333

A run is a backtest, a walk-forward, a scan, a regime analysis or one of your saved lab circuits, on daily bars. Each kind's daily cap, the same on every plan: 50 backtests, 50 stochastic-method backtests, 10 walk-forwards, 10 lab circuits, 30 mean-reversion scans, 15 pairs scans, 20 regime analyses and 10 regime optimisations. A lab circuit with a Research card in it (the factor models, the routers, paper-trade markers) runs on Research, as in the lab. A refused call does not count, and a run outside your plan or past a cap is refused with a message that says why. The plans.

What this connector will not do: the assistant does not receive raw market data or raw fundamentals through it, only processed metrics, tiers, scanner outputs and your own saved work. It places no orders and moves no money, and nothing it returns is investment advice: a backtest describes how rules behaved on past data. Revoke access any time in the assistant's connector or plugin settings.

Three surfaces

Three ways an AI works with QuanterLab

Quantin, inside the platform
A chat assistant in the web app. It explains cards, methods and results and guides you around the platform. It runs nothing.
The QuanterLab connector, in ChatGPT and Claude. This page.
A hosted MCP server your ChatGPT or Claude account connects to. It reads the catalog and the published papers and lists your own saved work on every plan; it runs backtests, walk-forwards, scans and your saved canvas strategies (what each plan runs), and follows and summarises them. Runs are simulations on historical data: it places no orders and moves no money.
QuanterLab Desktop, on your machine
The engine and the canvas installed locally, with a local MCP server that Claude Desktop or Claude Code connects to. It builds and runs circuits, walks a registered study window by window, compiles it, and submits it to the platform as a draft. Compute is your machine. Download and setup.

Skills

Four skills for an assistant that does research here

A skill is a short file an assistant reads before it acts. These four state, in the order a model needs them, what keeps a study on QuanterLab clean: the traps, the structure of the work, the shape of a status report, and the bones of a paper. They are written for Claude Code and Claude Desktop; any assistant that reads instructions can use them.

Download the four skills
One zip, four folders, each holding a SKILL.md
The traps, stated so a model recognises them before it commits: look-ahead in every form it takes, survivorship, costs and financing charged as real, multiple testing, and the limits of the data checked before design.
How a piece of work stays legible to the person who returns to it in a month: one project per question, names that say what the run was, the record of what was tried including the arms that died, and what a run needs to be re-run by someone else.
Status without invented findings: what was run, what came back, what is in flight, the next decision. Verdicts reported as verdicts, and permission to say nothing happened.
The bones of a paper produced from the platform: what is bought, when and for how long before anything else, with a figure per action type; the declared hypothesis and family size on the page; limitations stated; what is published alongside so the result can be re-run.

Install. QuanterLab Desktop installs the four for the assistant seated in it; nothing to do there. Claude Code: unzip into ~/.claude/skills/ for every project, or into a project's .claude/skills/ for that project alone; each skill then answers to /quanterlab-research-hygiene and the other three names. Claude Desktop: Settings, Skills, add each SKILL.md. The desktop app's own MCP server also serves three prompts, study_setup, study_hygiene and paper_prep, which appear as slash commands in Claude Code and as templates in Claude Desktop without any installation.

Reference

What the hosted connector serves

Claude picks the tool from plain language; the list is for readers who want to see what is there. Each tool that starts a run says which plan runs it, and each run returns a task that the progress tools follow and summarize_workflow reads.

Universal Strategy Builder
Indicator-rule backtesting and walk-forward optimisation on a single ticker.
  • start_backtest, start_walkforward: each start is a run (what each plan runs).
  • list_indicators: the indicator catalogue with parameter shapes.
  • get_backtest_progress, get_walkforward_progress: progress of a run.
Stochastic methods
OU, Kalman and cointegration models, and the universe scanners.
  • start_stochastic_backtest, start_mr_scan, start_pairs_scan: each start is a run (what each plan runs).
  • list_stochastic_methods: the method catalogue.
  • get_stochastic_backtest_progress, get_mr_scan_progress, get_pairs_scan_progress: progress of a run.
Regime optimizer
HMM regime detection with per-regime thresholds.
  • start_regime_analysis, start_regime_optimization: each start is a run (what each plan runs).
  • get_regime_analysis_progress, get_regime_optimization_progress: progress of a run.
Primitives
The circuit engine's catalog and your runs.
  • start_primitives_run: runs one of your saved canvas projects; each start is a run (what each plan runs), and one with a Research card runs on Research.
  • list_primitives: the catalog and what each primitive does.
  • get_primitives_run_progress, get_primitives_run_result: progress and the summarised result of a run.
  • list_my_primitives_projects: your saved circuits and studies.
Fundamental analyzers
  • list_fundamental_analyzers: the fundamental analyzers and their inputs.
Your saved work
What you saved on the platform, and the research library.
  • list_my_backtests, list_my_filter_results, list_my_trading_configs, list_my_projects, list_my_running_tasks.
  • save_trading_config, save_workflow_result, summarize_workflow: save and summarise what a session produced.
  • search, fetch: the published papers, with their public links.
  • describe_capability: which workflow fits a question, and what it needs.
Other Claude clients for the hosted connector

Claude Desktop, in claude_desktop_config.json:

{
  "mcpServers": {
    "quanterlab": { "url": "https://quanterlab.com/mcp" }
  }
}

Restart Claude Desktop; the sign-in opens in your browser on first connection. Claude Code:

claude mcp add --transport http quanterlab https://quanterlab.com/mcp

Then /mcp inside Claude Code to sign in. Claude in Chrome reads the connector list of your claude.ai account.

For the desktop's local server, the one that runs and registers research, the configuration is written by the desk's Assistant panel with one click; the manual form is on the desktop page.