Choose the surface you are using
ChatGPT can help formulate a research question and explain strategy rules. To read or change your NexusTrade account, it needs an authenticated tool connection. Desktop MCP settings and hosted web plugins are separate surfaces.
This guide describes the documented setup and NexusTrade tool contracts. No connected ChatGPT account, historical test or trade was executed to produce the page.
Desktop: add the NexusTrade MCP server
In the ChatGPT desktop app, open Settings → MCP servers → Add server. Enter the name nexustrade, choose Streamable HTTP and set the URL to https://nexustrade.io/api/mcp. Save, select Restart, then select Authenticate to complete NexusTrade's browser OAuth flow.
Start a local Codex task and type /mcp to inspect the connection. The configuration belongs to that Codex host and is shared with its CLI and IDE clients. Do not expect it to appear automatically in a hosted web chat.
NexusTrade MCP URL: https://nexustrade.io/api/mcp
Transport: Streamable HTTP
Authentication: OAuthWeb: use an available plugin or an authorized custom app
Open the Plugins tab, inspect the available integration and install it with the plus button. Complete the requested account connection and start a new chat. Hosted web chats do not read your local config.toml. If NexusTrade is not listed, use the custom-app setup below.
For accounts with custom-app controls, Pro users can connect MCP with read/fetch permissions in developer mode. Full MCP including writes is available to eligible Business and Enterprise/Edu users. Business admins or owners and authorized Enterprise/Edu members can enable developer mode. Admins use Workspace settings → Apps → Create; authorized users can use Settings → Apps → Create. Supply the NexusTrade endpoint and OAuth authentication, select Scan Tools, complete sign-in, then Create. Admins or owners control workspace publication.
These Apps controls depend on the account and workspace. In the Admin console, Plugins → Manage Legacy Apps opens the app-management surface. If your account has neither an available integration nor authorized custom-app creation, use the supported desktop path or ask your workspace administrator. Regular chat access alone does not establish custom MCP availability.
Verify access without changing anything
Discover the NexusTrade tools, then ask fetch_portfolios for owned portfolios. Read one returned ID with get_portfolio and check the account, saved strategies and deployment type. An empty list can be a valid new account; it is not proof of a failed connection.
Keep SDK API keys out of the OAuth MCP setup. Authorize in the browser rather than pasting a brokerage credential into your chat.
Use only NexusTrade read tools. List my owned portfolios and inspect one returned ID. Summarize its strategies and whether it is a draft, paper or live portfolio. Do not create, edit, backtest, deploy or place orders.Turn the brief into rules you can inspect
Ask for the universe, signal, sizing, exit rule, test period, initial capital and benchmark before submitting a historical test. Keep the returned backtest ID, poll the same run and inspect warnings, orders and drawdown. Use a separate paper deployment when you want forward simulation.
Account tools can create or change resources. Approve the specific next step after reviewing it. A conversation about a promising result is not an instruction to activate live trading.
Draft a strategy from this research brief. Show the complete rules and test assumptions first. After I approve the configuration, run one historical test and compare it with the stated benchmark. Stop after the result review; do not deploy.Follow the task through to a returned result
Start with the source brief, then freeze a rule for a historical test. The paper guide shows how to identify the running simulated book, read its history and pause it. Check that your current connection grants the required tools before saving or activating anything.
Review a separate brokerage workflow
Public and Tradier deployment use the documented NexusTrade broker connections. The Robinhood guide uses Claude Code with Robinhood’s external MCP server. A paper book does not transfer into a brokerage account by itself; verify the live account, permissions and execution schedule in the selected guide.