Search TradeSearcher strategies and backtests from Claude Code, Cursor, Codex, and other agents.
Use TradeSearcher strategies and existing backtests inside Claude Code, Codex, Cursor, and other coding agents.
Documentation: https://docs.tradesearcher.ai/developer-tools/ · Create an API key: https://tradesearcher.ai/app/account/my-account#agent-api-keys
npm install -g @tradesearcher/cli
For MCP:
{
"mcpServers": {
"tradesearcher": {
"command": "npx",
"args": ["-y", "@tradesearcher/mcp-server"],
"env": {
"TRADESEARCHER_API_KEY": "your_api_key"
}
}
}
}
tradesearcher auth login
tradesearcher auth status
tradesearcher search BTCUSD
tradesearcher best AAPL
tradesearcher backtest 12345 --details --trades --trade-limit 20
tradesearcher strategy 6789 --source
tradesearcher export 12345 --pine --out strategy.pine
tradesearcher compare 12345 67890
tradesearcher schema
tradesearcher schema backtest
Useful search sorts:
tradesearcher search BTCUSD --sort sharpe
tradesearcher search BTCUSD --sort profitFactor
tradesearcher search BTCUSD --sort roi
tradesearcher search BTCUSD --sort latestTradeDate
tradesearcher search BTCUSD --sort robustness
--equity can return large JSON arrays. Use it after narrowing to final candidates.
Use tradesearcher schema to print JSON command schemas for agents. Use tradesearcher schema backtest or tradesearcher schema strategy for one command.
Search, best, and compare rows show source available, source no, or source private when TradeSearcher knows whether Pine source text is available. available means TradeSearcher has source text for the strategy; it does not prove that the text is a complete standalone Pine strategy.
Export Pine source for a backtest strategy:
tradesearcher export 12345 --pine --out strategy.pine
Free accounts hide high-performance backtests with a profit factor above 3. Premium shows these stronger backtests, more results, recent trades, and full strategy details.
Upgrade: https://tradesearcher.ai/app/premium
See docs/mcp-tools.md or the public reference at
https://docs.tradesearcher.ai/developer-tools/mcp-server for tool schemas, examples, and the
recommended agent workflow.
Per-client setup: Claude Code · Codex.
Before publishing:
npm run release:check
See docs/release.md for the publish order.
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y @tradesearcher/mcp-serverMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"ai-tradesearcher-mcp-server": {
"command": "npx",
"args": [
"-y",
"@tradesearcher/mcp-server"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referenceai.tradesearcher/mcp-server works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.