Back to Browse

Tradewink MCP Server

Developer ToolsLow Risk9.9MCP RegistryRemote
Free

Server data from the Official MCP Registry

MCP for Tradewink trading signals and watchlists. Not financial advice.

About

MCP for Tradewink trading signals and watchlists. Not financial advice.

Remote endpoints: streamable-http: https://tradewink-mcp.fly.dev/mcp

Security Report

9.9
Low Risk9.9Low Risk

Valid MCP server (2 strong, 4 medium validity signals). 1 code issue detected. No known CVEs in dependencies. Imported from the Official MCP Registry. 1 finding(s) downgraded by scanner intelligence.

Endpoint verified · Requires authentication · 2 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Found in Source Code

Found by scanning the linked source code. This listing connects to a hosted endpoint, so none of this runs on your machine: it describes what the server software does where it is hosted.

file_system

Applies to the server that hosts this plugin, not to your machine.

env_vars

Applies to the server that hosts this plugin, not to your machine.

Shell Command Execution

Runs commands on the server that hosts it, not on your machine.

HTTP Network Access

Connects to external APIs or services over the internet.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "io-github-leancoderkavy-tradewink": {
      "url": "https://tradewink-mcp.fly.dev/mcp"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

@tradewink/mcp

Connect any LLM to Tradewink signals and analysis via the Model Context Protocol, then pair it with Alpaca for agent-driven execution.

Get real-time quotes, manage your portfolio, execute trades, run AI analysis, and more — all from your AI assistant.

Quick Start

1. Configure Your Client

No API key needed — @tradewink/mcp uses OAuth 2.1. The first time you run it, a browser window opens to authorize your tradewink.com account. Tokens are cached in ~/.tradewink/mcp/ and refresh automatically.

Automatic Setup (Recommended)

Auto-detect and configure all your installed AI clients with one command:

npx @tradewink/mcp setup

This detects and configures: Claude Code, Claude Desktop, VS Code (Copilot), Cursor, Windsurf, and OpenAI Codex CLI.

Manual Setup
claude mcp add tradewink -- npx -y @tradewink/mcp

Add to your claude_desktop_config.json:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "tradewink": {
      "command": "npx",
      "args": ["-y", "@tradewink/mcp"]
    }
  }
}

Add to your VS Code settings (.vscode/settings.json or global settings):

{
  "mcp": {
    "servers": {
      "tradewink": {
        "command": "npx",
        "args": ["-y", "@tradewink/mcp"],
        "env": {
          "TRADEWINK_API_KEY": "tw_your_key_here"
        }
      }
    }
  }
}

Add to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):

{
  "mcpServers": {
    "tradewink": {
      "command": "npx",
      "args": ["-y", "@tradewink/mcp"]
    }
  }
}
codex mcp add tradewink -- npx -y @tradewink/mcp

Add to ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "tradewink": {
      "command": "npx",
      "args": ["-y", "@tradewink/mcp"]
    }
  }
}

Any client that supports MCP stdio servers works:

npx @tradewink/mcp

2. Start Using It

Ask your AI assistant things like:

  • "What's my account balance?"
  • "Show me my open positions"
  • "Get a quote for AAPL"
  • "What are today's top market movers?"
  • "Analyze NVDA with AI"
  • "Add TSLA to my watchlist"
  • "What are my active trading strategies?"
  • "Show my trade history for the past week"

Tradewink Signals + Alpaca Execution

Use tradewink-mcp as the signal and research layer for your agent, and the official Alpaca MCP server as the execution layer. This keeps Tradewink's market context, screeners, technical analysis, and AI insights separate from the broker tools that place orders.

This is an integration pattern: no Alpaca order-execution code is added to tradewink-mcp.

Add both servers to the same Claude Desktop or Cursor MCP configuration:

{
  "mcpServers": {
    "tradewink": {
      "command": "npx",
      "args": ["-y", "@tradewink/mcp"]
    },
    "alpaca": {
      "command": "uvx",
      "args": ["alpaca-mcp-server"],
      "env": {
        "ALPACA_API_KEY": "your_paper_api_key",
        "ALPACA_SECRET_KEY": "your_paper_secret_key",
        "ALPACA_PAPER_TRADE": "true"
      }
    }
  }
}

The official Alpaca server uses uvx and defaults to paper trading; the explicit ALPACA_PAPER_TRADE setting above makes the safety boundary visible. Create paper keys in Alpaca's dashboard and keep credentials in your local MCP client configuration. See the Alpaca MCP setup and configuration docs.

Example agent workflow

Ask the agent to:

  1. Get a Tradewink signal, such as market movers plus get_technical_analysis or analyze_ticker for AAPL.
  2. Check the current quote and paper-account buying power, define a maximum loss/risk budget, and size the position from that budget rather than blindly copying a signal.
  3. If the thesis and sizing pass review, place a paper order with Alpaca's place_stock_order, then report the order details and risk controls.

For example: “Use Tradewink to find a bullish AAPL setup, explain the signal and invalidation level, size it to no more than 1% of my paper account, and—only after I confirm—place the corresponding paper order through Alpaca.”

Tradewink signals are informational and may be incomplete, delayed, or wrong. Trading involves substantial risk, including loss of principal; an agent can misunderstand data or instructions. Review every signal, size, and order yourself, and do not switch ALPACA_PAPER_TRADE to false until you understand and accept the risks.

Available Tools

CategoryTools
Accountget_account, get_positions, get_portfolio_live
Watchlistget_watchlist, add_to_watchlist, remove_from_watchlist
Market Dataget_quote, batch_quote, get_historical, get_news, get_analyst_ratings, get_earnings, get_technical_analysis
Screenerget_market_movers, get_screener_results
Tradingplace_order, close_position, get_open_orders, cancel_order
Strategiesget_strategies, get_strategy, get_exit_strategies, get_sell_confidence
Trade Historyget_trades, get_trade_analytics, get_trade_executions, get_audit_log
AI Analysisask_ai, analyze_ticker, get_insights
Preferencesget_preferences, list_preference_options, update_preference, reset_preference
Schedulingschedule_analysis, list_scheduled_jobs, cancel_scheduled_job

Configuration

Environment VariableRequiredDefaultDescription
TRADEWINK_API_KEYNo—Skip the OAuth flow and use a manual API key (tw_...). Useful for headless CI.
TRADEWINK_ENDPOINTNohttps://tradewink-mcp.fly.dev/mcpCustom MCP server endpoint

You can also pass --endpoint as a CLI argument:

npx @tradewink/mcp --endpoint https://custom.example.com/mcp

Auth

OAuth 2.1 is the default. On first run a browser window opens to tradewink.com/mcp/authorize, you approve the request, and the bridge caches an access + refresh token pair at ~/.tradewink/mcp/<host>.json. Access tokens live for 1 hour and refresh automatically for 60 days. You can revoke access anytime from your dashboard.

Set TRADEWINK_API_KEY=tw_... to skip OAuth and use a manual key (e.g. for CI, sandboxes, or pinned long-lived access).

How It Works

This package runs a local MCP server over stdio and proxies every tool/resource call to the remote Tradewink MCP server over HTTPS. OAuth tokens are minted per-device and scoped to your account.

Your LLM Client ←stdio→ @tradewink/mcp ←HTTPS (Bearer token)→ Tradewink MCP Server

License

MIT

Reviews

No reviews yet

Be the first to review this server!