Luxalgo MCP Server

What luxalgo-mcp-server does

The luxalgo-mcp-server MCP server gives an AI agent structured access to several parts of the LuxAlgo ecosystem. Its library tools cover trading and technical-analysis concepts, indicator metadata, publicly available source code, families, tags, and paginated catalog browsing. Search supports concept aliases, while list operations can filter and sort indicator results.

Authenticated tools expose the signed-in LuxAlgo account’s plan tier, entitlements, and basic profile information. Trade Journal tools read accounts, performance dashboards, calendars, breakdowns, trades, notes, and annotation vocabularies. They can also write journal data by adding manual trades, updating trade annotations, and creating or moving day notes.

The server also includes read-only broker access when run locally with supported credentials. Broker tools report connected accounts, balances, open positions, trade history, and aggregate statistics. The edge_symbols tool reports the symbols, sessions, coverage windows, and build information available from the hosted edge-statistics store.

How it works

The hosted service is available at https://mcp.luxalgo.com/mcp over MCP-compatible HTTP. Hosted library access is keyless. Account and journal operations use LuxAlgo authentication, while locally configured broker operations use credentials supplied through the MCP client environment.

For local use, the npm package runs through stdio and exposes the hosted tool set while enabling broker tools. Broker credentials remain in the local client configuration; the README specifies read-only access and says those keys are not sent to LuxAlgo. A broker becomes available when all of its required environment variables are configured.

Setup and configuration

Add the hosted URL to an MCP client, or run the npm package locally with npx -y @luxalgo/mcp. Cursor, Claude Desktop, Claude Code, VS Code, Windsurf, Zed, LM Studio, and Gemini CLI are documented setup targets. The hosted configuration needs only the server URL.

Local broker configuration uses names in the form BROKERS_<BROKER>_<FIELD>, such as BROKERS_ALPACA_API_KEY, BROKERS_ALPACA_API_SECRET, or BROKERS_HYPERLIQUID_WALLET_ADDRESS. Use broker_setup to inspect supported brokers and their exact variable names. No broker variables are needed if broker tools are not required.

Tools and capabilities

The luxalgo-mcp-server MCP server includes:

• Library search, concept and indicator retrieval, source-code retrieval, family and tag discovery, and filtered catalog browsing.
• LuxAlgo account entitlement and profile lookup.
• Journal account discovery, dashboard metrics, calendar views, performance breakdowns, trade search, trade detail, day detail, notes, and annotation tags.
• Journal writes for manual trades, trade updates, day notes, and note changes.
• Broker setup guidance, account balances, positions, trade history, aggregate statistics, and cache refresh.
• Hosted symbol coverage metadata through edge_symbols.

Limitations and notes

The hosted endpoint does not provide local broker tools; use the local stdio deployment for those connections. Broker access is read-only, although journal tools can create and modify journal records. Library source code is fetched only when publicly served and requested. Journal filters that use account IDs require first calling journal_list_accounts to obtain those IDs. The server is most relevant to the Finance & Fintech category when an agent needs LuxAlgo-specific research, journaling, or account context rather than general market execution.