AI agents · MCP

Give an agent a seat
at your exchange.

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 eight tools. No exchange secret ever enters the chat.

Generate a token Create an account

Connect in three steps

Every call needs an Autoview account token and, for entry/alert/command, a hook already linked to an exchange (the connect tool can link one).

Step 1

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. The token form asks for your current passphrase every time you mint, so if you registered with just a six-digit code and have not set a passphrase yet, add one at /account/profile/ first.

Step 2

Point your client at the endpoint

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.

{
"mcpServers": {
"autoview": {
"url": "https://api.autoview.com/mcp/",
"headers": { "Authorization": "Bearer av_mcp_..." }
}
}
}

Step 3

Link a hook to an exchange

Orders trade through credentials already linked to a hook, not raw keys pasted into a chat. Ask your agent to call connect. It links a webhook to keys you have already saved, or gives you a link to save them. For other exchanges, use the setup wizard. Then call the setup tool to see your hook ids, their linked exchanges, and what each exchange supports.

Eight tools, all gated on your token

Dry-run is the default everywhere a live switch exists. A bare call previews; it does not trade.

`setup`

Read 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.

`connect`

Link one of the seven certified exchanges to your account. It creates a webhook tied to the keys you have already saved, or returns a link where you can save them. Calling it twice is harmless. Connecting a real-money exchange needs a live-scoped token; any token can connect a paper exchange.

`catalog`

Browse every other supported exchange, filtered by paper, free, or name. Exchanges outside the certified seven work with command and alert only, not with entry or connect.

`entry`

Place 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.

`alert`

Build 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.

`command`

Build just the alert message string from structured order fields, without a webhook, for when you already have the destination.

`hooks`

List 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.

`events`

Read 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.

The TradingView round trip

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.

Ask your agent to call setup

Confirms which hook to use and which exchange it is linked to.

Ask it to call alert

Pass hook_id, symbol, side, and quantity (plus any order type or bracket fields). It returns the message, webhook, expiration, and resolution TradingView needs.

Hand it to TradingView's create_alert

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:

TradingView's webhook argument needs a TradingView plan with webhooks enabled and two-factor authentication turned on.
TradingView's 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.
TradingView's condition is price-only (cross/cross_up/cross_down/greater/less). It does not carry a full Pine strategy alert.
TradingView's market data over MCP is delayed and rate-limited to roughly 100 calls per minute. TradingView's own 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.

Exchanges and scope

Crypto.com and every practice/testnet/sim exchange are free. Kraken live trading needs an active Autoview subscription.

Free

No subscription required

Crypto.com, OANDA Practice, ByBit Testnet, ByBit Spot Testnet, and Tradovate Simulation.

Paid

Live orders need a subscription

Kraken live trading. Every other live exchange outside the free list above needs the same per-exchange subscription too. Anyone can call these exchanges; without an active subscription, orders run as dry-runs instead of being refused. See pricing for the price.

Dry-run vs. live

Two gates, not one

A bare call previews without trading. Placing a real order, or connecting a real-money exchange, also needs a live-scoped token, chosen when you generate it at /account/tokens/.

Full setup walkthrough: the MCP getting-started guide.