Tradesearcher Agent Tools MCP

What Tradesearcher Agent Tools MCP MCP server does

Tradesearcher Agent Tools MCP MCP server gives coding agents access to TradeSearcher strategy and backtest data. It is intended for workflows that begin with finding strategies for an asset and continue with inspecting performance, reviewing trades, comparing backtests, or exporting strategy source when available.

The available operations correspond to the project’s documented command-line capabilities. Agents can search by symbol, request a best-result view, retrieve backtest or strategy details, compare two backtests, export Pine source, and inspect command schemas. Search results can be sorted by measures such as Sharpe ratio, profit factor, return on investment, latest trade date, or robustness.

How it works

The server is launched as an MCP process through npx and receives TRADESEARCHER_API_KEY in its environment. An MCP-compatible client can then invoke the server’s tools from an agent workflow. The repository separately documents MCP tool schemas, examples, and a recommended workflow.

A typical process is to narrow search results first, inspect promising backtests, and then request further details or compare finalists. Backtest output can include details, trades, and equity data. Equity arrays may be large, so the README recommends requesting them only after reducing the candidate set.

TradeSearcher reports whether Pine source is available, unavailable, or private when it knows the source status. An available status means TradeSearcher has source text for the strategy; it does not establish that the text is a complete, standalone Pine strategy.

Setup and configuration

Install the published MCP package through an MCP client configuration rather than installing the repository directly:

{
  "mcpServers": {
    "tradesearcher": {
      "command": "npx",
      "args": ["-y", "@tradesearcher/mcp-server"],
      "env": {
        "TRADESEARCHER_API_KEY": "your_api_key"
      }
    }
  }
}

Create the API key through the TradeSearcher account page. The repository also provides client-specific setup documentation for Claude Code and Codex. The CLI package can be installed globally with npm install -g @tradesearcher/cli, but that installation is separate from configuring the MCP server.

Tools and capabilities

Tradesearcher Agent Tools MCP MCP server supports these documented task types through its agent tooling:

• Search strategies for an asset such as BTCUSD.
• Sort search results by Sharpe, profit factor, ROI, recency, or robustness.
• Retrieve a best-result view for a symbol.
• Read backtest details and trades, with an optional trade limit.
• Retrieve strategy information and request its source.
• Compare two backtests.
• Export Pine source for a backtest strategy when source is available.
• Print schemas for all commands or for a specific command.

The source export example writes Pine output to a local file. The documented examples use backtest and strategy identifiers to retrieve records and source-related information.

Limitations and notes

Account level affects the data returned by TradeSearcher. Free accounts do not show high-performance backtests with a profit factor above 3. Premium accounts expose those stronger backtests, additional results, recent trades, and complete strategy details.

Source availability is not the same as source completeness, and private source cannot be treated as exportable. Large equity responses can produce substantial JSON, so they are better reserved for shortlisted candidates. The provided material does not specify additional authentication methods beyond the API key environment variable or define client-specific behavior outside the documented Claude Code and Codex setup notes.