MCP

Hosted MCP vs Local MCP for Trading Systems

Local MCP is useful for experiments. Production trading needs OAuth, scoped permissions, an NT8 bridge, journal and webhook history, and updates that ship when NT8 changes. CrossTrade ships that.

CrossTrade Team

• 3 min read
Share
Hosted MCP vs Local MCP for Trading Systems

An honest comparison. Local MCP is not bad. Hosted MCP is not magic. Both exist for good reasons. The question is which one fits a trading workflow that has real users and real consequences.

Local MCP is useful

If you are a developer prototyping a custom tool, a local MCP server is the right choice. You control the surface. You define the tools. You change them as fast as you can edit a file. The friction is low. The blast radius is small. The audience is one person.

Local MCP is the right shape for:

  • Research sandboxes.
  • Internal developer tools.
  • One-off experiments with no production trading permission.
  • Projects where you change the surface frequently.

Production trading needs more than a local pipe

Once real money and real users are involved, the requirements change.

  • OAuth. Tokens that the user can authorize and revoke. PKCE. Dynamic client registration. The standard machinery.
  • Scoped permissions. A read scope must be a hard floor. The transport must reject writes from a read token.
  • Auditability. A list of authorized clients per user. The ability to revoke a stale client. A log of writes.
  • Support. Someone to file a bug with when the backtest engine starts diverging from NT8's UI.
  • Updates. The NT8 surface changes. The add-on changes. The protocol evolves. Production trading needs a supplier on the hook for keeping up.

None of these are out of reach in a local server. All of them are non-trivial. Each of them takes work you could be spending on your actual trading.

OAuth, scopes, auditability, support

The OAuth piece is the one most local implementations skip. The temptation is to grant a long-lived API token and call it a day. That works until the token leaks (terminal screenshot, log line, copied-and-pasted to a teammate) and you realize there is no revocation path.

CrossTrade MCP issues OAuth 2.1 tokens with PKCE. Tokens are bound to a single OAuth client. Users see a list at AI Clients and can revoke any of them instantly. The audit trail of which AI client has which scope lives in one place.

NT8 desktop complications

NinjaTrader 8 is a Windows desktop application. There is no cloud surface to point an MCP server at. Whatever talks to NT8 must run on the same machine as NT8.

CrossTrade's add-on is what does that work. It connects out to CrossTrade's hosted services. The hosted MCP server routes requests to the add-on, the add-on talks to NT8, and the response travels back. The bridge is reliable because CrossTrade has been operating it for years for webhooks, REST, and copier features. MCP is the newest interface on the same bridge.

If you build local MCP for NT8, you will end up writing your own version of this bridge. That is a significant undertaking that has nothing to do with the trading logic you actually wanted to build.

CrossTrade's hosted model

What you get for choosing hosted CrossTrade MCP:

  • One URL: https://app.crosstrade.io/v1/api/mcp.
  • OAuth 2.1 with PKCE and dynamic client registration.
  • Scopes mcp:read and mcp:trade, enforced at the transport.
  • The CrossTrade Add-On bridge to NT8.
  • A versioned, documented tool surface that grows over time.
  • NT8 Strategy Analyzer parity for single backtests.
  • Months of TradingView webhook history, copier activity, and matched-trade journal accessible as read-only tools.
  • CrossTrade ships updates when NT8 changes.

The cost is the Elite subscription tier. REST and WebSocket remain on Pro.

Stay synced across every follower with the CrossTrade trade copier Learn More

Where local still wins

If your workflow is none of the above, local is fine. A research notebook that pulls bars and runs a custom statistical analysis does not need OAuth. A one-developer team building an internal dashboard does not need a managed bridge. The decision is "what audience does this serve and how much production risk is attached."

The two are not mutually exclusive. Most MCP clients support multiple servers. Run CrossTrade for the production NT8 workflows. Run a local server for whatever it does best.

Comparison page

For a side-by-side comparison with the full table, see NinjaTrader MCP Server: Hosted OAuth vs Local MCP.

Pick by audience. Local for one developer. Hosted for traders who do not want to maintain auth, audit, and the NT8 bridge themselves.