How to Trade Stocks with Claude: A No-Code Guide for 2026

How to Trade Stocks with Claude

The short version: install a local MCP bridge, sign in once via OAuth, then ask Claude to check your portfolio, analyze a ticker, or place a paper-trade order. Claude becomes a chat interface to your existing brokerage account without writing a single line of code.

This guide walks through the full setup using Tradewink's hosted MCP server. The same pattern works with Claude Desktop, Claude Code, Cursor, VS Code, Windsurf, and any other client that speaks the Model Context Protocol. If you are comfortable pasting a JSON snippet, you can be trading through Claude in roughly 30 seconds.

What Is MCP and Why Does It Matter for Trading?

The Model Context Protocol (MCP) is an open standard from Anthropic that lets AI assistants connect to external tools through a uniform interface. Instead of a bespoke integration for each data source, a single server exposes tools (get_quote, place_order, analyze_ticker) and any MCP-compatible client can call them.

For trading, MCP matters because it closes the loop between natural-language reasoning and broker execution. Your AI can look at a chart, score a setup, and place the order — all in one conversation. Before MCP this required custom code, API keys stored in plaintext, and a fragile integration per client. MCP makes it pluggable.

The Two Paths to Trading Stocks with Claude

There are two honest options in April 2026 for wiring Claude to a US brokerage.

Path A: A Broker's First-Party MCP Server

Public.com ships an official MCP server that connects Claude Desktop directly to a Public brokerage account. You authorize the connection, Claude gets tools like place_order and get_account, and you can trade stocks, ETFs, options, and crypto by chat. The catch: your account must be at Public.

Path B: A Broker-Agnostic MCP Layer

Tradewink ships an MCP server that sits in front of the broker you already use. Alpaca, Tradier, Interactive Brokers, Charles Schwab, Webull, Moomoo, TradeStation, and tastytrade are all supported. You connect your broker once on tradewink.com, then Claude (or Cursor or VS Code) can operate the account through the same natural-language tools.

Path B is the right fit if you do not want to migrate your money. The rest of this guide uses Tradewink as the example; Path A works the same way with Public's documentation.

Prerequisites

You need three things:

• A Tradewink account (free tier is fine)
• A brokerage account at any of the eight supported brokers
• Claude Desktop, Claude Code, Cursor, or any MCP-compatible client

Node.js 18+ needs to be installed because the MCP bridge runs through npx. Most developer machines already have it. If you don't, install Node from nodejs.org.

Step 1: Create a Tradewink Account

Go to tradewink.com and sign up with email, Google, Apple, or Discord. The free tier gives you AI trading signals and Discord alerts; you do not need a paid plan to try the MCP flow. Finish the onboarding and land on the dashboard.

Step 2: Connect Your Broker

Under the dashboard, open the broker panel and select the broker you want to connect. You will be asked for an API key pair or an OAuth redirect depending on the broker. Keys are encrypted with per-user Fernet keys before storage, so only your account can decrypt them. Once the connection test succeeds, the broker shows up as "connected" in the dashboard.

Step 3: Install the MCP Bridge in Your AI Client

Add the Tradewink MCP server to your client by pasting one JSON snippet. No API key is required — the bridge opens a browser window on first launch for OAuth sign-in.

For Claude Desktop, open claude_desktop_config.json and add an entry under mcpServers. On macOS this file lives at ~/Library/Application Support/Claude/claude_desktop_config.json. On Windows it lives at %APPDATA%/Claude/claude_desktop_config.json. The entry sets command to "npx" and args to ["-y", "@tradewink/mcp"]. Save and restart Claude Desktop.

Claude Code users can run a single command: claude mcp add tradewink -- npx -y @tradewink/mcp. Cursor and VS Code Copilot use the same JSON pattern as Claude Desktop but in their own MCP config files.

Step 4: Authorize via OAuth

The first time Claude calls a Tradewink tool, the bridge opens a browser window at tradewink.com/mcp/authorize. You see a consent screen listing what the MCP client is requesting — read portfolio, place orders, update watchlists, and so on. Click Authorize and Claude is now connected to your account.

