
Tradewink
io.github.leancoderkavyPublished by GitHub account leancoderkavyv0.3.0Updated Oct 28, 2026
MCP for Tradewink trading signals and watchlists. Not financial advice.
Overview
Tradewink MCP gives an assistant access to Tradewink trading signals, market data, watchlists, portfolio and order tools for a Tradewink account.
- What you can do
- Read account, positions and live portfolio data
- Manage watchlists: list, add and remove tickers
- Fetch market data: quotes, batch quotes, history, news, analyst ratings, earnings and technical analysis
- Screen markets for movers and screener results
- Place and close orders, list open orders and cancel orders
- Review strategies, trade history, analytics, executions and audit log
- When to use it
- Useful when you want an assistant to research markets, check a Tradewink portfolio, manage watchlists or act on Tradewink signals inside a chat client. The README also describes pairing it with a separate broker server for execution.
- Requirements
- A Tradewink account and authorization: OAuth 2.1 browser approval on first run, or a manual API key in TRADEWINK_API_KEY. The README's local package runs via npx (Node.js) over stdio and proxies to the remote endpoint; the manifest lists a remote streamable HTTP endpoint requiring an Authorization bearer token. Optional TRADEWINK_ENDPOINT or --endpoint overrides the server address.
Installation
In SourceWeft
- Open Tradewink in the dashboard and add it to a workspace.
- Connect Authorization token credentials. They are stored privately and never shown on public pages.
- 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.leancoderkavy%2Ftradewink/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.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"tradewink": {
"type": "http",
"url": "https://tradewink-mcp.fly.dev/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}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:
This detects and configures: Claude Code, Claude Desktop, VS Code (Copilot), Cursor, Windsurf, and OpenAI Codex CLI.
Manual Setup
Claude Code
Claude Desktop
Add to your claude_desktop_config.json:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
VS Code (Copilot)
Add to your VS Code settings (.vscode/settings.json or global settings):
Cursor
Add to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):
OpenAI Codex CLI
Windsurf
Add to ~/.codeium/windsurf/mcp_config.json:
Any MCP-Compatible Client
Any client that supports MCP stdio servers works:
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:
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:
- Get a Tradewink signal, such as market movers plus
get_technical_analysisoranalyze_tickerforAAPL. - 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.
- 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
Configuration
You can also pass --endpoint as a CLI argument:
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.
License
MIT
Source: README.md at commit 3cf1420
Tools
0Version history
1- v0.3.0LatestSep 24, 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