Summary

Two routes to one endpoint — take the HTTP one unless your client can't.

The HTTP configuration is a URL and nothing else, with the client running the login. The npm bridge exists for clients that only accept a `command`, and on Windows the README is emphatic about it: install into a fixed directory and point at `node` with an absolute path rather than relying on npx, which picks the wrong binary.

What it is

A connection to TradeOS trading intelligence. Point your client straight at the Streamable HTTP endpoint and let it handle OAuth, or run the npm package as a local stdio bridge that proxies to the same endpoint.

What you get

Market analysis, ticker search and spread comparison from a plain-language question
Macro context alongside the instrument you asked about
Custom trading agents you create and manage from the conversation
A Claude Code plugin in `tradeos-skills/` that adds an analyze command on top of the connection

Requirements

A TradeOS account with MCP API access. The HTTP route needs only the endpoint `https://ai.tradeos.xyz/api/agent/mcp/mcp-call` and a browser sign-in. The stdio route needs Node.js 18+, `npm install @tradeos/tradeos-mcp`, and `TRADEOS_ACCESS_TOKEN` — a JWT the bundled OAuth helper prints for you to paste into the client config.

Setup effort

One command plus a key — npm install @tradeos/tradeos-mcp, then supply credentials