Tradewink MCP Guide: Connect @tradewink/mcp to Your AI Assistant
Set up the Tradewink MCP server (@tradewink/mcp) for research and paper trading on US stocks and ETFs. Covers OAuth setup, client config, safety limits, and what tools are unavailable.
The idea, illustrated
Explore the ideas visually
Step through the key sections, then read the complete guide below.
Step 1 of 4: Quick answer. Paused.
Put this into practice with a watchlist
Build a watchlist, then review each signal’s entry, stop, target, and reasoning. Broker access is optional.
Starter watchlist: SPY, QQQ, AAPL.
Starter examples. Not recommendations; you can edit them before anything is saved.
Public subscriptions are paper-only. Live beta enrolment, copy-trading expansion, and live MCP orders are frozen; a paid plan does not unlock them.
Tradewink MCP is the @tradewink/mcp package: a Model Context Protocol server that connects a supported AI assistant to Tradewink research and paper workflows for US stocks and ETFs. You authorize once, then ask the assistant to review a watchlist, inspect research, or prepare a paper order you confirm.
This guide is the product-specific setup path. For category context, see trading MCP servers and TradingView MCP.
Quick answer
Install with npx @tradewink/mcp setup (or add the server manually), complete OAuth when prompted, and keep every trading action on paper confirmation. Public Tradewink plans are paper-only. Tools return general research, not personalized investment advice.
What MCP changes in the workflow
Without MCP, you bounce between browser tabs and chat. With MCP, the assistant can call Tradewink tools in-process after you approve the connection. That does not make the assistant a broker, and it does not enable live public execution. It shortens research loops while leaving confirmation with you.
Install options
Automatic setup
npx @tradewink/mcp setup
The setup command detects installed clients and writes MCP config for them. Re-run after adding a new client.
Manual example (Cursor)
Add to .cursor/mcp.json or ~/.cursor/mcp.json:
{
"mcpServers": {
"tradewink": {
"command": "npx",
"args": ["-y", "@tradewink/mcp"]
}
}
}
Claude Code example: claude mcp add tradewink -- npx -y @tradewink/mcp. See the package README for Claude Desktop, VS Code, Windsurf, and Codex paths.
Authorization
Interactive use relies on OAuth 2.1. The first tool call opens a browser window to authorize your tradewink.com account. Tokens cache under ~/.tradewink/mcp/ and refresh automatically. Do not paste session cookies into chat logs.
For headless hosts that cannot open a browser, the README documents an API-key env path. Treat that secret like a password: never commit it, never put it in a prompt, rotate if exposed.
Safety boundaries (read before first call)
- Coverage: US stocks and ETFs research and paper trading.
- Orders: paper orders you confirm — not "autonomous live trading."
- Live MCP orders: disabled under current gates; a paid plan does not unlock them.
- Raw quotes, history, movers, and screener tools may appear in the tool table as currently unavailable while public raw market data remains off.
- Outputs are research context. You still verify material facts before acting.
Put the setup on a watchlist first
Use the rules in this guide to evaluate a signal’s entry, stop, target, and reasoning before deciding what, if anything, to do.
Starter watchlist: SPY, QQQ, AAPL.
Starter examples. Not recommendations; you can edit them before anything is saved.
Public subscriptions are paper-only. Live beta enrolment, copy-trading expansion, and live MCP orders are frozen; a paid plan does not unlock them.
Sensible first prompts
After auth succeeds, try tasks that stay review-first:
- "List my Tradewink watchlist and summarize why each ticker is there."
- "Show the latest signal reasoning for TICKER and list missing fields."
- "Draft a paper order ticket for review — do not submit until I confirm."
- "What would invalidate this idea based on the written stop?"
Avoid prompts that ask the model to guarantee profits, hide rejects, or bypass confirmation.
Pairing with delivery and Autopilot
MCP is one interface. Discord/web delivery is another. Paper Autopilot is a separate automation surface that still stays paper on public plans — see paper Autopilot explained. You can use MCP to explain a setup, then practice the ticket manually with the paper trading guide or Claude/Codex signal workflows.
Troubleshooting
- Auth loop: clear cached tokens only if instructed by the README; then re-authorize.
- Tool missing / unavailable: check whether the tool is gated (raw market data) rather than assuming install failure.
- Wrong account: confirm the OAuth user matches the Tradewink login you intended.
- Client not detecting server: restart the client after config changes; verify JSON syntax.
Where to go next
Product overview: /mcp. Signals hub: /signals. Pricing and plan limits: /pricing. Keep the public claims mindset: paper-first, explainable research, no fabricated track records in prompts or posts.
Public subscriptions are paper-only. Use paper practice and your own rules before any live decision. Educational information only, not personalized investment advice.
Frequently Asked Questions
What is @tradewink/mcp?
It is Tradewink's Model Context Protocol server that lets supported AI assistants call Tradewink research and paper-trading tools for US stocks and ETFs after OAuth.
Does Tradewink MCP place live trades?
Public plans are paper-only. Orders are paper orders you confirm. Live MCP orders stay disabled under current product gates.
Do I need an API key?
Interactive clients use OAuth 2.1 in the browser. Headless machines may use a configured API key only when a browser cannot open.
Are quotes and screeners available via MCP?
Raw market-data tools may be listed as currently unavailable while public raw market data remains disabled. Check the live tool table in the package README.
Which assistants work?
The setup command targets common MCP clients such as Claude Code, Claude Desktop, VS Code Copilot, Cursor, Windsurf, and OpenAI Codex CLI. Follow the package README for current support.
Read next
Keep learning with a related guide before putting an idea on your watchlist.
Trading MCP Servers: Connect AI to Market Data
What a trading MCP server is, what tools it exposes, safety limits to look for, and how to set up Tradewink's free MCP in Claude, Cursor or Codex.
TradingView MCP: What It Is and How to Set One Up
What a TradingView MCP setup means, what MCP servers can and cannot do with TradingView, safety limits for AI agents, and a paper-first setup checklist.
Use Tradewink with Claude, Codex, and the signals API
Connect an AI assistant through MCP, retrieve signal records through the API, and use a preview-first workflow with explicit order approval.
Try AI signals on your watchlist
Send yourself a signal preview, then add tickers to see ranked entries, exits, and risk notes in Tradewink.
Sources cited in this guide
- Model Context Protocol (modelcontextprotocol.io)
Tradewink builds explainable AI trading signals for US stocks and ETFs. Build a watchlist, see what Winkie rejected and why, and paper-track ideas before you decide. Public subscriptions are paper-only. Live beta enrolment, copy-trading expansion, and live MCP orders are frozen; a paid plan does not unlock them.
How this guide is reviewed
Tradewink reviews educational content against its documented market-data sources, risk controls, and product methodology. See our data sources and evaluation methodology for the evidence and limitations behind the platform, and our editorial standards for how guides are sourced, dated, and corrected.

Comments
Comments are reader opinions, not investment advice. A moderator reviews your first comment before it appears, and moderators can remove any comment later.
Loading comments…