MCP Server

Bring your own AI

The VYX MCP server gives your own AI — Claude Desktop, Claude Code, claude.ai, ChatGPT, Codex, Cursor, or any client that speaks the Model Context Protocol — the sight of the desk's own analyst and hands on your positions. It reads your board scored live — the analyst's whole board if you ask — previews candidates before saving, composes signals and regimes, stands up and steers the desk's analyst, files reads and setup cards on your desk, and trades with you: you analyze together, agree on a setup, and it places and manages the position from the conversation. Your practice books are open to it on every plan, Free included, so the two of you can work real setups on play money from the first message; the live wallet needs a trading plan and the live switch on. The in-app chat is the zero-setup way to do all this on us; the MCP server is the same copilot running on your own AI subscription, so your usage scales with the plan you already pay your AI provider for. On connect it briefs your client with built-in instructions — what VYX is, what each metric means, the workflow, and the guardrails — so a fresh session uses it well from the first message. It is non-custodial: the key it trades with can place and close but never withdraw, live trading is off until you (or your AI, on your word) turn it on, and it cannot connect a wallet, change your guardrails, clear your kill switch, or enable or arm a desk trader.

Connect it (one URL, no install)

Add the connector URL below in your AI client and sign in to VYX when it asks — that is the whole setup. There is nothing to install, it speaks Streamable HTTP, it works on mobile, and it auto-updates. Signing in this way grants your AI full access to compose on your account — signals, regimes, desks, watchlists, and trader strategies — so it can get you set up rather than only look around. You approve that on a consent screen that lists exactly what it can touch, and you can revoke it anytime under Settings → API & integrations. Connecting is free on every plan.

https://api.vyx.app/mcp

Client-by-client

The same URL works everywhere. Where a client asks for an API key instead of a sign-in, mint one under Settings → API & integrations and send it as a Bearer token. Every AI you have signed in this way is listed there too, under Connected apps — what it can reach, when you authorized it, and when it last acted — and Disconnect severs it on the spot: the app loses access now, not at its next token renewal.

• ChatGPT — Settings → Apps → Advanced settings → Developer mode, then Settings → Connectors → Create and paste the connector URL. Sign in to VYX when prompted.
• Claude (claude.ai, Desktop, Code) — add it as a custom connector and authorize with your VYX account.
• Codex, Cursor, and other MCP clients — add the same URL as a remote MCP server.
• Anything that wants a token instead of a sign-in — Authorization: Bearer vyx_sk_live_…

Authorization: Bearer vyx_sk_live_…

Let your AI set you up

The fastest way to a working desk is to ask for one. Once connected, your AI can read the live market, compose the signals that catch what you care about, stand up a desk around them, and explain what it built — the setup work you would otherwise do by hand in the app. It can trade with you too: practice books need no setup at all, and the live wallet opens the moment the live switch is on — a switch your AI flips when you tell it to trade live. Wallets, guardrails, the kill switch and any desk trader's enable/arm stay with you in the app.

• "Connect to VYX, look at what the market is doing, and build me a desk for catching liquidity sweeps on the majors."
• "Set up VYX for someone who trades funding-rate extremes — compose the signals, preview them first, and light the ones that discriminate."
• "Read my board and tell me what it is set up to catch, in plain English."
• "Work my Mean reversion desk for A+ setups, top-down, and show me each read on the Workbench as you go." — the hunt_setups prompt walks this: the desk's mandate first, then the field and regimes, the higher timeframe, the tape, and only then a call.
• "Analyze the premarket rally on META end to end." — the read_the_move prompt pages back to where the move actually began, reads what flow did through each third of it, and only then looks at the current bar.

Tools: see the market

The read tools are the in-app chat's sight, served fresh on every call — live scoring for every plan, not cached engine runs.

