AI trading workflows

Connect Meta Muse to NexusTrade for stock research

Create a NexusTrade custom connector in Muse, sign in, check a read-only tool and build a dated company research brief.

Product
Meta Muse personal agent
Connection
Custom connector
First task
Read-only stock research

1. Request the custom connector in Muse

Open a conversation in the Muse personal agent app. For a service outside its built-in Connector list, Meta documents asking Muse to create a Custom Connector. Send the connection request below. Muse Code is a separate developer client; its settings file is not the setup route used here.

text
Create a Custom Connector named NexusTrade. Use the remote Streamable HTTP MCP endpoint https://nexustrade.io/api/mcp. Read the server authentication discovery and tool schemas. Guide me through NexusTrade sign-in and list the available tools. Do not place orders, activate portfolios, run backtests or change account settings.

2. Complete NexusTrade authentication

NexusTrade publishes the same hosted MCP endpoint used by its other remote clients. It supports OAuth discovery. Follow the sign-in and consent flow the connector presents, select the intended NexusTrade account and review the requested access. Keep credentials out of the conversation; Muse provides a Secure Credentials Store for custom connectors.

If sign-in loops or the connector cannot discover authentication, check that the endpoint ends in /api/mcp and ask Muse to show the discovery error. Use the NexusTrade developer documentation to resolve the error before proceeding. A generated client or a saved connector alone does not confirm account access.

3. Check a read-only tool result

Ask Muse to list the tools returned by NexusTrade and call fetch_portfolios with include_live=false and include_positions=false. Pass one returned portfolioId as portfolio_id to get_portfolio; inspect portfolio.portfolioId, portfolio.type and portfolio.strategies from the response. Check that identity against the account you intended to connect. An empty portfolio list can be valid for a new account; an authentication error or a missing tool result is not a successful check.

Keep approval enabled for account changes. Meta lets you change when Muse asks for approval in Settings. To disconnect a connector, open Settings, then Connectors.

text
Show the tools returned by the NexusTrade connector. Use an available read-only tool to read my account identity or list existing portfolios without updating them. Show the returned result and any error. Do not infer account data from web pages or create anything.

4. Build a dated company brief

Use AAPL as a first test and request dated company data. Open the cited sources yourself and confirm issuer identity, reporting period and publication date. The brief should separate reported facts, interpretation and missing information. If a tool lacks a field, leave that field unresolved.

text
Using the NexusTrade connector, research AAPL. Show the company identity, dated fundamentals available from the tools, fiscal periods and source links. Follow primary filings where available. Separate reported facts from interpretation. State missing fields or failed requests. Return a research brief and the next question to investigate; do not place orders, activate a portfolio or launch a backtest.

5. Review before testing a rule

Compare the returned fundamentals with their dates and linked filings. Resolve a missing source or an account mismatch before using the brief. If you decide to test a strategy, define explicit rules and assumptions in NexusTrade, then inspect the historical result separately from any forward paper observation.

Choose the task you want to finish

Use the research guide for a dated company brief, the backtest guide for one fixed historical candidate, or the paper guide to observe a separately identified simulated book. Each guide shows how to check the connection, retain the accepted operation ID and recover from a failed request.

Review a brokerage deployment separately

Public and Tradier have native NexusTrade account connection and strategy-port flows described below. Public also offers its own external MCP route. The Robinhood guide uses Claude Code with separate NexusTrade and Robinhood MCP servers; it does not imply that this client already has a verified native Robinhood connection. Broker account selection, order approval and a verified stop remain separate from paper observation.

Continue exploring