AI trading workflows

Connect VS Code Copilot to NexusTrade research tools

Install NexusTrade MCP in VS Code, complete OAuth and inspect company research beside your strategy files.

As of 2026-10-10

Connection
Remote MCP with OAuth
First output
Dated company brief

Use Copilot chat beside your research files

This guide is for VS Code Copilot users who want NexusTrade research tools in chat. Keep sources and research notes beside the proposed strategy. Cursor and the Codex extension have separate setup flows.

Install the server in VS Code

Open NexusTrade Developers and select Add to VS Code. Allow the browser to open VS Code, inspect the NexusTrade HTTP server definition and confirm installation. Alternatively, run MCP: Add Server in the Command Palette and follow its guided remote-server setup.

For a new portable workspace setup, place the block below in .mcp.json at the project root. Existing .vscode/mcp.json files use a top-level servers object; do not paste this portable mcpServers block into that format.

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

Authenticate and check the tools

Start the server when VS Code asks to trust it. Open Chat and use Configure Tools to enable NexusTrade tools. Complete NexusTrade browser OAuth when authentication is requested.

Ask Copilot to list the tools and read an existing portfolio without updating it. Confirm its name and ID in NexusTrade. Review the proposed tool inputs before approving the first research call.

Save the first company brief

Use the request below, then save filing sources, reporting periods and uncertainties in a workspace note. Check the filing behind each figure before translating the thesis into strategy code.

text
Use NexusTrade read-only research tools to compare AAPL reported revenue and operating cash flow over stated filing periods. Cite primary filings and publication dates. Record missing or restated values and distinguish facts from interpretation. Do not create, update, deploy or trade any portfolio.

Keep strategy changes separate from research

Review the complete candidate rules and test assumptions before submitting a historical run. Retain the original definition and accepted operation IDs so the next diff has a clear baseline.

Check a missing tool or failed account read

If NexusTrade tools are missing, check that the server is enabled and trusted, then use Configure Tools to enable the tools needed for the read-only task. Complete any pending OAuth prompt. If a request fails, inspect the server error before editing strategy code. Check the returned portfolio identity against NexusTrade; an empty list is a valid result for a new account.

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.

Continue exploring