Configure Cursor
For this project, create or open .cursor/mcp.json in the project root and merge the configuration below into its mcpServers object. For all projects, use ~/.cursor/mcp.json. Preserve other configured servers.
Open Cursor's Customize page to manage MCP servers. Find NexusTrade and complete the requested OAuth connection in your browser. Cursor supports OAuth for remote servers. You can also use Add to Cursor on the NexusTrade developer page and review the installed server in Customize.
Server URL: https://nexustrade.io/api/mcp. Use the same NexusTrade environment as your account.
{
"mcpServers": {
"nexustrade": {
"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.