Configure VS Code
Open the Command Palette with Cmd+Shift+P on macOS or Ctrl+Shift+P on Windows/Linux. Run MCP: Add Server and follow the remote HTTP server flow with the URL below and name nexustrade. Choose workspace .mcp.json or Copilot Global for a new portable configuration.
Alternatively, run MCP: Open User Configuration and merge the servers configuration below into that VS Code profile file. It is the VS Code profile format, rather than the portable mcpServers format. Run MCP: List Servers, select NexusTrade and start it. Complete the account sign-in requested by the connection, then inspect its tools in chat. Workspace trust and server enablement can affect availability.
Server URL: https://nexustrade.io/api/mcp. Use the same NexusTrade environment as your account.
{
"servers": {
"nexustrade": {
"type": "http",
"url": "https://nexustrade.io/api/mcp"
}
}
}Authorize the account connection
The remote MCP server uses OAuth discovery. Sign in to NexusTrade and approve the requested connection. An SDK API key is a separate credential; do not paste it into a client configuration that already supports OAuth.
Authorization grants access to the account’s supported tools; it does not publish your portfolios, watchlists, conversations or custom datasets. Keep credentials out of shared configuration and screenshots.
Check the connection with a read
Ask the client: Discover NexusTrade tools, then call fetch_portfolios to show my saved portfolios. Read one returned ID with get_portfolio. Do not create, edit, deploy or backtest anything. Compare its name and rules with the same portfolio in your NexusTrade account. An empty portfolio list can be a valid result for a new account; it is not a failed connection.
If NexusTrade is absent from the client's server list, check that you saved the configuration in the selected project or profile. If it appears but requests sign-in, finish the client-specific OAuth step above. If a read returns an authorization error, reconnect to the intended NexusTrade account. Preserve the returned error instead of asking the agent to bypass authentication. A research conversation can request compute and backtests, which can consume credits. Historical results are simulations. Live-order workflows retain their existing application approval boundary.