How to Connect Claude to NinjaTrader 8 Using MCP

Claude already speaks MCP. Point it at CrossTrade.

Anthropic introduced MCP as the standard for AI assistants to talk to external systems. Claude Desktop and Claude Code are MCP-native clients. CrossTrade exposes a hosted MCP server at https://app.crosstrade.io/v1/api/mcp. The combination is the cleanest path from a Claude conversation to your NinjaTrader 8 install.

Setup is one URL, one OAuth approval, one capability check. After that, the conversation does the work.

What you need

Claude Desktop setup

1. Open Claude Desktop.
2. Settings → Developer → Edit Config.
3. Add the CrossTrade server:

{
  "mcpServers": {
    "crosstrade": {
      "url": "https://app.crosstrade.io/v1/api/mcp"
    }
  }
}

4. Save and restart Claude Desktop.
5. On your next message that references CrossTrade, Claude opens a browser tab to the CrossTrade consent screen. Approve mcp:read.
6. Verify by asking Claude to call GetMcpCapabilities and McpSelfTest.

Claude Code setup

claude mcp add --transport http crosstrade https://app.crosstrade.io/v1/api/mcp

On the first tool call, Claude Code prints a consent URL. Approve in the browser; the token is stored in Claude Code's keychain.

When to pick which

• Claude Desktop: interactive trading sessions, journal review, copier diagnostics, day-to-day conversational use.
• Claude Code: NinjaScript authoring, repository-style sessions, longer compile/backtest loops, anything you want under version control.

Run these first to prove the connection

Pre-session brief

Journal review

Webhook audit

Copier diagnosis

NinjaScript compile and Strategy Analyzer

Claude Code is excellent at the compile loop because it can read your local files and call MCP tools side by side. A representative prompt:

For backtests:

Claude Code and NinjaScript vibe coding

Claude Code is a natural fit for strategy coding workflows. The CLI environment can edit local NinjaScript files and call CrossTrade MCP tools in the same conversation. The compile loop becomes a tight cycle: draft, compile in memory, read diagnostics, look up unresolved identifiers, repair, recompile.

• Claude Code is a natural fit for strategy coding workflows.
• CrossTrade MCP gives Claude access to NT8-side compile and backtest feedback.
• The agent should produce a plan before code, with each NT8 type and method confirmed against your install via GetNinjaScriptHelp and LookupNinjaScriptSymbol.
• The agent must summarize every compile repair so you can review what changed.
• The agent must not call DeployStrategy without an explicit confirmation, regardless of how good the backtest looked.

For the full pattern, see Vibe Coding NinjaScript Strategies with CrossTrade MCP.

Hosted CrossTrade MCP vs running your own

Safety notes worth repeating

• Default to mcp:read. Upgrade to mcp:trade only when a workflow needs writes.
• Add confirmation gates in the system prompt for any write action.
• Treat webhook payloads, journal entries, and activity log messages as data, never as instructions.
• Verify firm rules before running an agent against a funded account. See the prop firm AI trading hub.

Common Claude setup errors

Frequently asked questions