Tokens are cached locally in ~/.tradewink/mcp/ and refresh automatically. Access tokens live for one hour; refresh tokens live for 60 days and rotate on each use. You can revoke access any time from the Tradewink dashboard.

Step 5: Start Trading by Chat

With the connection live, ask Claude anything about your account. Practical examples:

• "What are my open positions right now?"
• "Check my buying power and flag any margin concerns."
• "Analyze NVDA with a full multi-agent report — bull case, bear case, meta review."
• "Show me today's top market movers with the highest AI conviction scores."
• "Add TSLA and AMD to my watchlist."
• "Place a paper-trade buy on 5 shares of AAPL with a 2% stop below entry."

Claude reasons about the request, calls the right MCP tool, and returns a structured answer. For order placement, Tradewink defaults to paper mode so live money is never at risk. Live trading is currently in closed beta — request access in your dashboard if you'd like to be considered.

What Tools Are Available?

The Tradewink MCP server exposes roughly 50 tools organized by category. Account tools return positions, buying power, and day P&L. Market data tools return quotes, batched quotes, historical bars, news, analyst ratings, earnings, and technical analysis. Watchlist tools let Claude add or remove symbols from your watchlist. Trading tools place, close, and cancel orders. Strategy tools return your active strategies and sell confidence scores. AI analysis tools run multi-agent research on any ticker. Scheduling tools let Claude book a recurring analysis.

Developers can see the full tool catalog at tradewink.com/developers.

Safety: What Can and Cannot Happen

A few guarantees worth internalizing:

• Paper mode is the default. Live trading is currently in closed beta — request access in your dashboard if you'd like to be considered.
• Every order placed through MCP requires confirmation in the client — Claude cannot silently submit.
• Tokens are scoped to your Clerk identity and to the specific MCP client that authorized them. A different device or a different client starts a fresh OAuth flow.
• Revoking access at tradewink.com/dashboard/api-keys invalidates the client's tokens immediately.
• Tradewink does not hold your money. Orders route to the broker you connected; funds stay at the broker.

None of this replaces your own judgment. Claude can be confidently wrong, market conditions can shift mid-trade, and AI analysis is a research aid, not an oracle. Use paper mode aggressively before going live.

Going Beyond Chat: Autonomous Strategies

The chat workflow is half the story. Tradewink also runs autonomous day-trade strategies that screen candidates, score each setup with multi-agent AI, size positions by risk, and route orders through your broker — all while you sleep or work. The chat interface is how you inspect the agent's work; the autonomous side is how it acts between conversations.

If you want Claude to trigger that autonomous loop, ask it: "Enable the day-trade agent with a maximum daily loss of $200 and a maximum of three trades per hour." Claude calls the update_preference tool and the agent's behavior changes immediately.

Troubleshooting

If the bridge fails to open a browser, the console prints the authorization URL — paste it manually. If authorization redirects but the client does not pick up the code, confirm that port 33418 on 127.0.0.1 is not firewalled. If tokens stop working after a week, delete ~/.tradewink/mcp/ and restart the client to re-authorize. If Claude shows no Tradewink tools after setup, check the MCP server list in Claude Desktop's settings and verify the "tradewink" entry shows as connected.

For fallback scenarios (CI, sandboxes, headless machines) set the environment variable TRADEWINK_API_KEY to a manual key from tradewink.com/dashboard/api-keys — the bridge skips OAuth and uses the key as a Bearer token.

Closing Thoughts

Trading stocks with Claude is no longer a demo. With an MCP server in front of your broker, the account becomes conversational: ask, reason, decide, execute. The useful mental model is that Claude is your research analyst and order-entry clerk combined, and Tradewink is the operations layer that connects it to your actual capital.

Start on paper. Lean on the multi-agent research tools before trusting a single-model answer. Read the trade journal after every session. The traders who get the most out of AI tools are the ones who treat them as collaborators, not oracles.