TradeOS (test)

io.github.TradeOS-AIPublished by GitHub account TradeOS-AIv1.0.0-alpha.6Updated Oct 27, 2026

[TEST] TradeOS MCP bridge: ticker search, My Agent, chart TA, macro news. npm or HTTP.

VerifiedStreamable HTTPWeb executableFinanceData & Analytics

Overview

AI-generated overview

TradeOS MCP connects an assistant to TradeOS trading intelligence for ticker search, market analysis, spread comparison, macro news and custom trading agents.

What you can do
  • Search tickers and look up market instruments
  • Analyze charts and technical indicators
  • Compare spreads and pull macro news context
  • Create and manage custom trading agents (My Agent)
  • Proxy all of the above to the TradeOS remote endpoint over HTTP or a local stdio bridge
When to use it
Useful when you want an assistant to research markets, compare spreads or run technical and macro analysis from natural-language prompts, and to keep custom trading agents in one place. Best for users who already have a TradeOS account with MCP API access.
Requirements
Either the remote HTTP endpoint with browser OAuth handled by the client, or the npm package run locally with Node.js 18+ and the TRADEOS_ACCESS_TOKEN environment variable obtained from the OAuth helper. A TradeOS account with MCP API access is required. On Windows the README advises a fixed local install instead of npx.
Before you install
The npm mode needs a TradeOS access token (TRADEOS_ACCESS_TOKEN) that must be kept out of version control and client configs shared with others. The server can create and manage trading agents, so changes may affect your TradeOS account. Market analysis is not investment advice, and prompts and data are sent to the TradeOS service.

Installation

In SourceWeft

  1. Open TradeOS (test) in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.TradeOS-AI%2Ftradeos-mcp-test/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "tradeos-test": {
      "type": "http",
      "url": "https://ai.tradeos.xyz/api/agent/mcp-call"
    }
  }
}

README

tradeos-mcp

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.

Overview

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:

ModeBest forAuth
HTTP (recommended)Cursor, Claude Code, most MCP clientsBrowser OAuth in the client
npm stdioClients that only support command / stdioTRADEOS_ACCESS_TOKEN env var

Production endpoint (both modes ultimately call this):

text
https://ai.tradeos.xyz/api/agent/mcp/mcp-call

Product docs: TradeOS MCP integration & usage

Prerequisites

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

Option A — HTTP (recommended)

No npm install. The client handles OAuth.

Cursor

Edit user config ~/.cursor/mcp.json (Windows: %USERPROFILE%\.cursor\mcp.json):

json
{  "mcpServers": {    "tradeos": {      "url": "https://ai.tradeos.xyz/api/agent/mcp/mcp-call"    }  }}

Save, restart Cursor (or refresh MCP in Settings → MCP), then complete OAuth when prompted.

Claude Code (plugin — recommended)

Use the bundled plugin in tradeos-skills/:

bash
claude --plugin-dir ./tradeos-skills

Then complete OAuth and run /tradeos:analyze. Full plugin workflow (validate, community marketplace submit): tradeos-skills/README.md — aligned with Claude plugin docs.

Option B — npm stdio bridge

Use when your client requires a local process (command + stdio).

1. Install locally

Do not rely on npx inside MCP on Windows (cache/path issues). Install once to a fixed directory:

bash
mkdir -p ~/tradeos-mcp-run   # Windows: mkdir %USERPROFILE%\Downloads\tradeos-mcp-runcd ~/tradeos-mcp-run         # Windows: cd %USERPROFILE%\Downloads\tradeos-mcp-runnpm install @tradeos/tradeos-mcp

Pin a version if you prefer, e.g. @tradeos/[email protected].

2. Get TRADEOS_ACCESS_TOKEN

Run the OAuth helper (opens browser → log in on TradeOS → prints token):

bash
# Linux / macOSnpx -y -p @tradeos/tradeos-mcp tradeos-mcp-oauth
# Or subcommand on main bin:npx -y @tradeos/tradeos-mcp oauth
# Or, from your install directory:node node_modules/@tradeos/tradeos-mcp/scripts/fetch-token.mjs

Windows (recommended):

cmd
cd /d %USERPROFILE%\Downloads\tradeos-mcp-runnode node_modules\@tradeos\tradeos-mcp\scripts\fetch-token.mjs

Copy the printed JWT (eyJ...). For local development of this repo, copy into .env:

bash
cp .example.env .env# TRADEOS_ACCESS_TOKEN=eyJ...

End users who only npm install the package do not need .env — set the token in MCP client config (mcp.json) instead.

