Autoview

Trade across 22+ exchanges and brokers from any MCP-capable AI agent, no install required.

CommunityOnlineNo sign-inGlobalFreeRead-only

What it can do

    What data it sees

    Do you need an account

    No: the server works without sign-in

    Trade across 22+ exchanges and brokers from any MCP-capable AI agent, no install required.

    How to connect

    How to connect Autoview to Claude

    The server address to paste into Claude settings:

    https://api.autoview.com/mcp/

    1. Open Claude (claude.ai or the desktop app).
    2. Go to Settings → Connectors.
    3. Click Add custom connector.
    4. Paste the server address copied below into Remote MCP server URL and click Add.
    5. In a chat, click + → Connectors and switch the new connector on.

    Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

    Authorization

    After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

    How to connect Autoview to ChatGPT

    The server address to paste into ChatGPT settings:

    https://api.autoview.com/mcp/

    1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
    2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
    3. Open Settings → Connectors and click Create.
    4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
    5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
    6. In a new chat open + → Apps/Connectors and enable the connector.

    OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

    Authorization

    On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

    How to connect Autoview to Cursor

    The server address to paste into Cursor settings:

    https://api.autoview.com/mcp/

    Fastest: click Open in Cursor below and confirm the prompt.

    Manually:

    1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
    2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
    3. Save the file. The server appears in the MCP list; authorize it there if asked.

    Authorization

    If the service needs sign-in, an authorize button appears next to the server in the MCP list.

    Server tool list (4)

    Raw names from tools/list. Only developers need these.

    entryPlace an order on a supported exchange using your own broker API keys. You fill structured order fields (symbol, side, quantity, type, price, trigger) — Autoview assembles the order for you. Dry-run by default: a bare call returns the parsed order without placing it; set live:true to place a real order. The order is relayed to the exchange asynchronously, so this returns { queued, trace } immediately, not the fill — pass the trace to the `events` tool to read what the order did. Requires your Autoview account token — an av_mcp_ personal access token (generate one at /account/tokens/ on the Autoview site) or an OAuth JWT. Supported exchanges: OANDAPRACTICE, KRAKEN, CRYPTO, CRYPTODEMO, BYBITTESTNET, BYBITSPOTTESTNET, TRADOVATESIM. Crypto.com and practice/testnet/sim are free; other exchanges require an active Autoview subscription. If you also hold a TradingView MCP connection, prefer `command` + `hooks` for anything that should outlive this chat: entry fires once, now; a TradingView alert built from `command`'s output and `hooks`' webhook URL keeps firing after this conversation ends.
    eventsRead what one of your orders did. The entry tool relays orders asynchronously and returns a trace id; pass that trace here to get the events the order produced (fills, cancels, and any exchange error), newest first. Requires your Autoview account token (av_mcp_ personal token from /account/tokens/, or an OAuth JWT) — the same token you passed to entry. Poll this a moment after entry if the events are not there yet — the exchange reports back out-of-band.
    hooksList your Autoview webhook URLs — the destination for a TradingView (or any other) alert's webhook field. Each hook already knows which exchange(s) it is linked to; there is nothing further to configure on the Autoview side. Pair with the `command` tool: build the alert message with `command`, take a URL from here, and pass both straight to TradingView's create_alert(webhook, message). Requires your Autoview account token (av_mcp_ personal token from /account/tokens/, or an OAuth JWT). The returned URL is itself a bearer secret for unattended trading — treat it like a password; rotate a hook's key from /account/hooks/ on the Autoview site if it leaks.
    commandBuild an Autoview alert command string from structured order fields (symbol, side, quantity, type, price, trigger) without placing an order — the output is the value TradingView's create_alert `message` field should carry. Dry-run by default: a bare call returns a preview command (appends d=1); set live:true to build a command that trades for real once TradingView fires the alert. Pair with the `hooks` tool for the destination webhook URL. Requires your Autoview account token (av_mcp_ personal token from /account/tokens/, or an OAuth JWT) — live:true requires a live-scoped token. exchange is optional: pass one of OANDAPRACTICE, KRAKEN, CRYPTO, CRYPTODEMO, BYBITTESTNET, BYBITSPOTTESTNET, TRADOVATESIM to also validate order-type/bracket support for that exchange; omit it to build a generic command routed by whichever exchange(s) the destination hook is linked to.