> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.ninjatrader.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.ninjatrader.com/_mcp/server.

# Resources

**Beta, pre-release.** The NinjaTrader MCP server and its trading skills are in beta and
aren't yet generally available. The beta runs on Demo only, which trades simulated money.
Live access opens later. Server hostnames, the tool set, the skills, and the onboarding
flow may change before launch.

In addition to [tools](/mcp/tools), the NinjaTrader MCP server exposes **resources**: named, read-only data sources your agent can read on demand or subscribe to for live updates. Where a tool is an action the agent *calls*, a resource is data the agent can *watch*.

Each resource has a `tradovate://` URI and returns JSON. All resources provide read-only access, and the same [account permissions](/mcp/authentication#permissions-and-scopes) as the equivalent tools apply.

## Available resources

| URI                           | Name            | Description                                                                              | Access                |
| ----------------------------- | --------------- | ---------------------------------------------------------------------------------------- | --------------------- |
| `tradovate://account-list`    | Account List    | Your trading accounts with names, types, and active status.                              | Accounting: Read      |
| `tradovate://positions`       | Positions       | All open positions across your accounts with symbol, quantity, and entry price.          | Positions: Read       |
| `tradovate://orders`          | Orders          | All working orders across your accounts with symbol, action, type, quantity, and status. | Orders: Read          |
| `tradovate://product-catalog` | Product Catalog | All tradable products with fees, margins, session times, and contract specifications.    | ContractLibrary: Read |
| `tradovate://kalshi-events`   | Kalshi Events   | Flattened Kalshi event catalog with series, milestones, and markets.                     | ContractLibrary: Read |
| `tradovate://service-status`  | Service Status  | Current platform service health from the public status API.                              | None                  |

## Subscriptions

The server supports resource subscriptions: a client can subscribe to a resource and receive a notification when its data changes. Today the server emits change notifications for the `account-list`, `positions`, and `orders` resources only. The server accepts a subscription to `product-catalog`, `kalshi-events`, or `service-status` but sends no updates for them, so reread those resources on demand. This lets an agent keep an up-to-date view of your `positions` and `orders` as fills and cancellations happen, without polling. Whether and how subscriptions surface in your workflow depends on your AI client's MCP support.

Resources complement tools rather than replace them. For example, the `positions`
resource gives a live view of open positions that you can subscribe to, while the
[`my_portfolio`](/mcp/tools) tool returns a richer one-time snapshot that also includes
account balances and working orders.