Access Your Trade Data from Claude Desktop via MCP

This guide explains how to reference and analyze your TraderIsMe trade data directly from an AI chat client like Claude Desktop, using MCP (Model Context Protocol) integration. All you need to do is issue a single API key and paste it into Claude Desktop’s config file — then you can hand your trade history to the AI in natural language, with prompts like “Analyze my USDJPY trades from last month” or “What time of day has the highest win rate?”

MCP integration is free on every plan, including the Basic plan.

What You Can Do with This Guide

  • Retrieve TraderIsMe trade data from Claude Desktop using natural language
  • List your accounts, select an account, and pull filtered trade history
  • Since history is handed directly to the AI, you can run any analysis the UI does not expose

Requirements

Step 1: Issue an MCP API Key

  1. Log in to TraderIsMe and open “Settings” in the left sidebar.
  2. Open the “MCP Integration” section on the page and click “Generate API Key.”
  3. Click the “Copy” button to the right of the generated MCP API key to copy it.

The MCP API key is a different key from the “account identifier API key” used by the Data Sync EA or the “account API key” used by feature EAs. Manage it separately as dedicated to MCP integration. If the key leaks, you can invalidate it with the “Regenerate” button on the same screen (regeneration immediately invalidates the previous key).

Step 2: Add It to the Claude Desktop Config File

Claude Desktop loads external MCP servers via a config file called claude_desktop_config.json. Its location by OS is:

OSConfig file location
macOS~/Library/Application Support/Claude/claude_desktop_config.json
Windows%APPDATA%\Claude\claude_desktop_config.json

When you issue a key in the “MCP Integration” section of the TraderIsMe settings screen, a ready-to-paste JSON snippet is auto-generated below it. Click “Copy” and paste it into the config file above.

The snippet looks like this (the MCP API key issued in Step 1 is automatically filled into the YOUR_API_KEY placeholder):

{
  "mcpServers": {
    "traderisme": {
      "command": "npx",
      "args": ["-y", "traderisme-mcp"],
      "env": {
        "TRADERISME_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}

If you have already registered other MCP servers (e.g., filesystem, github), merge the "traderisme": { ... } entry into the existing mcpServers object. A JSON syntax error will prevent Claude Desktop from loading MCP servers, so watch your commas carefully.

Step 3: Restart Claude Desktop and Verify

After saving the config file, fully quit and relaunch Claude Desktop. On first launch, npx -y traderisme-mcp downloads the package, which can take tens of seconds.

After it starts, look at the tools list in the input area (the 🔧 icon). If a traderisme server appears with the following tools registered, the connection is successful:

Tool namePurpose
get-accountsList registered trading accounts
select-accountSelect the active account for the session (target of other tools)
get-tradesFetch trade history for the selected account (filter by symbol / period / direction / count)

Try talking to the chat window like this:

  • “Show me my registered accounts” → get-accounts is called and returns the account list
  • “Select account ID 1” → select-account locks the target account
  • “Give me 100 USDJPY trades from last month” → get-trades filters by period and symbol
  • “From this history, break down win rate by day of the week” → the AI can analyze the fetched history freely

Troubleshooting

  • traderisme does not appear in the tools list — Possible JSON syntax error in the config file, or Claude Desktop was not restarted. Validate the file with a JSON validator and fully quit Claude Desktop (Cmd+Q / quit from the task tray) before relaunching.
  • “Authentication error” or “Invalid API key” is returned — Regenerate the MCP API key from the settings screen and replace TRADERISME_API_KEY in claude_desktop_config.json with the new key.
  • npx: command not found — Node.js is not installed. Install the LTS version from nodejs.org.
  • Accounts list works, but trades come back empty — First check that you have selected an account with select-account. Without selection, get-trades returns empty. Also check that the account has any synced trade history (verify your Data Sync EA setup).

Related Documents