• vyx_scan — your board scored live by your active desk's signals (or one named signal), with per-signal contributions and where price sits in its recent range. Sort, filter, and cap the slice. Ask for the analyst view and it returns the desk analyst's whole board as text instead — the session clock, the field, each regime as its recent series, every row with its percentile against its own history, price against range and ATR, higher-timeframe trends, fillability, co-movers and chart structure, the tape, positions, live setups and the record — the same context the analyst hunts from.
• vyx_symbol — one market read top-down: where price sits in its recent structure and the path that got it there, the tape (sweeps, absorption, presses, level tests, range breaks — with what is still standing), then your signals' scores with the per-indicator why, and the current bar last. Read it again one interval up for the higher frame. Any Hyperliquid market reads, including ones your desk's board filters out — those come back with the same structure, tape and microstructure, and say plainly that they carry no desk score. Ask for bars and the candle history comes back under a window summary: what price did across the whole slice, and what order-flow imbalance, cumulative volume delta and open interest did through each third of it — so a rally that ran the whole way on negative book pressure reads at a glance instead of bar by bar. The reply also says whether older bars exist and hands back the exact timestamp to page further, so your AI knows when it is holding a slice of a move rather than the move.
• vyx_search — screen the whole universe by one metric condition (spread, imbalance, OFI, funding, OI change, and more).
• vyx_regime — your regime tiles evaluated on the live universe. Each tile's high, neutral or low names the fixed rule behind it — above or below 0, a share of its markets, or above or below its baseline — not where it sits in its own range. Ask for the series and each tile comes back over its last 100 bars, oldest to newest — the read the desk analyst gets — so where now sits against the read's own range is yours to see, not a label's.
• vyx_signal_history — how one market has been scoring over time. Leave the signal out and it reads your whole desk: every lit signal and the Total per bar, exactly as the board blends them; name a signal to drill in. Signals that fire on a few bars list just those bars, so "when did the desk last fire on BTC, and which way?" is one call.
• vyx_levels — a signal's level zones on one symbol: price bands, touches, breaks, and where price sits against each zone (inside, or above / below by how much). Zones start from the bars a signal fired on, and the reply says so when a window had none.
• vyx_pulse — the live order-flow pulse across the universe.
• vyx_news — the live news wire behind the board: crypto wires plus world coverage, each item mapped to the markets it names with freshness and an expected direction. The catalyst check — if nothing on the wire names a mover, the move is flow.
• vyx_list / vyx_watchlists — your saved objects and watchlists.
• vyx_positions — every position you are holding right now, real money and practice books alike, in one list, each labelled with the trade desk that opened it and the stops and targets on it. Size, entry, mark, unrealized PnL, leverage and liquidation come from the venue for real positions and from the practice book for practice ones. It reads every builder-dex market you trade, not just the main exchange, so nothing you hold is quietly left out. A position VYX has no record of opening is shown as unattributed rather than guessed at. Filter by desk, or by book.
• vyx_analyst_latest / vyx_trader_decisions — the desk analyst, desk-scoped: the standing orders it runs under, its faculties and cadence, whether it is running, the setup cards it filed newest first, and the desk's record by author; and a trader's auditable decision log (what it decided and why). Raise limit to page further back.
• search / fetch — a plain-language way in: find the markets, signals, or desks relevant to a question, then pull the full live record for one. Clients that only support these two (ChatGPT's research modes among them) can still read VYX through them.

Tools: the Workbench and setup cards

Most sessions with your AI are a search for an idea, not a call. These tools let it show its work on your desk as it goes — the Workbench tab in the Analyst column fills in the moment each read is filed — and file a setup card when a real level and an invalidation exist.

• vyx_analyze — file an analysis on the desk's Workbench: a chart (one market at an interval, with the next timeframe up drawn hollow behind it), a comparison (the market against the ones it moves with, every line rebased to zero at the window's start — name the peers, or let the desk pick the strongest co-movers), a metric (OFI, CVD, funding, open interest or volume over the window), or a signal read (one signal's score bar by bar — name a signal on your desk, or let your AI compose one and score it without saving it, which you can then Keep as signal from the bench). Your AI chooses what to look at and writes one sentence; VYX draws it from the venue's own candles, so nothing on the bench is a number the model made up. Every analysis is kept; the bench scrolls back as far as the record goes.
• vyx_analyses — read the bench: what has been filed on a desk, newest first, or only what one setup linked.
• vyx_create_setup — file a setup card: symbol, side, archetype, the context (the regime, where price sits in the higher timeframe, and optionally the market's group — one sentence each, settled before the thesis), thesis, entry, invalidation and two targets. It is held to the same fence as the desk's analyst — entry near the last price, every level inside the recent range, ordered for the side — and a card without its context is not filed. The card wears your AI as its author, links the analyses it leaned on, and is graded by VYX exactly like the analyst's: from the bar its entry prints. A stop or the 48-hour deadline reached before the entry ever prints voids the card — no trade happened, so no result is claimed.
• vyx_setups — the desk's setup cards: the context, the frame, the status and grade (including void and withdrawn), when the entry filled, who authored each, and how many analyses it links — plus the desk's record by author, your AI's beside the analyst's, so it calibrates on the outcomes before it.
• vyx_withdraw_setup — pull one of your AI's own live cards before it resolves, with a one-line reason. It stays on the record as withdrawn — a pulled call is information, never a deletion. Nothing is cancelled anywhere: a card was never an order.
• vyx_revise_setup — revise one of your AI's own live cards: pass only what changes. The revision runs the whole fence again; on success the original steps aside as withdrawn (revised) and points to the new card, so a call's lineage stays on the record. Up to three revisions per call.

Tools: trade together

Your AI can be your co-trader: the two of you analyze, agree on a setup, and it places and manages the position from the conversation — the same order ticket you use in the app, driven by your words instead of your click. No setup stands in the way: your practice books — play money at real prices — are open to it from the first message. The live wallet you approved in the app sits behind one switch on your account, off by default; when you tell your AI to trade live, it flips the switch itself, says so, and it stays on until either of you turns it off. Every live open passes your money guardrails against the venue's own account state and refuses with the reason when it would breach them; the kill switch stops everything; and when a desk trader is enabled on the wallet, that wallet is the trader's — the connection will not place, move or close anything beside it until you stop the trader. Every position it opens carries its stop from the first bar; a stop is moved cancel-first so the venue never holds two; every order records the desk it was sent from, so what you hold reads with who opened it. The key it trades with can place and close, never withdraw.

• vyx_trading_status — read first: your practice books (armed, equity, open positions), the approved live wallet and its network, whether live trading is on your plan, whether the live switch is on, the kill switch, the guardrails, and whether a desk trader currently owns the wallet.
• vyx_set_trading — the live switch: on lets connected AIs trade the approved wallet; off closes it again. Your AI flips it when you ask to trade live, and tells you it did.
• vyx_open_position — open a position you agreed on, practice or live: market (fills now, bracket rests at once) or limit / post_only (rests at price). Requires the stop; takes a target; size in coin units or USD notional; records the desk and the setup card it follows.
• vyx_close_position — close all or a fraction at market, reduce-only. A full close clears the orphaned stop and target; a partial re-sizes them to what remains.
• vyx_set_protection — move or set the stop and/or target on an open position. Only the sides you pass change; on the live book the old trigger is cancelled before the new one rests.
• vyx_move / vyx_cancel — move a resting entry to a new price, or cancel one order by id.
• "Let's trade my Mean reversion desk together on the practice book, risking $50 a trade." — the trade_session prompt walks this: books and holdings first, the hunt, your yes, the order with its stop, then managing it with you one dated line at a time.

Tools: check, then build

The same check-your-work loop the in-app chat runs before it builds anything — a quick check on the live field, then a grade over history for each draft (nothing saved), and only the version that holds up gets created. A signal that lights a small share of the board (about 2–10% of market-bars) reads as events; one that lights most of it reads as noise.

• vyx_preview_indicator — one formula across the universe: range, median, dead-data detection.
• vyx_preview_signal — a candidate composite on the current bar: fire count, buy/sell split, dead gates, and any field that reads nothing on Hyperliquid. Nothing is saved.
• vyx_preview_regime — a candidate regime's reading, distribution, and whether it moves, with the same scope and relative options as vyx_create_regime, so a cohort row (memes, AI, a watchlist) or a row measured against crypto previews exactly as it will read, with its member count.
• vyx_create_signal — create or update a composite from the same rich item shape the chat composes.
• vyx_create_regime — one instrument of a desk's read: a regime tile (median, mean, dispersion, or breadth), market-wide or scoped to one sector or theme (memes, L1s, semis, AI), a set of asset classes, or a watchlist; relative:true reads a scoped tile minus the whole field. It lands on the desk's strip as it is created.
• vyx_validate_signal — proof over about 1,000 bars of history, for a saved signal or for drafts that are never saved (up to four side by side on one window): how much of the board it lights, whether the markets it lights move more than the rest, and its direction after costs.
• vyx_set_server_side — run a signal 24/7 server-side (Trader and up).
• vyx_delete — remove a saved object by kind and id.

Tools: work your trade desk

Full desk control, the way the in-app chat has it. A desk's lit signals are exactly what its AI trader trades — changing them changes what an armed trader acts on at its next tick, and your agent is briefed to say so before doing it. AI traders follow the same plan gating as in the app (Autopilot and up).

• vyx_desk — a desk whole, starting with its mandate: description and explainer (what it is for), the analyst's standing orders and faculties, the live setups that already stand across every author, then lit signals, interval, liquidity floor, its trader (strategy, mode, whether it can run and why), open trades, recent closed trades with R, and your armed posture. Your AI is briefed to read it before its first call and never to guess a desk's strategy from its signal names.
• vyx_create_desk / vyx_switch_desk — stand up a new desk; switch the active one (syncs to your devices).
• vyx_set_desk_interval — set the bar a desk scores on (1m to 1d). It moves every lit signal together, like the desk's own interval control, so the analyst and trader read the same bar you do.
• vyx_set_desk_regimes — set, add or remove the regimes on a desk's strip. A desk's regimes are its read: the strip is exactly what its analyst reads, and what its setup cards must descend from.
• vyx_set_desk_signals — set, add, or remove the desk's lit signals by id or name.
• vyx_create_analyst / vyx_edit_analyst / vyx_delete_analyst — the desk's analyst, whole: stand one up with its standing orders, faculties and cadence; steer it, switch it on or off; remove it and its cards. Turning an analyst on is safe authority — it files setup cards, never orders.
• vyx_set_analyst_brief — write a desk's standing orders: what it hunts, what it skips, how entries are timed, no-trade conditions. The same brief the desk's own analyst obeys, so one text steers both minds on the desk, and the next session starts from it instead of re-explaining. Creates the desk's analyst if it has none, left off until you turn it on.
• vyx_create_trader — compose the desk's autonomous follower with the chat's strategy model: summary, setups, planning, management, sizing, avoid. Always created disabled; running it stays with you.
• vyx_edit_trader — revise the strategy in place (version bumps, learnings preserved). It cannot enable, arm, or switch modes.
• vyx_create_watchlist / vyx_update_watchlist — named watchlists.
• vyx_share_desk — make a desk public and get its no-login link.

Tell us when something is wrong

Your AI can report a bug or send feedback straight from the session that hit it, with vyx_report_issue. It is briefed to file the moment a tool errors, the data reads back wrong, stale or empty, or it needed something no tool could do — rather than quietly working around it and leaving you with a worse answer. A fault report carries the exact call it made, what it expected, and the verbatim response; a vague one is refused with a list of what to add, so what reaches us is something we can reproduce. Feature requests and plain feedback go through the same tool and are held to a different bar — say what you want to be able to do and why today's tools cannot, and no reproduction is asked for. It reaches the VYX team directly, and your AI will tell you what it filed.

• vyx_report_issue — a bug, a data problem, a missing capability, or a feature request.
• "That 4h read looks off — report it to VYX with what you actually got back."
• "Ask VYX for a way to screen the whole universe by realized volatility, and say why I want it."

And read our answer back

Reports are not a one-way send. We read what your AI files the same day and answer in writing, and vyx_reports hands that answer back to the AI that filed it: where each report stands — being looked at, fixed, answered, queued, declined, or waiting on more detail from you — and the note we wrote to it. So a session that hit a wall last week starts by checking whether the wall is still there instead of building the same workaround again, and a fix reaches your AI without you having to relay it. Your AI sees the reports filed from your account and nobody else's. Ask it to check, or leave it to the prompt it already has.

• vyx_reports — the status and our written note on everything your account has filed, newest first.
• "Did VYX ever come back on that 4h candle problem you reported?"
• "Before you work around that again — check your filed reports."

Resources

Resources are read-only context you can attach so the model grounds its reasoning in your live board and the analyst's view — two analysts at once.

• vyx://signals — your signal definitions.
• vyx://board — your board scored live by your active desk signals.
• vyx://desk — your active trade desk whole: lit signals, trader, open trades, recent trades.
• vyx://pulse — the live order-flow pulse snapshot.
• vyx://analyst — the AI analyst's latest notes.

Guided prompts

The server ships slash-command prompt templates — pre-written best-practice workflows your client surfaces as commands. Pick one instead of writing the prompt yourself.

• get_started — new here: your AI reads the live market, composes signals for what you want to catch, previews them before saving, and stands up your first desk around the ones that survive.
• morning_brief — the pulse and regime across the universe plus your board digest and what changed.
• inspect_symbol — a deep microstructure read of one symbol (depth, imbalance, CVD, funding, OI, structure).
• build_signal — a guided composer: preview first, then vyx_create_signal.
• desk_review — read a desk whole, judge its trader's recent trades, and propose one strategy revision.

Example prompts

Or just ask in plain language and the model picks the right tools.

• "What is the order-flow pulse right now — where are funding and aggression concentrated?"
• "Scan my board and summarize the three strongest signals and why."
• "Preview a signal that fires when the book fractures — spread blowout plus an unstable spread — and create it if it discriminates."
• "Read my desk, review the trader's last ten trades, and suggest one change to its sizing rules."
• "Switch to my Majors desk and light only the OI Surge and Fracture signals."

What it will never do

The MCP server holds no execution authority, on purpose. It cannot place, modify, or cancel an order; it cannot enable a trader, arm your account, or switch a trader between analyst, testnet, and live. Traders it composes are born disabled. Your AI can see everything and shape everything — the decision to let a strategy touch money stays with you, inside the app, behind the same hard rails the built-in chat obeys.