Cryptohopper Trading MCP
Cho phép tác nhân AI quản lý bot giao dịch, lệnh và chiến lược Cryptohopper của bạn, bằng tài khoản mô phỏng hoặc tiền thật.
Máy chủ MCP được lưu trữ
npx add-mcp 'https://mcp-trader.cryptohopper.com/mcp'Cài vào Claude Code, Codex, Cursor và nhiều công cụ khác
Tài liệu
On this page
This page describes how to connect an AI app to Cryptohopper. It is the entry point for the docs site and links to the per-client setup guides in the support knowledge base.
Cryptohopper has two MCP servers. Each has its own address, and you can connect one or both:
| Server | What your AI can do | Address | Sign-in |
|---|---|---|---|
| Trading MCP | Manage your own Cryptohopper account: bots, positions, orders, trades, strategies and backtests | https://mcp-trader.cryptohopper.com/mcp | OAuth 2.0 only |
| Market data MCP | Read live and historical crypto market data: tickers, orderbooks, candles and market details | https://mcp-data.cryptohopper.com/mcp | OAuth 2.0 or an MCP API key |
The market data MCP never touches your bots, orders or exchange keys. The trading MCP only ever acts on your own bots.
Trading MCP
Trading MCP endpoint
The trading MCP is served at: https://mcp-trader.cryptohopper.com/mcp
It works with AI apps that support remote MCP servers with OAuth sign-in, such as Claude and ChatGPT. It does not accept MCP API keys: a request with an mcp_ key is refused.
Connecting an AI app
- In your AI app, add a custom connector or MCP server and paste https://mcp-trader.cryptohopper.com/mcp.
- The app opens the Cryptohopper sign-in. Log in to your account. There is no API key to copy.
- A consent page shows the name of the AI app and the permissions it asks for. Check them, then approve.
- Ask your AI to list your bots to check the connection.
For clients configured with a JSON file, use the address without a key:
{
"mcpServers": {
"cryptohopper-trading": {
"type": "http",
"url": "https://mcp-trader.cryptohopper.com/mcp"
}
}
}
Permissions
The consent page lists each permission the AI app asks for, in the words below. You approve them for that app only. The AI connections tab shows them as view, change bots and trade.
| On the consent page | Scope | What it allows |
|---|---|---|
| See your bots, positions, orders and settings | mcp:hoppers.read | Bots, their config and stats, positions, open orders, trades, assets, the output log, strategies and backtests |
| Change your bots: settings and strategies, switch them on and off, and move a subscription from one bot to another | mcp:hoppers.manage | Enable and disable bots, change their state and config, create, change, generate and delete strategies, run backtests, move a subscription between bots |
| Place and cancel orders and sell positions on your bots | mcp:trade.execute | Place and cancel orders, sell, hold and release positions, set take profit, DCA, cancel all orders, panic sell and panic reset |
Trading MCP tools
| Permission | Tools |
|---|---|
| See your bots | list_hoppers, get_hopper, get_hopper_config, get_hopper_stats, list_positions, list_open_orders, list_trades, list_assets, get_output_log, list_strategies, get_strategy, list_backtests, get_backtest, get_backtest_limits |
| Change your bots | enable_hopper, disable_hopper, set_hopper_state, update_hopper_config, create_strategy, update_strategy, delete_strategy, generate_strategy, run_backtest, assign_subscription |
| Place and cancel orders | place_order, cancel_order, sell_position, hold_position, release_position, set_take_profit, dca_positions, cancel_all_orders, panic_sell, panic_reset |
The trading MCP cannot reach your exchange API keys, your account security, your subscription orders or your Cryptohopper credits.
Paper trading and real money
- Your AI can manage and trade on your paper trading bots right away.
- Real-money bots need the Trading with real money switch, in your profile under AI connections. It is off by default. Switching it on asks for your account password or a code sent by email, and your 2FA code when your account has 2FA. Switching it off asks nothing.
- Trading actions (orders, sells, DCA, take profit, cancels, releasing positions, panic sell and panic reset) and starting a bot (enabling it, or switching buying or selling on) need a bot with a subscription, also on paper trading bots.
- Switching a bot between paper trading and real money resets all its balances, in both directions, and a switch from real money to paper leaves its real positions unmanaged. It is not a toggle to try out.
- Stopping is always allowed: disabling a bot, holding a position, and switching buying or selling off work on every bot, also with real money off.
Safety
- Your own bots only. Every call is checked against your account. A bot that is not yours is refused.
- A daily limit per bot. Orders, sells and DCA on a real-money bot count against that bot's daily limit in US dollars. The default is 1,000 per bot per day; you can set your own in the AI connections tab, up to 1,000,000. The day runs from 00:00 to 24:00 UTC. A trade that does not fit in what is left of today's limit is refused, and so is a trade when the limit cannot be checked. The limit counts the trades the AI places itself. It does not count panic sell, or what a bot's own strategy trades once the AI enables the bot or moves a subscription to it.
- A cap per order. Cryptohopper also caps the size of a single order the AI places with
place_order, whatever the daily limit. A larger order is refused. Selling a whole position and DCA are not capped per order. - Confirm before it runs. Important actions take two calls: the first returns a preview and a confirmation token, the second, with that token, executes. Your AI app can show you the preview before anything happens. An AI app that runs tools without asking you can make both calls by itself, so check your app's tool approval settings.
- Short sign-ins. Access tokens for trading are short-lived. The AI app keeps a refresh token for up to 30 days to get new ones; disconnect the app in AI connections to end it, for example on a lost or shared computer.
AI can make mistakes, and no AI can guarantee a profit. Start with paper trading bots, keep the daily limits low, and keep the real-money switch off until you trust how your AI app works.
Disconnecting
Open Edit profile and go to the AI connections tab. It lists every AI app you connected and what it may do. Disconnect ends that app's access to your account. To stop all AI apps from trading with real money at once, switch off Trading with real money in the same tab. Bots that are already enabled keep trading on their own strategy; disable them to stop them.
Market data MCP
The rest of this page is about the market data MCP.
Endpoint
The Cryptohopper Market Data MCP is served at: https://mcp-data.cryptohopper.com/mcp
Transport is HTTP with Server-Sent Events (SSE). All requests must be authenticated — either via OAuth 2.0 or via a bearer-token API key. See OAuth vs. API key authentication for a comparison of both methods.
Prerequisites
To connect a client you need:
- A Cryptohopper account.
- One of the following authentication methods:
- OAuth 2.0 — no key required; the client handles a browser-based authorisation flow on first connect.
- A Cryptohopper MCP API key (bearer token) — see how to get a Cryptohopper MCP API key.
- An MCP-compatible client (see supported clients below).
The free Pioneer subscription tier is sufficient to connect and test the MCP. See subscription tiers for a full comparison.
Supported clients
The following clients have dedicated setup guides:
| Client | Type | Setup guide |
|---|---|---|
| Claude Code | Terminal | Claude Code setup |
| Claude desktop | Desktop app | Claude desktop setup |
| Cursor | IDE | Cursor setup |
| VS Code | IDE (Copilot agent mode) | VS Code setup |
| Zed | IDE | Zed setup |
| Gemini CLI | Terminal | Gemini CLI setup |
| OpenAI Codex | Terminal | Codex setup |
Any other MCP-compatible client (LM Studio, Continue, Cline, and similar) can be connected using the generic client setup guide.
Connection model
When a client connects to the MCP endpoint:
- The client performs an initial handshake over HTTP.
- The client authenticates using either OAuth 2.0 (browser-based authorisation on first connect, with automatic token refresh thereafter) or a bearer-token API key.
- The client requests the list of available tools. The server returns tool names, descriptions, and argument schemas.
- The client upgrades to an SSE stream for ongoing tool invocations.
All state is held client-side. The server does not persist session state between requests. See Architecture for details.
Authentication
The MCP supports two authentication mechanisms:
- OAuth 2.0. On first connect, the client opens a browser-based authorisation flow. Access tokens are short-lived and refreshed automatically. No key is stored in the client config, but the client keeps a refresh token for up to 30 days. Disconnect the app in the AI connections tab of your profile to end it, for example on a lost or shared computer.
- Bearer token (API key). A long-lived key is passed in the Authorization header of every request:
{
"Authorization": "Bearer <your_api_key>"
}
The client handles either flow automatically once configured. Authentication is scoped to a single Cryptohopper account. Weekly quota and rate limits are applied per account, not per key or per OAuth grant. See OAuth vs. API key authentication for guidance on which to choose, API key security best practices, and rate limits explained.
Configuration format
Most clients use a JSON configuration block that includes the server URL and — for the API key flow — the bearer token. The exact format varies per client.
Option A — API key (bearer token):
{
"mcpServers": {
"cryptohopper": {
"type": "http",
"url": "https://mcp-data.cryptohopper.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}
Option B — OAuth 2.0 (no key in config):
{
"mcpServers": {
"cryptohopper": {
"type": "http",
"url": "https://mcp-data.cryptohopper.com/mcp"
}
}
}
With Option B, the client triggers the OAuth authorisation flow on first connect. Per-client guides document the exact file location and any client-specific fields.
Verifying the connection
After configuring a client, verify the connection by issuing a minimal query. Example:
What is the current BTC/USDT ticker on Binance?
A successful response includes a last price, bid/ask, 24-hour change, and 24-hour volume. See ticker tool reference for the full response schema.
If the response does not arrive, see error reference and troubleshooting.
Tools exposed
The MCP exposes the following tool categories:
| Category | Tools | Reference |
|---|---|---|
| Ticker | Current ticker (get_ticker) | Ticker tool reference |
| Orderbook | Orderbook snapshot (get_orderbook) | Orderbook tool reference |
| Candles (OHLCV) | Candle history (get_candles) | Candle tool reference |
| Metadata | List exchanges (list_exchanges), list markets (list_markets), get market (get_market), list quote currencies (list_quote_currencies) | Supported exchanges |
| Account | Usage and quota query (get_usage) | Usage and limits |
The exact tools available depend on the subscription tier. See subscription tiers.
Tier-specific behaviour
Certain behaviours differ per subscription tier. Examples:
- Exchange coverage. The Pioneer tier is limited to Binance, Coinbase, and Kraken. Higher tiers expose additional exchanges. See supported exchanges.
- Historical data. The Pioneer tier returns real-time data only. Explorer, Adventurer, and Hero support historical candle queries, with different lookback limits.
- Cost factor for historical data. On Explorer and Adventurer, historical candle queries are charged at 5× (short history) or 20× (long history) relative to a baseline call. On Hero, all queries are charged at 1×. See rate limits explained.
Attempts to query functionality outside the current tier return a tier-restriction error. See error reference.
Quickstart
The fastest path to a working connection:
- Choose an authentication method — OAuth 2.0 (recommended for interactive clients) or a bearer-token API key (recommended for scripts and automation). For API keys, generate one in your Cryptohopper account settings.
- Configure the client of your choice using its setup guide.
- Issue a test query.
Total time is typically under five minutes.
Was this article helpful?
NoYes
MCP serverhttps://mcp.cryptohopper.com/mcp Try Cryptohopper free
On this page
Need help?
Cannot find the answer to your question? Check F.A.Q. Contact support
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Cryptohopper MCP","item":"https://docs.cryptohopper.com/docs/cryptohopper-mcp"},{"@type":"ListItem","position":2,"name":"Setup overview","item":"https://docs.cryptohopper.com/docs/cryptohopper-mcp/setup-overview"}]}