TL;DR
Use VS Code's MCP server controls to add NexusTrade, complete browser sign-in and enable the tools in Copilot chat. Check a public filing first, then verify the intended account before using owned portfolios. Keep source periods and research notes in the workspace, and freeze explicit rules and assumptions before a historical test. Paper observation and live brokerage deployment are separate workflows with their own portfolio IDs, account permissions and evaluation schedules.
Connect Visual Studio Code in the intended environment
- Configuration format
- The full guide distinguishes portable .mcp.json from the supported VS Code profile format. Preserve other servers when merging configuration.
In VS Code’s Command Palette, run MCP: Add Server. Follow the remote HTTP setup with name nexustrade and URL https://nexustrade.io/api/mcp. Choose the intended workspace or global scope. Run MCP: List Servers, start NexusTrade, complete browser sign-in and enable the needed tools in Copilot chat.
Try a public filing read in VS Code Copilot
Inspect the request
Run the public filing request after connecting. A fresh response may return a later filing; compare its reporting period, filing date and source URL.
Recorded NexusTrade filing reference
NexusTrade MCP sec_edgar returned this listing in Codex on 2026-10-12. Use it as a reference when checking your own connection.
Show the table · 5 rows, 2 columns
| Returned field | Recorded result |
|---|---|
| Company | Apple Inc. |
| Form | 10-Q |
| Filing date | 2026-07-31 |
| Period ended | 2026-06-27 |
| Accession | 0000320193-26-000020 |
No matching rows. Clear the filter to see all records.
Choose a separate next task
These guides are independent choices after the connection check. Review any proposed paid research, historical test or portfolio change before authorizing it.
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.
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.
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.
Optional: check the account before owned-record changes
Optional: verify an owned portfolio before changes
Skip this step if you only want to inspect the public filing in the next step. Before reading or changing an owned portfolio, ask for a read-only list, inspect one returned ID with get_portfolio and compare its name, strategies and deployment type. An authenticated empty list is valid for a new account.
What you should see: For owned records, you have the intended account response or an authenticated empty response. Resolve an account mismatch before saving anything. Public filing inspection does not require an owned-portfolio read.
- Identity boundary
- A server list or public filing read does not verify access to your owned portfolios.
Use only NexusTrade read tools. Call fetch_portfolios, then get_portfolio with one returned portfolio ID. Report the ID, name, strategies and deployment type. If the authenticated list is empty, report that result. Do not create, edit, backtest, deploy or place orders.
No comments yet.