Do not commit tokens to git.

3. Configure Cursor

json
{  "mcpServers": {    "tradeos-npm": {      "command": "node",      "args": [        "C:/Users/YOU/Downloads/tradeos-mcp-run/node_modules/@tradeos/tradeos-mcp/build/index.js"      ],      "env": {        "TRADEOS_ACCESS_TOKEN": "eyJ..."      }    }  }}

Replace YOU and the path with your actual install location. Use forward slashes or escaped backslashes in JSON.

If Cursor cannot find node, set the full path:

json
"command": "C:/nvm4w/nodejs/node.exe"

Enable tradeos-npm in Settings → MCP. Status should show connected with tools listed.

4. Verify in terminal (optional)

Environment variables in mcp.json do not apply to your shell. Set the token in the same terminal session:

cmd
REM Windows CMDset TRADEOS_ACCESS_TOKEN=eyJ...node C:\Users\YOU\Downloads\tradeos-mcp-run\node_modules\@tradeos\tradeos-mcp\build\index.js
bash
# Linux / macOSexport TRADEOS_ACCESS_TOKEN=eyJ...node ~/tradeos-mcp-run/node_modules/@tradeos/tradeos-mcp/build/index.js

Success:

text
[tradeos-mcp] remote: https://ai.tradeos.xyz/api/agent/mcp/mcp-call[tradeos-mcp] stdio bridge ready

Press Ctrl+C to stop. Cursor starts its own process; you do not need to keep this terminal open.

Windows notes

  1. Use local node + install path in mcp.json, not npx, for MCP.
  2. If npm cache errors mention C:\Program Files\nodejs\node_cache, run once:
    cmd
    npm config set cache "%USERPROFILE%\.npm-cache"
  3. npx @pkg tradeos-mcp-oauth may run the wrong bin on Windows. Prefer:
    cmd
    npx -y -p @tradeos/tradeos-mcp tradeos-mcp-oauth
    or node .../scripts/fetch-token.mjs from your install directory.
  4. Clear a broken npx cache (quit Cursor first):
    cmd
    rmdir /s /q "%USERPROFILE%\.npm-cache\_npx"

npm package reference

ItemValue
Package@tradeos/tradeos-mcp
MCP Registry nameio.github.TradeOS-AI/tradeos-mcp
Bin: MCP bridgetradeos-mcp
Bin: OAuth tokentradeos-mcp-oauth
OAuth subcommandoauth on bin tradeos-mcp

Install:

bash
npm install @tradeos/tradeos-mcp

Development (this repo)

bash
git clone https://github.com/TradeOS-AI/tradeos-mcp.gitcd tradeos-mcpnpm cinpm run buildnpm run oauth:token    # browser OAuth → prints token (copy into .env if needed)npm run registry:verify
ScriptPurpose
npm run buildCompile stdio bridge to build/
npm run oauth:tokenBrowser OAuth → print token
npm run registry:verifyPre-publish checks (package.json ↔ server.json)
npm run registry:sync-version <ver>Sync version from release tag

Publishing (maintainers)

Push a version tag to trigger .github/workflows/publish-mcp.yml:

bash
git tag v1.0.0git push origin v1.0.0
  • Stable tags (v1.0.0) publish to npm latest and the MCP Registry.
  • Pre-release tags (v1.0.0-beta.1) publish with an npm dist-tag matching the prerelease label (e.g. beta).
  • Requires GitHub Actions secret NPM_TOKEN (Classic Automation token for @tradeos).

Verify on the registry API:

bash
curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=io.github.TradeOS-AI/tradeos-mcp"

Troubleshooting

SymptomLikely causeFix
TRADEOS_ACCESS_TOKEN is requiredToken not set in env / mcp.jsonRun oauth helper; set env in MCP config
unauthorized on connectExpired or invalid tokenRe-run oauth; paste fresh JWT (no Bearer prefix)
EPERM / node_cachenpm cache under Program Filesnpm config set cache "%USERPROFILE%\.npm-cache"
TAR_ENTRY_ERROR / 'tradeos-mcp' is not recognizednpx failed on WindowsLocal install + node path in mcp.json
MODULE_NOT_FOUND for node_modules/...Ran script from wrong directorycd to install dir or use absolute path
Token works in terminal, not in Cursormcp.json path or token mismatchMatch paths; restart Cursor / refresh MCP
MCP connects but no toolsWrong server enabledDisable broken localhost entries; use production HTTP URL or working tradeos-npm

Related

Source: README.md at commit 2b620e3

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0-alpha.6LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts