# XTester Studio

> XTester Studio is an MCP server for trading analysis. Local stdio MCP server letting AI clients connect to a desktop XTester Studio strategy. It is available on Windows, macOS, Linux and CLI.

- **Kind:** MCP server
- **Platforms:** Windows, macOS, Linux, CLI
- **Website:** https://xtester.pw/mcp/install
- **MCP Registry name:** pw.xtester/xtester
- **Categories:** [trading analysis](https://ai-powered.com/categories/trading-analysis)
- **Listing updated:** 2026-11-18

## About

The README-style registry entry describes XTester as a desktop application for strategy development and testing, and the install guide says it ships a built-in local MCP server. Instead of a hosted endpoint, the AI client launches a local XTester.McpHost process over stdio, so no separate network port is opened on the machine.

Connection is set up from Settings → External agents inside the app, which generates a client configuration with the local executable path already filled in. The guide covers merging that snippet into Claude Code, Codex CLI, Cursor and Claude Desktop configs, and asks the user to approve access per Studio window before an agent attaches. The site states it does not provide a remote MCP endpoint, so browser-only chat clients cannot reach it directly.

The listing is aimed at traders and developers who already build or test strategies in XTester and want an external agent to inspect sessions and tools under explicit permission grants. Requirements include Windows 10 2004+, macOS 14+ or Linux x64 with glibc 2.28+.

## Features

- **Local stdio transport:** The MCP server runs as a local process that the client launches directly, with no open network port.
- **Generated client configuration:** Settings → External agents produces a config snippet with the installation's absolute paths for supported clients.
- **Per-window access approval:** An external agent must be approved in the chosen Studio window before it can attach to a project.
- **Session listing:** A list_studio_sessions tool, where available, shows open windows and their projects before a session is selected.
- **Read-only first check:** The guide suggests a connection test that reads tool lists and makes no file changes or test runs.

## Good for

- Connecting Claude Code or Cursor to a running XTester Studio project to inspect strategy setup
- Verifying an MCP connection with a read-only tool listing before granting any edit permissions
- Letting an agent pick the correct Studio window when several projects are open

## FAQ

### Can a browser-based chat connect to XTester over MCP?

No. The site says a web chat that only accepts a remote HTTP URL cannot connect to this local process, and it does not provide a remote MCP endpoint.

### Which MCP clients have documented configuration formats?

The install guide lists Claude Code (.mcp.json), Codex CLI (~/.codex/config.toml), Cursor (.cursor/mcp.json) and Claude Desktop on Windows and macOS. It notes other clients need separate setup.

### What operating systems are supported?

The guide lists Windows x64 10 version 2004 or later, macOS 14 or later with separate Apple Silicon and Intel builds, and Linux x64 with glibc 2.28+ that also needs the system ICU runtime for tar.gz packages.

## Where this comes from

- Description: written from the project's website and its MCP Registry entry.

## Alternatives

- [TradeOS (test)](https://ai-powered.com/mcp/tradeos-test): TradeOS (test) is an MCP server for sports data.

---
Source: https://ai-powered.com/mcp/xtester-studio
