TradeOS MCP Server

If you already use TradeOS, the tradeos mcp server is the piece that lets your assistant work with it directly. TradeOS MCP: ticker search, My Agent, chart TA, macro news. npm stdio or HTTP.

What the server does

TradeOS MCP lets you connect TradeOS trading intelligence to MCP-compatible AI tools, so your assistant can analyze markets, search tickers, compare spreads, use macro context, and manage custom trading agents directly from natural-language prompts.

This repo publishes @tradeos/tradeos-mcp on npm: a stdio MCP bridge that proxies tools to TradeOS Streamable HTTP (mcp-call). You can connect in two ways:

Installation

@tradeos/tradeos-mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• Pre — release tags (v1.0.0-beta.1) publish with an npm dist-tag matching the prerelease label (e.g. beta)
• Mode — Best for
• Item — Value
• Package — @tradeos/tradeos-mcp
• Script — Purpose
• Symptom — Likely cause
• Cursor — Edit user config ~/.cursor/mcp.json (Windows: %USERPROFILE%.cursor\mcp.json):

Credentials and setup notes

Configuration is passed through the environment: TRADEOS_ACCESS_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

• Node.js 18+ - A TradeOS account with MCP API access - For npm stdio: ability to run a local install (see Windows notes) ---

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. TradeOS's toolset — Pre, Mode, Item and 4 more — is a fair guide to whether it matches your workflow. It is maintained by TradeOS-AI; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.