Can an AI agent actually place my TradingView trades?
Short answer: not the way the question usually means it, but close, and the real version is more useful. An AI agent doesn't read your TradingView alerts -- nothing in Autoview's agent surface parses a TradingView payload. What it does today is place a real order the moment you (or the agent, on your instruction) tell it to, through the same broker connections Autoview's webhook automation already uses. On Kraken and Crypto.com, that's a live, funded order right now. On five other venues, it's a free paper fill while you get comfortable with the idea.
Two different paths, not one
Autoview runs two separate mechanisms that both end in a real order, and they don't share code:
- The webhook path, the one Autoview has run for years: a TradingView alert fires, POSTs to your Autoview webhook URL, and Autoview places the order. No AI agent reads or touches any part of it. If this is what you're picturing, the TradingView webhook guide is the one you want, and it's been live the whole time.
- The MCP path, new and in early access: an AI agent you're talking to, Claude Desktop, a claude.ai connector, Claude Code, or a custom client, calls Autoview's
entrytool with a structured order (exchange, symbol, side, quantity, and so on). Nothing about the tool cares whether the idea behind that order came from a TradingView chart you showed the agent, your own analysis, or a strategy you described in plain language. The agent decides what to send; Autoview validates it, checks what you're entitled to trade, and places it.
So "can an AI agent place my TradingView trades" is really two questions stacked together. If it means "will Autoview auto-execute my TradingView alerts through an AI agent," the answer is no, and it doesn't need to be yes, because the webhook path already does that without one. If it means "can an AI agent I'm using place a real trade through Autoview," the answer is yes, today, and the rest of this page covers exactly what that looks like.
What's live today, and what's still paper
Autoview's MCP server currently supports seven venues. Two place real money orders today:
- Kraken -- live, requires an active Autoview Kraken subscription (the same one that gates Kraken on the webhook path).
- Crypto.com -- live, free, under Autoview's partnership lane.
Five more are free paper accounts, useful for watching an agent work before it ever touches funded money:
- Tradovate Simulation, OANDA Practice, Bybit Testnet, Bybit Spot Testnet, and Crypto.com Demo -- all $0, all real fills against play money.
Live OANDA and live Bybit aren't reachable through the MCP yet; only their paper counterparts are, and each live venue joins the list as Autoview finishes a dedicated coverage pass for it, the same phased rollout the webhook side went through exchange by exchange.
Why a misread instruction can't cost you money
Every call to entry is a dry run by default. An agent can misunderstand an instruction, so nothing gets sent to a broker unless you explicitly set live to true on that specific call. A dry run still builds the exact order Autoview would have placed and hands it back for you to read, so you can check the symbol, side, size, and any stop before anything real happens. That default applies the same way on Kraken and Crypto.com as it does on a free paper account -- going live is always a deliberate, separate step, never the fallback.
Tokens add a second layer: each one is scoped at creation to specific exchanges and to dry-run-only or live-enabled, and you can revoke any token instantly from /account/tokens/, which cuts an agent's access immediately, mid-session if needed.
Which AI agents actually connect
Anything that speaks the Model Context Protocol. Claude Desktop, the claude.ai connectors, and Claude Code all handle the connection handshake for you out of the box. A custom or autonomous agent client works too, as long as it completes the standard initialize call and carries the Mcp-Session-Id header the server hands back on every request after that, the one piece the ready-made clients hide from you.
What isn't there yet
Named plainly, not glossed over: attached brackets (stopLoss, takeProfit, trailStop) currently work on Tradovate Simulation only, not on Kraken or Crypto.com. Live OANDA and live Bybit aren't on the MCP yet, paper versions only. And, worth repeating because it's the whole premise of this page: the MCP does not ingest TradingView alerts, webhooks, or Pine Script signals directly. If your workflow is "TradingView fires, a trade happens automatically," that's the webhook path, running today, with no agent required.
Where to go next
If you want the technical walkthrough, the MCP getting-started guide covers the entry and events tools, token setup, and a full first order end to end. If what you actually want is a TradingView alert executing without any AI in the loop, that's how to automate TradingView alerts, the path Autoview has run at scale for years. If you're comparing where AI agents fit against Autoview's other surfaces (browser, cloud, webhook), Platforms lays out all four side by side.