Build with AI

Two MCP servers — a remote market-data endpoint and a local trading server. Pick the one you need.

Vike ships two Model Context Protocol servers. They know nothing about each other, and one MCP client can hold both at once.

Data API — 73 tools — https://data.vike.io/mcp, remote HTTP. Vike runs it; your client holds a URL and a credential from your Vike account (an X-API-KEY, or an OAuth connection for clients that register themselves). Wallets, tokens, Polymarket and alerts on transfers and Hyperliquid. Every call is metered against one hourly budget.

Trader — 17 tools — vike-cli mcp, a local stdio subprocess your client launches. No Vike account is involved: it talks to services you run — a vike-datahub for backtests, a vike-tradehub node for live state and orders — authenticated with your own daemon's HMAC node keys. Rhai strategy authoring, backtests, sweeps, walk-forwards, and order writes behind a mandatory preview gate. Nothing is metered.

The difference to carry into setup: one is a URL you point a client at, the other is a command the client runs. They are configured in different places, and their credentials are different kinds of thing — an account key versus the keys of a daemon on your own machine.

⚠ Nothing in the navigation links here. The sidebar's product switcher moves between the two servers directly, so this page exists only for a saved URL. Follow one of the two links above.