Generate a token
Create an
av_mcp_
personal access token at
/account/tokens/. Choose which exchanges it may trade and whether it can place live orders; dry-run is the default.
Autoview's MCP server lets Claude, Cursor, or any MCP-aware agent place and inspect real orders on your own exchange account through one endpoint and six tools. No exchange secret ever enters the chat.
Every call needs an Autoview account token and, for entry/alert/command, a hook already linked to an exchange.
Create an
av_mcp_
personal access token at
/account/tokens/. Choose which exchanges it may trade and whether it can place live orders; dry-run is the default.
The MCP endpoint is
https://api.autoview.com/mcp/. Send the token as an
Authorization: Bearer
header if your client supports custom headers (Claude Code, Cursor, and most non-browser clients do this automatically); otherwise pass it as the
token
argument on every call.
Orders trade through credentials already linked to a hook, not raw keys pasted into a chat. If you have not linked one yet, run the
setup wizard, then call the
setup
tool first to see your hook ids, their linked exchanges, and what each exchange supports.
Dry-run is the default everywhere a live switch exists. A bare call previews; it does not trade.
setupRead this first. Your token's scope, which exchanges you can trade right now, per-exchange facts (order types, symbol format, bracket support), and your hooks.
entryPlace one order right now against a linked hook's credentials. Dry-run unless you set live:true. Returns a trace id; read the fill with events.
alertBuild everything TradingView's Create Alert dialog needs in one call: the webhook URL, the message, an expiration that does not silently lapse at 30 days, and a resolution.
commandBuild just the alert message string from structured order fields, without a webhook, for when you already have the destination.
hooksList your webhook URLs and which exchange each is linked to. The URL is itself a bearer secret. Rotate a hook's key from /account/hooks/ if it leaks.
eventsRead back what an order did. Also the only way to see an order that a TradingView alert fired directly at a webhook, without ever calling entry.
TradingView runs its own MCP server too (mcp.tradingview.com/mcp , public beta). Connect both, and your agent can build a strategy and wire the alert without you ever opening TradingView's UI.
Confirms which hook to use and which exchange it is linked to.
Pass hook_id, symbol, side, and quantity (plus any order type or bracket fields). It returns the message, webhook, expiration, and resolution TradingView needs.
With TradingView's MCP server connected, your agent calls its
create_alert
tool directly, forwarding Autoview's
webhook,message,resolution
, and
expiration
as its own arguments of the same name. No copy-paste. Without TradingView's MCP connected, paste the same values into TradingView's Create Alert dialog by hand instead.
Four things to know before you wire this up:
webhook argument needs a TradingView plan with webhooks enabled and two-factor authentication turned on.expiration defaults to 30 days if you omit it. Autoview's alert tool exists specifically to avoid that lapse, so make sure your agent forwards Autoview's value instead of leaving TradingView's default in place.condition is price-only (cross/cross_up/cross_down/greater/less). It does not carry a full Pine strategy alert.get_alerts also strips out message and webhook, so use get_alerts_log to read the message text back. Never put the hook's key in the message field either way; the webhook URL already carries it.Crypto.com and every practice/testnet/sim exchange are free. Kraken live trading needs an active Autoview subscription.
Crypto.com, OANDA Practice, Crypto.com Demo, ByBit Testnet, ByBit Spot Testnet, and Tradovate Simulation.
Kraken live trading.
A bare call previews without trading. Placing a real order also needs a live-scoped token, chosen when you generate it at /account/tokens/.
Full setup walkthrough: the MCP getting-started guide.