3 posts tagged with "api"

Connecting Claude to your trading account is the easy half. The hard half is knowing what to ask it — because most "AI for crypto" demos collapse the moment you want to do something real. This post is the practical half: five concrete workflows where the VolatiCloud MCP server turns multi-screen dashboard work into one conversation, plus copy-pasteable prompts and the trade-offs nobody warns you about.

Haven't connected MCP yet? Start with the MCP server setup guide — it covers configuration for Claude Code, Claude Desktop, and Cursor, and how the tool architecture works. Come back here once you're connected.

VolatiCloud's MCP server is live. Drop a four-line config into Claude Code, Claude Desktop, or Cursor and your AI assistant gets typed access to every operation in the VolatiCloud GraphQL API — list bots, run a backtest, fork a strategy, fetch live trades — directly from chat. No manual API calls, no copy-pasted tokens, no glue code, and no leaked credentials in .env files.

This post covers what MCP is, how the VolatiCloud server is built, and how to install and configure it in your editor. Once connected, see the companion post on practical AI trading workflows and example prompts.

Manually clicking through a dashboard to start 12 bots before the New York open is not algorithmic trading — it's manual trading with extra steps. VolatiCloud's API client system gives you OAuth 2.0 client_credentials authentication for the entire GraphQL surface, so any script, CI pipeline, or external dashboard can manage bots, trigger backtests, and pull live performance data without a browser in the loop.