TL;DR
Connect Claude Code to NexusTrade in your project, authenticate through /mcp and start with a public filing read. You can then choose a company brief, a historical backtest or a separate paper portfolio. These are different outputs: filing evidence supports a thesis, a backtest measures historical rule behavior, and paper history records simulated activity after deployment. Review the configuration before authorizing a test or portfolio change.
Connect Claude Code in the intended environment
claude mcp add --transport http nexustrade https://nexustrade.io/api/mcpScroll horizontally to read the full command, or copy it.
- Setup scope
- The command adds the server for the current project. Use the full guide if you need a connection across projects.
In your project terminal, run the command below. Start Claude Code with claude, enter /mcp and choose NexusTrade to complete browser sign-in. Return to /mcp to inspect the connection and available tools.
Try a public filing read in Claude Code
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.
Give Claude Code a trading workspace
Claude Code works from your terminal and repository. Use it to keep the research brief, strategy configuration and review notes together while NexusTrade provides account-scoped data and trading operations.
Start with a narrow question and a paper candidate. The agent can author code, but the strategy’s universe, entry rule, sizing, exit rule and validation period still need to be explicit.
Write the first research brief
A useful request names the instrument, test period, capital, benchmark and stopping point. Ask Claude to show its configuration before it submits a test, then inspect results without approving a deployment implicitly.
Draft a daily SPY strategy with explicit entry, position sizing and exit rules. Show the complete configuration first. After I approve it, run one historical backtest over a fixed period, compare it with buy-and-hold SPY, and report warnings and drawdown. Do not deploy it.Separate three kinds of evidence
Use filing and news sources to assess a thesis. Use historical backtests to assess rule behavior over past data. Use a separately identified paper deployment to observe simulated execution going forward. A strong historical result is not a measured live outcome.
Check a missing tool or failed account read
If NexusTrade is missing from /mcp, check the server registration and URL. If it appears but the account read fails, complete browser authentication and inspect the returned error before retrying. Confirm the returned portfolio name and ID against NexusTrade. A new account can return an empty portfolio list; it should not produce an invented portfolio.
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.