Configure Claude.ai
On an individual Pro or Max account, open Customize, then Connectors. Choose + Add, then Add custom connector. Name it NexusTrade, paste the server URL below and choose Continue. Review detected authentication and continue. Choose Sign in now and Claude's published OAuth identity, then finish with Add and complete NexusTrade sign-in.
On Team or Enterprise, an owner first adds the Web connector in Organization settings, Connectors. Members then open Customize, Connectors and choose Connect. In a chat, use +, then Connectors to enable NexusTrade for that conversation.
Server URL: https://nexustrade.io/api/mcp. Use the same NexusTrade environment as your account.
https://nexustrade.io/api/mcpAuthorize 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.