Connect VS Code to NexusTrade MCP

Add the NexusTrade server

{
  "servers": {
    "nexustrade": {
      "type": "http",
      "url": "https://nexustrade.io/api/mcp"
    }
  }
}

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 shown above and name nexustrade. Choose workspace .mcp.json or Copilot Global for a new portable configuration.

Sign in to your NexusTrade account

Alternatively, run MCP: Open User Configuration and merge the servers configuration shown above 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.

Verify with a real read

Run this public read after sign-in. Match the company, filing form, date and SEC URL in the returned result.

Recorded public read: Apple SEC filing

NexusTrade MCP sec_edgar returned this listing in Codex on 2026-10-12. Use it as a reference when checking your own connection.

Point it at trading

Once the connection is live, these walkthroughs run against your NexusTrade account through VS Code.

If something doesn't work

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.

Continue exploring