NinjaTrader MCP Server: CrossTrade, Native and Local Options

Pick the account access and workflow you need

NinjaTrader 8 is a Windows desktop application. CrossTrade’s desktop tools need its add-on running inside that installation. A cloud brokerage connection is a different route: it reaches supported broker accounts without making your local NinjaScript environment available automatically.

• Local MCP for NT8: a developer-controlled MCP server running on the trader's PC. Useful for sandboxed experiments, internal tools, and workflows that never touch live trading permissions.
• Hosted CrossTrade MCP: a CrossTrade-managed endpoint at https://app.crosstrade.io/v1/api/mcp. OAuth 2.1, scoped permissions, the CrossTrade NT8 Add-On bridge, journal and webhook and copier history, Strategy Analyzer parity. Built for production trading.
• Native NinjaTrader MCP beta: NinjaTrader documents a remote HTTPS/OAuth service with Demo and Live endpoints, account reads, order operations and risk tools. This is separate from Nina insights and its desktop AI Strategy Builder.

See the dated native-AI comparison, then follow CrossTrade setup or the AI strategy-building workflow.

The job description

An NT8 MCP server gives an AI client typed access to the tools that server implements. CrossTrade’s desktop workflow includes:

• Reading accounts, positions, orders, executions, quotes, and bars.
• Resolving NT8 symbols, methods, and overloads so the agent's generated code compiles.
• Placing, modifying, cancelling, and flattening orders (with the right permission).
• Running NinjaScript compile and Strategy Analyzer backtests.
• Deploying and monitoring strategies.

A production NT8 MCP server adds the operational layer: journal history, add-on activity, copier diagnostics, OAuth, scoped permissions, audit trail, and predictable updates.

NinjaTrader runs on your desktop. That changes the problem.

Cloud brokers like Tradovate have HTTP APIs. To inspect the types, scripts and strategy instances inside your own NT8 installation, CrossTrade uses an add-on in that installation. NinjaTrader’s published native MCP beta is a separate remote account service; do not confuse its brokerage connection with CrossTrade’s desktop bridge.

CrossTrade's bridge is the CrossTrade NT8 Add-On, which has been the bridge that powers webhooks, REST, and copier features for years. MCP is the latest interface that uses it.

What a local MCP server looks like

AI client  ──(stdio or HTTP)──>  Your local MCP server (Node/Python)  ──>  NT8 (NinjaScript)
                                              │
                                              └─ tokens, config, code
                                                 you maintain it all

Strengths:

• Full control. You define every tool.
• No subscription cost beyond NT8.
• Good for research where you change the surface frequently.

Costs:

• You write and maintain the bridge.
• You handle auth, scopes, logging, error handling.
• You ship updates when NT8 changes.
• You have no journal, no webhook history, no copier integration unless you write them.

What CrossTrade ships

AI client  ──(OAuth)──>  https://app.crosstrade.io/v1/api/mcp  ──>  CrossTrade NT8 Add-On in NT8
                                       │
                                       ├─ scoped tokens (mcp:read, mcp:trade)
                                       ├─ typed tool surface (versioned)
                                       ├─ journal, webhook signals, copier activity
                                       └─ backtest engine parity with NT8 SA UI

Strengths:

• One URL, no local server to maintain.
• OAuth 2.1 with PKCE and dynamic client registration.
• CrossTrade NT8 Add-On bridge, already deployed inside NT8.
• Matched-trade journal, TradingView webhook history, add-on activity log: months of operational data the agent can analyze.
• NT8 Strategy Analyzer parity: single backtests are bit-identical to NT8's UI.
• CrossTrade ships updates when NT8 changes.

Costs:

• Elite subscription required for MCP transport.
• The tool surface is curated; not every NT8 internal is exposed.

Hosted vs local at a glance

Choose by audience

Check permissions and operational behavior

Hosted versus local describes where the service runs. Check the actual permissions, account controls and failure behavior before using either route.

• OAuth scope is enforced at the transport. A mcp:read token cannot call write tools.
• Tokens are revocable from the CrossTrade AI Clients page.
• CrossTrade's add-on already enforces opposing position protection, auto-reconnect, and the operational constraints traders care about. The MCP server inherits those.
• Keep the add-on current and recheck capabilities after NT8 or client upgrades. An unavailable tool or failed read is a reason to investigate, not to assume the old behavior still applies.

Frequently asked questions