Connect Continue to NinjaTrader 8
Open-source IDE assistant (VS Code + JetBrains). YAML config, kebab-case transport, bearer-token auth.
Continue calling CrossTrade MCP tools against a live NinjaTrader 8 account. Run this yourself in 5 minutes →
Why pair Continue with CrossTrade MCP
Continue runs in both VS Code and JetBrains IDEs with the same config. Edit ~/.continue/config.yaml to add CrossTrade. Bring your own provider API keys.
~/.continue/config.yaml with type: streamable-http (kebab-case) What this combination unlocks
Cross-IDE
Same YAML works in VS Code and JetBrains.
BYOK
Use any provider key directly.
The connection chain
Continue │ OAuth-authorized tool call ▼ CrossTrade hosted MCP server (https://app.crosstrade.io/v1/api/mcp) │ ▼ CrossTrade Add-On running inside NT8 on your PC │ ▼ NinjaTrader 8
One URL, one consent screen, one read-only first prompt. The MCP server is hosted by CrossTrade; you don't run anything beyond NT8 + the CrossTrade Add-On.
Ready to set up Continue?
The full step-by-step setup lives on a dedicated page. Verified against Continue.dev's current docs.
Copy-paste prompts that work today
Also consider
Common questions
Is Continue a good fit for NinjaScript development?
Yes, especially if you split work between VS Code and JetBrains IDEs. Continue runs in both with the same YAML config. BYOK across providers. The MCP integration uses streamable-http (kebab-case) transport.
Do I need Continue, or does Cline / Roo Code / Copilot work?
Continue is the only major one that runs in JetBrains AND VS Code from the same config. Cline / Roo Code are VS Code only. Copilot is the GitHub-native option. If your team mixes IDEs, Continue keeps the trading agent config in one place.
Cost?
The extension is free, open source, BYOK. Continue Hub (paid tier) hosts shared assistants for teams. For solo trading use, you only pay the model provider.
Does Continue support OAuth for remote MCP?
Not yet natively — the documented path is a bearer token in requestOptions.headers. To get a CrossTrade token, authorize via another OAuth-capable client (Claude Code, Cursor) and copy from the AI Clients page. Continue is likely to add native OAuth in a future release.
Why is type required, unlike Cursor?
Continue's YAML schema demands an explicit type field. Valid values: stdio, sse, streamable-http (kebab-case). Omitting it leaves the server in an undefined state. Cursor and Windsurf infer transport from url, but Continue doesn't.
Continue vs Cline?
Cline has stronger MCP UX (browser OAuth, panel UI for managing servers). Continue is cross-IDE (VS Code + JetBrains). Pick Cline if you're VS Code only and want polish; Continue if you also work in IntelliJ/PyCharm/Rider.
Can I use Continue on the JetBrains side for NinjaScript / Rider?
Yes — Continue's JetBrains plugin works in Rider, IntelliJ, PyCharm, GoLand, etc. Same YAML config. Useful if you're maintaining NinjaScript C# in Rider and want CrossTrade tools alongside.
Where does the YAML config live?
~/.continue/config.yaml (Mac/Linux) or %USERPROFILE%\.continue\config.yaml (Windows). For project-scoped overrides, put .continue/config.yaml in your repo root, or per-server YAML files in .continue/mcpServers/.
Connect Continue to NinjaTrader 8 in 5 minutes
Free Sim101 walkthrough. Read-only first. Upgrade scope only when a real workflow needs it.
