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.
The idea, illustrated
Explore the ideas visually
Step through the key sections, then read the complete guide below.
Step 1 of 4: Choose MCP or the signal API. 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 Claude Codex: An integration connects software permissions and data; it does not establish that a trading proposal is correct.
Use an AI assistant to explain the idea and organize your checks. Keep research, signal retrieval, and order permissions separate so you know what the assistant can actually do.
Before installing tools or choosing a plan, inspect a public signal record. Use the timestamp, reasoning, and missing fields to decide whether this is the kind of research you want in your own workflow.
Choose MCP or the signal API
MCP: Connects compatible clients to permitted strategy, analysis and account tools. Raw quote, historical-data, mover and screener tools return unavailable while raw market-data redistribution is disabled. Do not ask the assistant to bypass that restriction or fabricate a current quote. MCP access does not establish permission for every tool or account workflow.
REST signals API: Retrieves published signal records for your own application. This requires Pro or Elite API access. The current MCP tool set does not include a dedicated subscriber signal-feed tool. Strategy results are not interchangeable with delivered signal records.
For a no-code explanation, open a signal and provide its non-secret contents to your assistant. Include its ID, timestamp, symbol, asset class, direction, levels, and reasoning. Ask it to identify missing facts instead of guessing.
Connect your assistant
Install Node.js with npm if your computer does not already have it. For Claude Code, run:
claude mcp add tradewink -- npx -y @tradewink/mcp
For Codex CLI, run:
codex mcp add tradewink -- npx -y @tradewink/mcp
The package also provides an interactive setup helper for supported installed clients:
npx @tradewink/mcp setup
On first use, complete Tradewink's browser authorization and review the account you are authorizing. Restart or reconnect your client if needed, then confirm the Tradewink tools appear. Use MCP setup for other clients and the current connection details. Claude's official MCP documentation explains client scopes and approvals.
Keep tool approvals enabled. Do not select an unrestricted auto-approve mode for trading tools. Never put broker secrets or account tokens into a prompt.
Start with a research-only prompt
Explain this Tradewink signal in plain language. Check its symbol, timestamp, asset, proposed entry, invalidation, and target. Separate facts from assumptions. Compare with current data if available. Tell me what is missing and whether the original setup is stale. Do not place orders, change preferences, or enable trading.
Retrieve actual signals in your application
Generate or manage your eligible signal API key in API Keys. Store it server-side. This read-only POSIX-shell example expects the key in an environment variable; it does not place a trade:
curl --fail --silent --show-error \
-H "Authorization: Bearer $TRADEWINK_SIGNAL_API_KEY" \
"https://tradewink-signals.fly.dev/api/v1/signals?limit=5"
The response contains a signals array. The endpoint supports ticker, signal_type, and limit filters. Pass only relevant signal fields to your assistant; do not pass the authorization header. A 401 means authentication needs attention; an entitlement rejection requires checking the API plan. Do not retry either indefinitely.
Polling this endpoint is your application's job; connecting MCP does not create a background signal subscription. Deduplicate by signal ID and evaluate age before proposing any action. If you want push delivery instead, use webhooks.
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.
Preview an order before any submission
After independently choosing your paper account and proposed ticket, ask:
Verify which broker account and paper/live environment are selected. If you cannot verify them, stop. Prepare a place_order preview with confirm=false for the exact ticket I provide. Show the symbol, side, quantity, type, price constraints, and estimated cost. Do not submit, close, cancel, change preferences, or substitute missing fields. Wait for my explicit approval.
The current place_order tool defaults to confirm=false and returns a PREVIEW. This is neither a submitted order nor a simulated fill. A subsequent confirm=true call can submit a paper order only when the resolved account is verified as paper and all permissions and risk checks permit it. Live-account previews and submissions are blocked during the live MCP order freeze; an unknown account mode is treated as live and blocked. A prompt is not a security control: use client approvals and application-enforced limits too.
The tool's basic entry-order parameters do not create a complete bracket merely because a signal contains a stop and target. Review any exit workflow separately. Do not assume all broker-native features are exposed through MCP.
Verify what happened
An order response is not fill proof. Reconcile the broker order ID, status, filled quantity, and average fill price in the broker account. Use get_open_orders for outstanding orders and available history tools for supporting records; an order disappearing from the open list alone does not prove a fill.
For a custom AI-to-broker integration, enforce symbol/asset validation, freshness, deduplication, size limits, an explicit approval step, and a stop mechanism outside the model. Start with the Alpaca paper checklist. Public subscriptions are paper-only. Live beta enrolment, copy-trading expansion and live MCP orders are frozen; a paid plan does not unlock them.
Educational information only, not investment advice. AI can make mistakes, and paper or live orders can be rejected, remain open, or fill differently than expected.
Tradewink MCP Claude Codex: practical checks
Keep read access, request preview and order submission separate. Record an idempotency key, reconcile timeouts before retrying, and verify account, symbol and quantity from the returned order state rather than the model response.
Read the Alpaca paper trading limitations for the underlying definitions and limits. For a next step, use Partial Fill Testing: Replay Restarts and Duplicates and I received a trading signal. What do I do next?.
Frequently Asked Questions
Does the MCP include a subscriber get_signals tool?
The registered MCP tools include strategies, analysis and permitted account workflows, but raw quote, history, mover and screener tools are unavailable while redistribution is disabled; they do not expose a dedicated subscriber get_signals tool. Use the REST signals API or supply the signal text to your assistant.
Is an MCP preview a paper trade?
No. A preview does not submit an order. Paper execution requires a paper broker connection and a separate submission.
Can an AI execute through Tradewink?
Only a verified paper account can use the permitted paper submission path after approval and risk checks. Live-account previews and submissions are blocked while live MCP orders are frozen; installing MCP does not change that gate.
Should I paste my broker secret into Claude or Codex?
No. Use protected connection settings for broker credentials and OAuth for the MCP. Store API credentials in a server-side secret store or environment variable.
Does an instruction to ask first enforce a security boundary?
No. Keep client tool approvals enabled and enforce limits in your application too. Natural-language instructions alone are not an access-control mechanism.
Read next
Keep learning with a related guide before putting an idea on your watchlist.
Partial Fill Testing: Replay Restarts and Duplicates
Partial fill testing: Use synthetic broker events to check filled quantity, cash and restart behavior.
I received a trading signal. What do I do next?
A practical first-signal checklist: understand the setup, check freshness, choose paper practice or skip, and distinguish delivery from a fill.
Choose how Tradewink signals reach your tools
Choose dashboard, email, Discord, workflow integrations, webhooks, or API access. Test delivery before adding any execution step.
Try AI signals on your watchlist
Send yourself a signal preview, then add tickers to see ranked entries, exits, and risk notes in Tradewink.
Key Terms
Related comparisons
Sources cited in this guide
- MCP documentation (code.claude.com)
- Alpaca paper trading limitations (docs.alpaca.markets)
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…