TradeOS (test) — Claude Code MCP server: setup guide
Brings TradeOS market intelligence into AI assistants. It handles ticker searches, spread comparisons, and chart technical analysis directly from chat.
claude mcp add --transport http tradeos-mcp-test https://ai.tradeos.xyz/api/agent/mcp-callWhat TradeOS (test) does
This server acts as a bridge between your editor and the TradeOS analytics platform. It equips your assistant with tools to inspect price charts and evaluate live bid-ask spreads. You can also dispatch queries to your personal trading agents without leaving the terminal.
Connection works either over remote HTTP or through a local stdio process provided by @tradeos/tradeos-mcp. Running locally requires Node.js 18 or newer. Without a valid TRADEOS_ACCESS_TOKEN passed in the environment, the stdio bridge rejects incoming tool calls.
On Windows, executing the stdio bridge via npx often breaks due to npm cache path conflicts. Installing the package into a fixed local folder and referencing the built entrypoint directly keeps the connection stable.
What it helps with
- search ticker symbols and compare market spreads
- generate technical analysis for asset charts
- fetch recent macroeconomic developments
- send prompts to custom TradeOS agents
Example prompts for the agent
- Check current spreads and market conditions for SOL.
- Run technical chart analysis on the daily BTC timeframe.
- Summarize major macroeconomic headlines affecting markets today.
How to install TradeOS (test)
1Platform CLI: remote server
claude mcp add --transport http tradeos-mcp-test https://ai.tradeos.xyz/api/agent/mcp-call2Platform CLI
claude mcp add --env TRADEOS_ACCESS_TOKEN=<TRADEOS_ACCESS_TOKEN> --transport stdio tradeos-test -- npx -y @tradeos/tradeos-mcp-testReplace <…> with your own values
1Platform CLI: remote server
codex mcp add tradeos-test --url https://ai.tradeos.xyz/api/agent/mcp-call2Platform CLI
codex mcp add tradeos-test --env TRADEOS_ACCESS_TOKEN=<TRADEOS_ACCESS_TOKEN> -- npx -y @tradeos/tradeos-mcp-testReplace <…> with your own values
Config file
{
"mcpServers": {
"tradeos-test": {
"url": "https://ai.tradeos.xyz/api/agent/mcp-call"
}
}
}{
"mcpServers": {
"tradeos-test": {
"command": "npx",
"args": [
"-y",
"@tradeos/tradeos-mcp-test"
],
"env": {
"TRADEOS_ACCESS_TOKEN": "<TRADEOS_ACCESS_TOKEN>"
}
}
}
}Replace <…> with your own values
Config file
{
"servers": {
"tradeos-test": {
"type": "http",
"url": "https://ai.tradeos.xyz/api/agent/mcp-call"
}
}
}{
"servers": {
"tradeos-test": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@tradeos/tradeos-mcp-test"
],
"env": {
"TRADEOS_ACCESS_TOKEN": "<TRADEOS_ACCESS_TOKEN>"
}
}
}
}Replace <…> with your own values
1Platform CLI: remote server
gemini mcp add -t http tradeos-test https://ai.tradeos.xyz/api/agent/mcp-call2Platform CLI
gemini mcp add -e TRADEOS_ACCESS_TOKEN=<TRADEOS_ACCESS_TOKEN> tradeos-test npx -y @tradeos/tradeos-mcp-testReplace <…> with your own values
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about TradeOS (test)
How to install TradeOS (test) in Claude Code?
Run claude mcp add --transport http tradeos-test https://ai.tradeos.xyz/api/agent/mcp-call in your terminal. Then complete the browser OAuth step when prompted.
What does TradeOS (test) do?
It gives your assistant access to trading intelligence data. The model can inspect charts, query tickers, and incorporate macro news into its answers.
Should I choose HTTP or npm stdio?
The HTTP mode is recommended because it bypasses local package management and relies on browser login. Use stdio only if your MCP client strictly requires a local process.
